MX Linux Forum

(I have cross-posted this on both MX and BunsenLabs Forums).

For those who are interested in having a version of BunsenLabs (Lithium) running on MX19, I have begun work on that task. It is doubtful that I will ever 'fully' complete the task without the help of others. I will be able to build something to my liking but probably not to yours without your inut and assistance. If you are interested in helping, you can jump right in and contribute in this thread.

By way of status update, thus far I have installed and implemented a basic version of the current pre-alpha (experimental) BunsenLabs materials (per their guidance) on MX19b3. Images are available here:




To create a version on your MX19b3 installation, add this line to your apt sources (/etc/apt/sources.list.d/various.list) : To build a version of BunsenLabs (Lithium- experimental) on MX19b3 you simply need to enter the following commands in terminal mode: Among the Major tasks that need to be accomplished are:

- removal of the few systemd dependencies. On MX they probably do not need to be removed if you run using systemd.
- thorough testing for breakage(s) needs to be conducted. I have just begun those (for the features I use).
- transition to and testing on the released version of MX19

antiX19 Note:
I may or may not undertake the same task for antiX19. My initial testing indicates that moving BunsenLabs Lithium to antiX19 may be a much larger task and more difficult to achieve than it is on MX19b3.

I think it would be much better if an antiX expert wants to lead that charge. For now at least, I'll leave that for others.

Here is an image of Lithium on running on mx19b3, with yad logout and new background.

manyroads wrote: Tue Oct 08, 2019 12:17 pm My initial testing indicates that moving BunsenLabs Lithium to antiX19 may be a much larger task and more difficult to achieve than it is on MX19b3.

I think it would be much better if an antiX expert wants to lead that charge. For now at least, I'll leave that for others.

That's because BunsenLabs, like the vast majority of Debian base distros, uses systemd.

anticapitalista wrote: Tue Oct 08, 2019 5:21 pm [...]
That's because BunsenLabs, like the vast majority of Debian base distros, uses systemd.

You are correct. Actually the only systemd dependency I have found is with their logout button. I replaced that with a yad script and everything works well. I am able to run the entire BL Lithium setup on mx19b3, without systemd. Perhaps though the new mx systemd shim is doing something invisible to me ... I'm easily fooled by magic tricks...

In Lithium, they have built a beautiful new desktop with OB.

manyroads wrote: Tue Oct 08, 2019 5:29 pm

anticapitalista wrote: Tue Oct 08, 2019 5:21 pm [...]
That's because BunsenLabs, like the vast majority of Debian base distros, uses systemd.

You are correct. Actually the only systemd dependency I have found is with their logout button. I replaced that with a yad script and everything works well. I am able to run the entire BL Lithium setup on mx19b3, without systemd. Perhaps though the new mx systemd shim is doing something invisible to me ... I'm easily fooled by magic tricks...

In Lithium, they have built a beautiful new desktop with OB.

They are using systemd as the default init. MX has systemd as init ,but not set as default. antiX does not and will not have systemd at all, which means BunsenLabs on antiX is a no go.

anticapitalista wrote: Tue Oct 08, 2019 5:35 pm

manyroads wrote: Tue Oct 08, 2019 5:29 pm

anticapitalista wrote: Tue Oct 08, 2019 5:21 pm [...]
That's because BunsenLabs, like the vast majority of Debian base distros, uses systemd.

You are correct. Actually the only systemd dependency I have found is with their logout button. I replaced that with a yad script and everything works well. I am able to run the entire BL Lithium setup on mx19b3, without systemd. Perhaps though the new mx systemd shim is doing something invisible to me ... I'm easily fooled by magic tricks...

In Lithium, they have built a beautiful new desktop with OB.

They are using systemd as the default init. MX has systemd as init ,but not set as default. antiX does not and will not have systemd at all, which means BunsenLabs on antiX is a no go.

Actually the devs at BunsenLabs say there are very few init dependencies in their setup, I think I have only seen one mentioned (BL-exit their Logout). I am running MX19b3 without systemd and things boot and run fine; lightdm on MX fires up Openbox just fine as well. antiX19b3 boots with BL Lithium, however it chokes when SLIM tries to run BL Lithium OpenBox. I'll look into it further. I don't think there's a major problem, it's just that I'm way out of my league debugging this sort of issue. I'm more of a crash & hack kind of guy.

@anticapitalista... whoo- rah. BunsenLabs is now running on antiX19b3. It booted cleanly and is operational. I needed to clean off all the standard desktops, slim and replace the display manager with lightdm. Tada!

I'll begin working on building an antiX19 version of BunsenLabs Lithium as well as the one for MXLinux19b3.

Wouldn't it be simpler to just run the install script? It should be able to add the BL stuff alongside MX.

EDIT: sorry, that's probably what you did. Ignore me, I'm tired

Head_on_a_Stick wrote: Wed Oct 09, 2019 2:10 pm Wouldn't it be simpler to just run the install script? It should be able to add the BL stuff alongside MX.

EDIT: sorry, that's probably what you did. Ignore me, I'm tired

Mostly it is... rest well my friend.

Details for the installs (tutorial) on MX & antiX are available here:

http://eirenicon.org/getting-bunsenlabs ... a-journey/

What are you thinking of calling them? BLantiX? BL-MX? BLAM-X?

I still think BL could do worse than switching to a MX or antiX base instead of straight Debian.

Stevo wrote: Wed Oct 09, 2019 5:21 pm What are you thinking of calling them? BLantiX? BL-MX? BLAM-X?

I still think BL could do worse than switching to a MX or antiX base instead of straight Debian.

I think BLaM with a theme song by Wham might work. I'm actually hoping the folks at BL will see the ease with which I was able to make BL work with both antiX & MX and that will speak volumes in terms of benefits to all the distros. If it were me, I'd certainly see a significant advantage in using our distros as their base. Systemd, no-systemd, low-spec machines, blended toolkits, etc. But then what do I know.

...I think BLaM with a theme song by Wham might work...

BLaM#!

(the punctuation being in honour of the late great crunchbang, of course)

I'll write a Blog post on BLaM#! later today. I'll provide a link here.

BLaM#! BunsenLabs on MXLinux or antiX 'announcement.

http://eirenicon.org/2019/10/10/blam-openbox/

MX#!

If you want wallpapers for BL and/or BL&MX, I have made a few. :lipsrsealed: Hopefully they'll be appealing. If not, at least they are free.

https://www.dropbox.com/sh/ksubol4iaxr2 ... 9NzHa?dl=0

For those interested, here are a few photos of BL Lithium running on MX19b3 with my new wallpapers:

Outstanding work

One of the most well designed desktops I have ever seen. So many combos
https://i2.wp.com/eirenicon.org/wp-cont ... 9b3-b.png

Congrats on I'll begin working on building an antiX19 version of BunsenLabs Lithium. Who said it will not work on a completely systemd free environment.

Installing your antiX 19-b3 version on my x220. 276 new programs ,169mb archives 568mb Disk space used. hopeful i3 will live happily on on board. It was a non grub install. Had some junk call blowdows wasting a good disk partition. Will keep you updated.

Thanks so much.
Your baby antiX 19-b3-bl with all WMs removed and sgfxi installed intel video drivers with antiX fully updated.

KoO wrote: Wed Oct 16, 2019 8:48 am Thanks so much.
Your baby

I am very glad you like the setup. I, also, find it wonderful and extremely well built. I think the build on antiX could lead to an astounding rise in the popularity of both BL and antiX. It's pretty hard to boost the popularity of MX.

Nice work, looks really nice.

So, this should work on the new MX-19RC1?

Thank you for the effort and time spent on this.

Having not built BL-Lithium on anything beyond MX19b3, I can't say for certain. I can say that I will build and test BL-Lithium & MX19 when they are both officially ready for broader use.

If you have access to an RC for both you can certainly try building them to see how well my instructions/ guide works. I would appreciate an enumeratioin of any changes/ fixes you would like to contribute or request.

Edit: I am downloading the MX19RC1 just now. I'll build and test RC1 for both & Lithium over the next day or two. Watch this space for updates.

Okay.

I have downloaded both RC, 32 and 64 bit, and will try your tutorial on them. I probably will not have time to try this until tomorrow at the earliest. The 64 bit will be installed on a CF-31Mk4 and the 32 bit will go on a CF-29Mk4.

Will report back on the outcome. Thanks.

mklym wrote: Wed Oct 16, 2019 9:42 am Okay.

I have downloaded both RC, 32 and 64 bit, and will try your tutorial on them. I probably will not have time to try this until tomorrow at the earliest. The 64 bit will be installed on a CF-31Mk4 and the 32 bit will go on a CF-29Mk4.

Will report back on the outcome. Thanks.

Just in case you missed my update to your first query....

Edit: I am downloading the MX19RC1 just now. I'll build and test RC1 for both & Lithium over the next day or two. Watch this space for updates.

Yes, I did miss your update. Thanks.

I have everything running on MX19RC with the RC version of BunsenLabs Lithium... it works wonderfully and everything seems stable.
Updated build instructions are here:

https://wp.me/P4apmc-oW

Enjoy!

Up and running with BLaM#! in MX19RC1 on my CF-31. All good so far, have not had time to do much tweaking.

There was a small glitch for me when 'fixing' the logout/login button. Here is the quote from the tutorials (both the original and the new one covering MX-19RC1 are the same in this regard):

Next for tint2 (the menu bar at the top, button on the far right) open your terminal and edit the following file from terminal with the following command:

geany .config/tint/tintrc

Once open, search tintrc for bl-exit and replace bl-exit with .config/yad/logout.sh. Save & Close tint2rc.

The proper command should be:

geany .config/tint2/tint2rc

Without making those changes I was at a standstill. All I had originally was an empty text file.
Hope this helps anyone else having this problem.

Other than that little moment, everything went smooth.
Again, thank you for your effort and time manyroads.

Thank you. Consider it fixed. Sorry for the typo.

No worries. If I could figure it out, others would have had no problem.

I found out NOT to install a PAE kernel when offered in the BL questionnaire. I had a kernel panic and system lock-up. Had to pull the battery and ac adapter to shut it down. Booted the live MX19RC1 and ran the MX Boot Repair. On reboot I selected the non-PAE kernel and problem solved.

Coming from my BLaM#!

Cool! I m glad you are having fun with it.

Hey, cool project manyroads. If only for the learning and do believe Bunsenlabs is a good solid distro, though never used an actual install of it for more than a few mins before changing sources on it and then proceeding to tweaking all hades out of it. So quickly ended up being a hybrid OS. Ran it as a secondary OS on that laptop for a good while. Cool thing you're doing and keep it up manyroads, one of the great things about gnu/Nix, anyone is free to use anything from other distro's. One comes out with a really useful tools/software setup or config, all others can readily adopt or utilize it too. Think it's a key contributor to making gnu/Linux that much better. Anyone can take the best of what works from whatever source, pop them in a techno-blender and WHAM, make an awesome OS/install.

Wanted to comment some about things which were said in this thread but it's offtopic, so cross linking to another thread here. If you don't mind, if you do I'll get rid of it if/when asked. :P