Partconf should make sure that appropriate userspace tools for created filesystem are installed to /target. Especially fsck.$FILESYSTEM is needed.
How do we handle this as smoothly as possible? Should we insist on a naming standard of some sort? For reiserfs we have progsreiserfs and reiserfsprogs (yes, two different packages with different maintainers), for xfs we have xfsprogs, for ext2 and ext3 we have e2fsprogs, for jfs jfsutils etc.. Should we simply make a table of some sort, or should we rely on Provides: for this? /* Steinar */
Am So, den 16.11.2003 schrieb Steinar H. Gunderson um 18:24: I would like better a solution which fits better with modularity. What about a private debconf question, which holds a comma separated list of files to apt-install. This template would come with the userspace-tools udeb and partconf would apt-install the packages in question if corresponding filesystems are created.
Well, there are multiple userspace-tools udebs, right? (I'm not sure about how this works -- I can't really figure out where mkfs.* comes from :-) ) They'd have to register themselves in some sane way allowing for partconf to lookup filesystems into debs, then. Something like "partconf/userspace-packages/ext3 = e2fsprogs", perhaps? This would of course have to be a documented hook. :-) /* Steinar */
Am So, den 16.11.2003 schrieb Steinar H. Gunderson um 19:29: Yes, in case of reiserfs, the template would come with mkreiserfs-udeb. I neither don't know what provides mkfs.ext3 but I suppose it is parted-udeb?
fdisk-udeb (source package util-linux), actually, according to Tollef. /* Steinar */
Sebastian Ley wrote: I don't understand this pull toward using debconf questions for things that the filesystem can do and that do not involve user interaction or overriding. Just have any udeb that provides a mkfs.* also provide a /usr/share/fs-tools/<foo> that lists the names of packages to install for that filesystem type. Or any similar approach.
sön 2003-11-16 klockan 23.16 skrev Joey Hess: What, when we have a perfectly working registry? ;-) *runs for cover*