As you probably are aware, only part of my work on sysvinit made it
into Etch.  I am still not sure if I should request an exception from
the release team to get an updated version into Etch or not.  On one
hand, I would like to have some features in Etch, and on the other
hand, there are some unsolved issues left.  These features should be
included in Etch:

 - Mounting /lib/init/rw/ as tmpfs.  Solve libnss-ldap issue, as well
   as make several things easier during the early boot.

 - /dev/shm/ should be mounted without noexec for Etch, to avoid
   problem with user-mode-linux, dosemu and others.

 - Fix for bug in single user detection code for bootlogd.

 - Incorrect error reported from mountnfs.sh and rc.local with VERBOSE
   is set.

There are other fixes included after -20 as well.  The remaining
important issues I am aware of are

 - NFS mounting might fail if ifup -a take up several network
   interfaces, and first interface is insufficient to mount NFS
   partitions.  This is related to moving nfs mounting into if-up.d/
   and trigger mounting when interfaces are enabled. (#393532)

 - fuser might kill the wrong processes during shutdown with there are
   a lot of bind mounted virtual file systems. (#391375)

 - Booting will fail on machines with NFS-mounted / when using ifup to
   re-enable the network and activate NFS mounts, and NFS mounts of
   non-root file systems will not appear if ifup isn't used.  This
   might actually be a problem in ifupdown taking down eth0 before
   reconfiguring it. (#388761)

I'm not sure how to properly solve these while also solving the
problem the change was intended to solve.

An option might be to revert the NFS-related changes and reintroduce
them after Etch is released.  I already reverted the /dev/shm/ mount
option changes for similar reasons.  Opinions?

I am currently very busy preparing the free software prize here in
Norway, so it would be great with help to work on these issues.

Friendly,
-- 
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to