- crux-devel - lists.crux.nu

CRUX 2.6 Testiso with dm-crypt support
by Thomas Penteker 06 Aug '09

06 Aug '09

Hello together, just like before the CRUX 2.5 release I packed together a test iso with support for an ecrypted root partition (on setup-time). I'd really like to get your feedback on this. Technically speaking there were not much changes that had to be done to the ISO repository, the diff [1] is really tiny. A new package named cryptsetup-initrd got added and its name makes its purpose quite obvious: it will enable you to build the required initial ram disk that allows the system to decrypt / during startup. I put the raw package [2] up for review, too. The test ISO [3] can be downloaded, too though I will upload a slightly fixed version tomorrow adressing a special use case mentioned in the /init script. To make your live easier I provide some documentation [4] covering the new parts for installation. The passphrase you have to provide your partition(s) could be provided via a USB-stick, too. This scenario is not yet covered by my documentation but I will add this, as soon as possible. Please let me know if you can think of any other ``authentication-scenario" that you would like to have added. There's only one issue left that may require discussion: when the boot process leaves initrd (switch_root /newroot) the real root's /dev directory is already mounted as tmpfs + populated but /sbin/start_udev calls ,---- [ head -2 /sbin/start_udev ] | # mount /dev as a tmpfs; note: some video drivers require exec access in /dev | /bin/mount -n -t tmpfs udev /dev -o exec,nosuid,mode=0755 | `---- so we end up with an (almost) empty /dev-directory. My idead was to check for the existence of /etc/.dev_populated (which would be creatd by our initrd before switch_root). If the file is available, start_udev should not (re)mount /dev but delete /etc/.dev_populated and continue execution after line #3. Currently this is not implemented so you'll have to comment out the command in /sbin/start_udev. Comments/Suggestions/critique is welcome! [1] https://serverop.de/~tek/crux-dmcrypt/ISO.DIFF [2] https://serverop.de/~tek/crux-dmcrypt/cryptsetup-initrd/ [3] https://serverop.de/~tek/crux-dmcrypt/crux-2.6-test0a.iso https://serverop.de/~tek/crux-dmcrypt/crux-2.6-test0a.iso.md5 [4] https://serverop.de/~tek/crux-dmcrypt/DM-CRYPT-STEPS kind regards, Thomas Penteker --

2 3

[ANN] CRUX 2.6-test2
by Tilman Sauerbeck 25 Jul '09

25 Jul '09

Hi, we are pleased to announce the third test release of the upcoming CRUX 2.5 release. Please give it a try and report any problems you might find. Thanks, Tilman, for the CRUX team. [1] http://crux.nu/files/pre-releases/crux-2.6-test2.iso http://crux.nu/files/pre-releases/crux-2.6-test2.md5 -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?

1 0

Orphaning ports
by Lucas Hazel 18 Jul '09

18 Jul '09

I have been considering this for some time, but I'll now make it official. I am hereby orphaning all ports I am marked as maintainer for in opt and contrib. I will still be contributing to the CRUX project in maintaining my x86_64 multilib repositories and the portdb and anything else in general. However, my primary focus for the next 6 months is on completing my degree and I don't want the CRUX ports I'm maintaining to suffer because of this. I'll set up a wiki page after I send this email similar to what happened when sip retired. Anything that is not adopted, I will put in a private repo and add to the portdb. Hopefully, I'll have some time next year to be more involved again.

1 0

[PATCH] Do not attempt to build a package if the resulting file can't be written.
by Antti Nykanen 15 Jul '09

15 Jul '09

--- pkgmk.in | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/pkgmk.in b/pkgmk.in index 9fdf768..de50c95 100755 --- a/pkgmk.in +++ b/pkgmk.in @@ -350,6 +350,11 @@ remove_work_dir() { build_package() { local BUILD_SUCCESSFUL="no" + + if [ ! -w "$TARGET" ]; then + error "'$TARGET' is not writable." + exit 1 + fi make_work_dir -- 1.6.2.4

4 3

prt-get installation issue
by Ciprian Dorin, Craciun 10 Jul '09

10 Jul '09

Hello all! I've tried to install prt-get into a non-standard location (like /packages/prt-get). For this I've used ./configure --prefix=/packages/prt-get. Unfortunately make doesn't take these into account.. This is strange... Any ideas? Thanks, Ciprian Craciun.

2 2

CRUX 2.6, LVM2 support
by Juergen Daubert 28 Jun '09

28 Jun '09

Hello, one of the more then once requested features [1] for 2.6 is to have LVM (logical volume manager) [2] available on our installation ISO. I've done the needed modifications to the 2.6 branches yesterday: a) add lvm2 to iso.git http://tinyurl.com/n89geg b) remove opt/libdevmapper http://tinyurl.com/nwee3x c) add opt/lvm2 http://tinyurl.com/nqvt9x d) additions to core/rc http://tinyurl.com/ktqayw I don't see a real reason to split out libdevmapper from lvm2, the package isn't big at all (400 KiB), so I've done b) and imported c) from contrib with slight modifications. Btw, I'd be more than happy to hand over the port c) to someone else, Simon? d) is a very minimalistic approach, it calls lvm if the package is installed. If lvm is installed but the kernel is missing device- mapper support (CONFIG_BLK_DEV_DM), you get a warning at system boot, not a big issue IMO. Adding a configuration variable to /etc/rc.conf might be an option as well. Not sure if it is worth the effort, as the typical CRUX user installs only packages he needs ;) Comments, better ideas? thanks, Juergen [1] http://crux.nu/bugs/index.php?do=details&task_id=342 [2] http://sourceware.org/lvm2/ -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux

1 0

libarchive, xz and pkgutils
by Tilman Sauerbeck 17 Jun '09

17 Jun '09

Hi, CRUX 2.6 will ship with XZ (http://tukaani.org/xz/) in core. That package implements the XZ compression algorithm, which is the successor to LZMA. I believe that LZMA isn't in use in the free software world anymore, so I will only talk about XZ here. To extract an xz'ed tarball, you can do as follows: $ tar xJf coreutils-7.4.tar.xz This is obviously independent of libarchive ;) To extract an xz'ed tarball using bsdtar (libarchive), there's two choices basically: a) tell bsdtar to invoke unxz on the file to uncompress it, then just extract the uncompressed tarball: $ bsdtar --use-compress-program unxz xf coreutils-7.4.tar.xz b) do both uncompression and extraction using libarchive. $ bsdtar xf coreutils-7.4.tar.xz You can optionally specify the J flag to force XZ compression. This requires that libarchive was built with XZ support. Since xz is in core anyway, I would like to build our libarchive with XZ support. Your opinion? What does that mean for pkgutils? At the moment, in pkgutils we initialize libarchive so that support for all supported archive formats and compression algorithms gets included. This means that if compression algorithm foo is implemented in libfoo and libarchive uses libfoo to handle foo we need to link pkgutils statically to libfoo. Until now, this only meant we needed to pull in libz and libbz2. Now, if your copy of libarchive is built with XZ support it will be linked to liblzma (liblzma implements the XZ compression format. Yes, the name is confusing). So if you initialize libarchive to support all known archive/compression formats but only link to libz and libbz2 you'll get a linker error because the XZ stuff isn't found. There's two possible solutions for this: a) link to liblzma (XZ!) too. This will increase the size of our pkgadd binary since now a few more object files from liblzma.a will be included. b) initialize libarchive so that support for XZ is disabled -> no need to link to liblzma. This means that pkgadd/pkginfo will not be able to open xz'ed tarballs. Note that this does NOT apply to pkgmk. pkgmk doesn't use libarchive obviously, but instead calls out to tar to extract stuff. In case we decide to build bsdtar with libarchive support, I would like to change pkgmk so that it uses bsdtar to extract *.tar.gz, *.tar.Z, *.tgz, *.tar.bz2, *.tar.xz, *.zip Let me know what you think. Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?

3 4

portdb now has xml support
by lucas 12 Jun '09

12 Jun '09

I wrote a new implementation of the portdb some time ago that supports XML output. This has now gone live on the portdb page[1]. This should make it easier for non browser based interaction with the portdb, for example, I have also written a CLI tool for making queries with the portdb[2][3]. [1] http://crux.nu/portdb/?f=xml [2] http://git.die.net.au/cgit/crux/tools/pdb [3] http://git.die.net.au/cgit/crux/tools/crux-python -- Lucas Hazel <lucas(a)die.net.au>

1 0

Changes for system/iso.git 2.5
by Matt Housh 25 May '09

25 May '09

Tilman asked me to post a diff of my changes, so here it is. These are the changes I made to get the updated ISO working with 2.6.29.3, new busybox, etc. Matt

3 2

Ship core fonts on the 2.6 iso?
by Tilman Sauerbeck 11 May '09

11 May '09

Hi, Juergen and me have begun some preparations for the 2.6 release (there's a todo list in the wiki at http://crux.nu/Wiki/TODO26) For our xorg ports, I've removed a couple of ancient modules that aren't in use anymore. I'm also considering shipping xorg without any core font packages (ie, drop the following packages from the iso: xorg-font-adobe-100dpi xorg-font-adobe-75dpi xorg-font-alias xorg-font-bh-100dpi xorg-font-bh-75dpi xorg-font-bitstream-100dpi xorg-font-bitstream-75dpi xorg-font-bitstream-vera xorg-font-cursor-misc xorg-font-misc-misc A 'fixed' font and cursor fonts are built into libXfont these days, so -cursor-misc and -misc-misc can safely be removed. IMO shipping bitstream-vera suffices for the iso -- if users wish to use core fonts like -bitstream-100dpi they can install those from ports. Objections? Thanks, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?

2 2