Siduction Forum
Siduction Forum => Ideas & Improvements => Topic started by: buhtz on 2017/02/06, 04:49:16
-
In the last news you wrote about a new release but dropping 32bit. And you would like to know if and why someone still need 32bit.
I am using a Atom netbook which is 32bit. Linux is used for a lot of old machines. I can not understand this 32bit bashing.
But as a small distro like you it is acceptable because of your ressource. I would switch to Debian unstable when it happens. I think there is n such a big difference between this.
Just my 2 cents.
-
@buhtz, that's what is great about linux, you can hold what your using, move laterally to something that works for you or move on with your current or freely select what you like! ;)
Tom
-
Should you be one of those not happy with our plan, please let us know your reasons on our forum. If you have a good reason to still run 32-bit, you might even be able to talk us into a custom build.
Like the quote says, one can be built for you.
Either I or someone else can build it for you. (ah ya, I just volunteered) ;)
You can shoot me a pm or ask directly on irc when this happens.
-
For many years I have had with me a 32 bit cd and/or usb-stick with siduction (or earlier....sidux ....) to be able to rescue files from friends crashed windowz machines. I 32 bit rescue cd/usb-stick will be usable on all machines 64 or 32 bit. For now I will keep my newest 32 siduction usb-stick as rescue tool.
-
If I understood it correctly the main pain isn't the packaging but the need to develop/maintain a 32er kernel. Otherwise I would propose to offer at least a nox iso - useful for rescue and a good starting point for own customisation. And as another benefit it will fit on an old fashioned CD for the PCs that cannot boot from USB. Just my 2¢.
Ciao, Martin
-
You are right that maintaining an extra kernel for 32-bit is what makes this cumbersome. As I wrote in the release notes, a Liquorix-Kernel or one by Debian will work perfectly fine here.
-
Hi,
according to this German wiki entry (https://wiki.siduction.de/index.php?title=Erstellen_eines_siduction-%C3%A4hnlichen_ISO) I was able (after some tweaking) to build my own "siduction-style" lxqt-patience-i386.iso - already with liquorix kernel - thx Alf.
I've updated the wiki a little bit to reflect the latest status, but some more maintenance would be great.
Any interest in an English translation? - I would volunteer to do it next week.
Ciao, Martin
-
As we said before - we will try to build i386 images on request - yesterday i changed the receipes of LXDE and LXQt that way. The builds went surprisingly well - at least the images start :) - so i will upload LXDE and LXQt i386 to our mirrors. Maybe devil will write a few sentences in that regard.
A few remarks: horo, we should update the wiki not only a little bit, the pyfll thing should be a bigger overhaul.
I build most of the time on our buildserver, but for testing i use my local machine. It turns out that a few simple settings can speed up the build process a lot:
* build in tmpfs - that will improve the build time dramatically
* use apt-cacher-ng, especially if the internetconnection is slow
The tempfs thing gives an unbelivable boost - ok, one should have sufficient memory. Rignt now it takes between 7-9 min to build an image on my older local machine with warm apt-cache.
-
Hi Alf,
cool improvement when tmpfs and apt-cacher-ng are used - down from 50 minutes to 9 minutes. Thx for the hint. It took me a little bit of reading the fine documentation (the pyfll file itself ;) ) to find out that the argument in the *.conf files (originally cloned from git) must be "apt_cacher" instead of "apt-cacher" as it was before. I will document this in the wiki next week when I'm back home.
Ciao, Martin
EDIT: Ok, I changed the wiki a bit more. BTW: We had a discussion about pyfll some time ago (https://forum.siduction.org/index.php?topic=4777.msg39486).
-
Hi,
as promised I've updated and translated the old wiki entry, it redirects (https://wiki.siduction.de/index.php?title=Erstellen_eines_siduction-%C3%A4hnlichen_ISO&redirect=no) now to the bilingual wiki entry (https://wiki.siduction.de/index.php?title=Build_your_own_%22siduction-like%22_ISO).
FEEDBACK AND CONTRIBUTION WELCOME!
Wie versprochen habe ich den alten Wiki-Eintrag überarbeitet und übersetzt, der Artikel verweist (https://wiki.siduction.de/index.php?title=Erstellen_eines_siduction-%C3%A4hnlichen_ISO&redirect=no) jetzt auf den bilingualen Artikel (https://wiki.siduction.de/index.php?title=Build_your_own_%22siduction-like%22_ISO).
BITTE UM KOMMENTARE UND VERBESSERUNGEN!
Ciao, Martin