You are not logged in.
What do you find so good about the bunsenlabs? What's it's best feature?
Actually the community, even though I think I annoy some of them sometimes ![]()
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
What do you find so good about the bunsenlabs? What's it's best feature?
(please don't say openbox.. crosses fingers)
> Openbox
> Tint2 panel
> Nice default configuration for you to customize to your liking
> Forums
> Doesn't require much in the way of hardware resources. I usually run while using under 1GB of RAM.
Offline
dwmXS alpha ISO available
Debian 9.1
kernel 4.11.0-0.bpo.1
dwm-6.1-no patches
dmenu-4.7 [Alt+p]
dmenu-extended [Alt+d]
jgmenu [Alt+F1] or mouse right click
https://github.com/johanmalm/jgmenu
zsh+ohmyzsh
http://ohmyz.sh/
surf browser
st simple terminal
termite terminal
https://github.com/thestinger/termite
i3lock-fancy
https://github.com/meskarune/i3lock-fancy
ceni network config (sudo ceni)
htop custom htoprc
font rendering improved as per;
https://wiki.manjaro.org/index.php?titl … tRendering
Firefox ESR
Vivaldi
pcmanfm
rox-filer
glances system monitor
redshift ( ~/.xinitrc, add your geolocation to ~/.config/redshift.conf)
mpd soma fm 'ready to roll'
Offline
Well....
That looks very interesting. I'm going to slap your alpha .ISO into a VM and play around.
The meaning of life is to just be alive. It is so plain and so obvious
and so simple. And yet everybody rushes aroound in a great panic
as if it were necessary to achieve something beyond themselves.
- Alan Watts
Offline
@mrneilypops: I've just taken dwmxs for a run. Great effort. It's got some really nice touches (font, icon, theme, zsh, mix of software, etc).
It was a long time since I used dwm, so I have to admit I felt a bit lost to start with. The ratfactor visual guide came in very handy ![]()
Just had a quick play over lunch. Will have a deeper mooch around later.
Offline
I also had a go with it. I'll have a better go later, but it's really nice, I love the way it looks.
Did you actually like using dwm window manager? No offense, but you don't seem like the type of user who would enjoy a tiling window manager.
@mrneilypops is dwmXS 32 or 64 bit?
uname -afrom a terminal should give you your answer. Output from my BL-Hydrogen install...
~$ uname -a
Linux bl-stable 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u3 (2017-08-15) x86_64 GNU/LinuxNote the x86_64 near the end, signifying 64-bit.
Last edited by KrunchTime (2017-08-30 01:19:55)
Offline
@Temetka
@mariannemarlow
@malm
Thanks for trying dwmXS!
All feedback most welcome.
You will find more than 'one app per task' in some cases at this time until I decide the final apps list
64 bit only for the moment.
Offline
64 bit worked on my old netbook!
Yay!
Do you notice a speed boost?
64-bit is also significantly more secure than a 32-bit operating system thanks to the NX bit and the vastly increased effectiveness of stretch's ASLR/PIE combination ![]()
Offline
This is an old 32 bit netbook though, how come it even worked?!
Can we please see the output of:
lscpu | sed qThat should show your CPU architecture ![]()
Offline
^ That's 32-bit, was that output from dwmx?
I'm not sure what shows in /proc/cpuinfo if a 32-bit OS is used on a 64-bit processor, tbh.
Offline
@HoaS
On a 32 bit install with a 64 bit processor
$ lscpu | sed q
Architecture: i686Since you asked,
beardy@debian:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz
stepping : 10
<snip>My Core2Quad is absolutely 64 bit (no VT-x hence my VM installs being 32 this is snipped from such)
I suspect @mariannemarlow's CPU may well actually be 64 bit, many netbooks are, even if they came new with a 32 bit OS because of low memory.
Maybe the output of
cat /proc/cpuinfo | grep modelOne's favourite search engine could then turn up it's bitness.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
Then It's 64 bit
<omitted>
Intel® 64 ‡ Yes
Instruction Set 64-bit<omitted>
Security & Reliability
Intel® Trusted Execution Technology ‡ No
Execute Disable Bit ‡ Yes
So it is 64 bit, and as @HoaS pointed out running a 64 bit install will enhance security, though perhaps not as much as with a processor that supported Intel® Trusted Execution Technology.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
I'm not offended at all.
But what "type of user" do you think I am? just curious!
The kind of user who likes XFCE. ![]()
Offline
^Eclectic taste? How is that working with one husband/wife?
Btw love those colorful bird-pix. Quote: "They're like flying candies!"
Offline
^I mean the fotos from Featheredfiends.
Offline
^Eclectic taste? How is that working with one husband/wife?
Btw love those colorful bird-pix. Quote: "They're like flying candies!"
at both sentences.
Offline
^Oh, that's from Rocky - he said something like that in the pet shop where Adrian worked.
Offline
Getting settled in to my Alpine Linux box now, I'm liking it more the more I dig into it.
The init system is _much_ easier to manipulate than systemd, custom startup scripts are just that with no special syntax or format required beyond the start() function; here is one I've just made to save the backlight level on shutdown and restore it again on boot (systemd has a similar systemd-backlight@.service):
empty@alpine:~ $ cat /etc/init.d/backlight
#!/sbin/openrc-run
# Copyright 2017 HoaS
# Licensed under the GNU General Public License v3
description="Restore the backlight level."
start() {
ebegin "Restoring backlight level"
cp /etc/backlight.save /sys/class/backlight/intel_backlight/brightness
}
stop() {
ebegin "Saving backlight level"
cp /sys/class/backlight/intel_backlight/brightness /etc/backlight.save
}
empty@alpine:~ $It's exceptionally crude but it works perfectly 8)
Offline
It's exceptionally crude but it works perfectly 8)
If it works, that's all that usually matters. You scratched an itch. ![]()
Last edited by KrunchTime (2017-09-22 21:20:26)
Offline
Sometimes I think systemd adds unnecessary layers of complication to things. When I need something to run as a service at periodic intervals, it seems much easier to add it to cron. I usually end up building systemd timers and service files anyway but realistically I could save time by just tossing the stuff into cron and scheduling it.
Openrc may be crude by systemd's standards but that also looks like something that a person could get some work done with. Is it capable of handling timed events or would you go to cron for that in openrc?
Offline