- This topic has 99 replies, 13 voices, and was last updated Aug 19-2:48 pm by andyprough.
-
Posts
-
olsztyn
Mutual exclusion, thread locks and other technology techniques were applied only in expensive systems. Today even our phones and appliances have many of these capabilities.
I completely agree with you…
Back in nineties you mentioned and from my experience back in eighties as well, on IBM mainframes…
Today, it is phones which are an example of such resilience. Just imagine if iPhone froze due to some misbehaving app… That would be some big news and immediate attention from Apple…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
Brian Masinick
Yes, you are right about the eighties with IBM mainframe computer systems.
The MULTICS project started most of the early operating systems research that is the foundation of today’s systems.
It contributed to the mainframe system maturity and it was the foundation of the UNIX effort too. That work dates clear back to the sixties; it was far too costly to effectively implement back then,. I did run MULTICS on a Honeywell mainframe in 1982; it was part of a personnel systems program and it was my favorite. It was what led me to UNIx and much later Linux!
--
Brian Masinickex_Koo
One of the best patches for me is autostart as I can keep all my dwm stuff, separate and I don’t have to use .xinitrc for autostart’s in dwm. I don’t use a GUI login manager as use I tbsm to switch between window managers.
~/.dwm folder
#! /bin/bash nitrogen --restore & dunst & picom --config ~/.config/picom/picom.conf & nm-applet & dwmbar & ##~/suckless/dwmbar/dwmbar.sh &Brian Masinick
Brian Masinick
I haven’t found anything appealing yet in Badwolf. Firefox and Chrome are much more functional and complete; browsers like links2, lynx, and dillo are orders of magnitude lighter and faster for simple document page rendering; I see little to favor Badwolf.
--
Brian Masinick
andyprough
One of the best patches for me is autostart as I can keep all my dwm stuff, separate and I don’t have to use .xinitrc for autostart’s in dwm. I don’t use a GUI login manager as use I tbsm to switch between window managers.
~/.dwm folder
#! /bin/bash nitrogen --restore & dunst & picom --config ~/.config/picom/picom.conf & nm-applet & dwmbar & ##~/suckless/dwmbar/dwmbar.sh &Yes, I’m a big fan of the autostart patch. You and I use most of the same applets and autostart programs. But tell me about tbsm for window manager switching, I’ve never heard of it.
Yes, I’m a big fan of the autostart patch. You and I use most of the same applets and autostart programs. But tell me about tbsm for window manager switching, I’ve never heard of it.
tbsm is just a simple script that let you login to windows managers or GUI desktops from tty. No need to install login managers or even use .xinitrc .
I’m a big fan of the autostart patch. You and I use most of the same applets and autostart programs. But tell me about tbsm for window manager switching,
As dwm is well on course to become my primary WM on antiX, I am curious what autostart provides that I should consider to implement it… I was not clear on this looking at very limited info on suckless.
Also looked at tbsm, which at first looks interesting to simplify switching WMs. Just want to mention that the latest update was to rel. 0.5 and the date of this latest update was in Dec. 2018. Almost three years. Is this still a viable choice considering this project has been virtually dropped?Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersAlso looked at tbsm, which at first looks interesting to simplify switching WMs. Just want to mention that the latest update was to rel. 0.5 and the date of this latest update was in Dec. 2018. Almost three years. Is this still a viable choice considering this project has been virtually dropped?
Don’t worry about the date as there are only so many things that can be done with a simple program like this it works great..
The reason I like using dwm-autostart it keep all the related dwm stuff separate from the rest of the system setting. If you start using .xinitrc to start programs after login it can interfering with what use want to start with each window manager, as with i3wm I keep my autostart’s as part of the i3 .config.
part of my i3 config.
exec_always --no-startup-id exec i3-workspace-names-daemon & exec --no-startup-id picom --config ~/.config/picom/picom.conf & exec --no-startup-id nm-applet & exec --no-startup-id dunst & exec --no-startup-id /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 & exec --no-startup-id nitrogen --restore & exec --no-startup-id xfce4-power-manager &dwm-autostart
#! /bin/bash nitrogen --restore & dunst & picom --config ~/.config/picom/picom.conf & nm-applet & dwmbar & ##~/suckless/dwmbar/dwmbar.sh &Anonymous
very interesting thread. I like that DWM is dynamic and can handle the gimp windows
and be lean and mean. my only ? is if it will continue to support 32-bit in
future releases. Does anyone know?. setting it up on a p4-3ghz with 2 gb ram on laptop.
A hp pavilion zv5000 .ati 9000 igp video.. antiX-19.4-core rice build up.Brian Masinick
I don’t know any particulars about dwm, but considering that it does have much of it’s lineage in the “traditional” original concepts of window managers and it is also in a class of “tiling” window managers (of which there are not that many choices), my inclination is to think that it’ll be around for a while.
However, if in doubt, but you are STILL interested, make sure to grab the current source code, then you will be able to use it for a very long time indeed.
--
Brian MasinickBrian Masinick
Another thought: if you do manage to either forget or lose the code, I know that manyroads and a couple of the people in this thread DO have the code; one of us ought to be able to grab it for you if you lose track of it.
--
Brian Masinickandyprough
very interesting thread. I like that DWM is dynamic and can handle the gimp windows
and be lean and mean. my only ? is if it will continue to support 32-bit in
future releases. Does anyone know?. setting it up on a p4-3ghz with 2 gb ram on laptop.
A hp pavilion zv5000 .ati 9000 igp video.. antiX-19.4-core rice build up.DWM should compile on 32-bit as long as the distro supports it with build tools.
The bigger question is how long will Debian continue to support 32-bit? Ubuntu and Fedora are making moves away from supporting 32-bit, and the Debian project is (unfortunately) heavily influenced by the teams at Ubuntu and Fedora. As we saw from their incredibly short-sighted systemd decision, where Debian decided to follow Ubuntu and Fedora’s lead.
I have the 6.2 dwm source tarball downloaded. on my laptop I’m
going to git clone and build it.andyprough
I have the 6.2 dwm source tarball downloaded. on my laptop I’m
going to git clone and build it.Awesome! Let us know if you run into any questions.
- You must be logged in to reply to this topic.
