Hello, we are happy to announce that a test-release of CRUX 2.5 is available now [1]. Please give it a good test and report any problem. Remember, the glibc port does not build locales, see [2] how to generate them. thanks and best regards Juergen, for the CRUX team. [1] http://crux.nu/~jue/tmp/crux-2.5-test2.iso http://crux.nu/~jue/tmp/crux-2.5-test2.md5 [2] http://crux.nu/Main/Handbook2-5#LocaleGeneration -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
On 10/20/08 18:56 Juergen Daubert wrote:
Hello,
we are happy to announce that a test-release of CRUX 2.5 is available now [1]. Please give it a good test and report any problem. Remember, the glibc port does not build locales, see [2] how to generate them.
Hello, thanks for the 2.5 test image(s). Setup and the following small sysup went well here on two machines. As a minor note, I spotted some cruft on the ISO in /lib/modules, a couple of older kernel libs (2.6.27 and 2.6.27-rc9 afair). Regards, Simone -- Simone Rota Bergamo, Italy - http://www.varlock.com
On Sat, Oct 25, 2008 at 02:29:44AM +0000, Simone Rota wrote:
On 10/20/08 18:56 Juergen Daubert wrote:
Hello,
we are happy to announce that a test-release of CRUX 2.5 is available now [1]. Please give it a good test and report any problem. Remember, the glibc port does not build locales, see [2] how to generate them.
Hello,
thanks for the 2.5 test image(s). Setup and the following small sysup went well here on two machines.
Great, thanks for testing!
As a minor note, I spotted some cruft on the ISO in /lib/modules, a couple of older kernel libs (2.6.27 and 2.6.27-rc9 afair).
Jose has spotted this as well, I've added a note to [1]. Greetings Juergen [1] http://crux.nu/Wiki/TODO25 -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
Hello, Juergen! Juergen Daubert schrieb:
we are happy to announce that a test-release of CRUX 2.5 is available now [1]. Please give it a good test and report any problem. Remember, the glibc port does not build locales, see [2] how to generate them.
Thanks for your work! CRUX-2.5-test2 seems to work here... even after doing strange thiongs like this: I am looking for a way to install CRUX from an already booted foreign linux system without the necessity to boot from the CRUX CD. Sometimes I cannot access the console (hosted machine), there is no CDROM-drive (netbook) and no quick way to boot from a CRUX USB without building one manually. Currently, I mount the .iso, unsquashfs crux.squashfs, copy /cdrom/crux to the unpacked squashfs, chroot into it and run setup from there. Well, everything seems to work fine... the only thing which I need to install manually is unsquashfs from squashfs-tools. 1) Does it make sense to include unsquashfs with the CRUX CD? 2) Is there a simpler way to achieve above installation method aside of building my own un-iso/squashfsed CRUX? Regards, Clemens
On Sat, Oct 25, 2008 at 06:14:13PM +0200, Clemens Koller wrote:
Hello, Juergen!
Hello Clemens,
Juergen Daubert schrieb:
we are happy to announce that a test-release of CRUX 2.5 is available now [1]. Please give it a good test and report any problem. Remember, the glibc port does not build locales, see [2] how to generate them.
Thanks for your work!
Thanks for testing!
CRUX-2.5-test2 seems to work here... even after doing strange thiongs like this:
I am looking for a way to install CRUX from an already booted foreign linux system without the necessity to boot from the CRUX CD.
Sometimes I cannot access the console (hosted machine), there is no CDROM-drive (netbook) and no quick way to boot from a CRUX USB without building one manually.
Currently, I mount the .iso, unsquashfs crux.squashfs, copy /cdrom/crux to the unpacked squashfs, chroot into it and run setup from there. Well, everything seems to work fine... the only thing which I need to install manually is unsquashfs from squashfs-tools.
1) Does it make sense to include unsquashfs with the CRUX CD?
Hmm, not sure what you mean. A squashfs package on the iso or the unsquashfs as part of the binaries available after booting the iso? In both cases it dosn't solve your problem IMO, because you either need unsuashfs to access the iso, or a running crux system to install the package. Or do I miss something?
2) Is there a simpler way to achieve above installation method aside of building my own un-iso/squashfsed CRUX?
Good question, but don't think so. Would you mind writing a short guide in our wiki, please? Regards Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
where can i download crux-2.5-test iso? On Tue, Oct 28, 2008 at 3:59 PM, Juergen Daubert <jue@jue.li> wrote:
On Sat, Oct 25, 2008 at 06:14:13PM +0200, Clemens Koller wrote:
Hello, Juergen!
Hello Clemens,
Juergen Daubert schrieb:
we are happy to announce that a test-release of CRUX 2.5 is available now [1]. Please give it a good test and report any problem. Remember, the glibc port does not build locales, see [2] how to generate them.
Thanks for your work!
Thanks for testing!
CRUX-2.5-test2 seems to work here... even after doing strange thiongs like this:
I am looking for a way to install CRUX from an already booted foreign linux system without the necessity to boot from the CRUX CD.
Sometimes I cannot access the console (hosted machine), there is no CDROM-drive (netbook) and no quick way to boot from a CRUX USB without building one manually.
Currently, I mount the .iso, unsquashfs crux.squashfs, copy /cdrom/crux to the unpacked squashfs, chroot into it and run setup from there. Well, everything seems to work fine... the only thing which I need to install manually is unsquashfs from squashfs-tools.
1) Does it make sense to include unsquashfs with the CRUX CD?
Hmm, not sure what you mean. A squashfs package on the iso or the unsquashfs as part of the binaries available after booting the iso? In both cases it dosn't solve your problem IMO, because you either need unsuashfs to access the iso, or a running crux system to install the package. Or do I miss something?
2) Is there a simpler way to achieve above installation method aside of building my own un-iso/squashfsed CRUX?
Good question, but don't think so. Would you mind writing a short guide in our wiki, please?
Regards Juergen
-- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
_______________________________________________ crux-devel mailing list crux-devel@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux-devel
-- Crux Saves Your Soul.
On Tue, Oct 28, 2008 at 04:11:46PM +0800, junkie wrote:
where can i download crux-2.5-test iso?
look here: http://lists.crux.nu/pipermail/crux-devel/2008-October/003767.html regards Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
Hello, Juergen!
CRUX-2.5-test2 seems to work here... even after doing strange thiongs like this:
I am looking for a way to install CRUX from an already booted foreign linux system without the necessity to boot from the CRUX CD.
Sometimes I cannot access the console (hosted machine), there is no CDROM-drive (netbook) and no quick way to boot from a CRUX USB without building one manually.
Currently, I mount the .iso, unsquashfs crux.squashfs, copy /cdrom/crux to the unpacked squashfs, chroot into it and run setup from there. Well, everything seems to work fine... the only thing which I need to install manually is unsquashfs from squashfs-tools.
1) Does it make sense to include unsquashfs with the CRUX CD?
Hmm, not sure what you mean. A squashfs package on the iso or the unsquashfs as part of the binaries available after booting the iso?
I think I need unsquashfs as part of the binaries available after booting the iso. It would be also possible to unpack the squashfs-tools package when it's included on the CD but that would need an additional step.
In both cases it dosn't solve your problem IMO, because you either need unsuashfs to access the iso, or a running crux system to install the package. Or do I miss something?
Propably. :-) Goal: No need to boot from CDROM, no need to access the console, minimum downtime. Assumption: A system always has a spare partition for a version of CRUX. Usually, two small partitions w/ <10G each for / are sufficient for alternating installations. That's roughly what I did (out of my head) to minimize downtime of the running system: - download iso. $ mount -o loop crux-2.5.iso /mnt/iso $ unsquashfs /mnt/iso/crux.squashfs $ mkdir squashfs/cdrom $ cp -a /mnt/iso/crux squashfs/cdrom - chroot into squashfs $ setup - mkfs.ext3 to some spare partition - install to some spare partition - configure crux and compile kernel (or copy from existing system) - configure bootloader (usually lilo or grub) - install custom stuff from existing system. - cross fingers and reboot :-) If everything works fine, a full system update is done with the downtime of one reboot. :-) If something goes wrong, a reboot to the old system is possible. It's possible to configure lilo as well as grub to do da failsafe-fallback in case one system doesn't work. Using kexec could shorten the downtime even more... well that's a task for the advanced lection. ;-)
Good question, but don't think so. Would you mind writing a short guide in our wiki, please?
Yes, once there is a working solution for the common CRUX user. Regards, Clemens
On Tue, Oct 28, 2008 at 08:46:57PM +0100, Clemens Koller wrote: [...]
1) Does it make sense to include unsquashfs with the CRUX CD?
Hmm, not sure what you mean. A squashfs package on the iso or the unsquashfs as part of the binaries available after booting the iso?
I think I need unsquashfs as part of the binaries available after booting the iso. It would be also possible to unpack the squashfs-tools package when it's included on the CD but that would need an additional step.
In both cases it dosn't solve your problem IMO, because you either need unsuashfs to access the iso, or a running crux system to install the package. Or do I miss something?
Propably. :-)
Now I got it. Currently all executable binaries are packed in crux.squashfs and therefore not available via loop-mount of the iso. But it shouldn't be a problem to put the 50k unsquashfs somewhere else on the iso :) Maybe a new subdir /bin or something similar. Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
Hi, Juergen!
1) Does it make sense to include unsquashfs with the CRUX CD? Hmm, not sure what you mean. A squashfs package on the iso or the unsquashfs as part of the binaries available after booting the iso? I think I need unsquashfs as part of the binaries available after booting the iso. It would be also possible to unpack the squashfs-tools package when it's included on the CD but that would need an additional step.
In both cases it dosn't solve your problem IMO, because you either need unsuashfs to access the iso, or a running crux system to install the package. Or do I miss something? Propably. :-)
Now I got it. Currently all executable binaries are packed in crux.squashfs and therefore not available via loop-mount of the iso. But it shouldn't be a problem to put the 50k unsquashfs somewhere else on the iso :) Maybe a new subdir /bin or something similar.
Yes, that sounds good. A /bin/unsquashfs would do the job for me. Can you please include that for the next release? Thanks! Regards, Clemens
participants (4)
-
Clemens Koller -
Juergen Daubert -
junkie -
Simone Rota