Re: Is inability to operate with root read-only (and separate /etc, /dev, etc) a bug or design decision?

2006-08-16 Thread Peter Samuelson
[Philipp Matthias Hahn] > Which doesn't work because of linux-utils-2.12r/mount/fstab.c:55 As I recall, Andries (util-linux upstream) produced, at least a year ago, a kernel patch which allows the kernel to store an extra string of user data from 'mount', and display it in /proc/mounts, so that n

Re: Is inability to operate with root read-only (and separate /etc, /dev, etc) a bug or design decision?

2006-08-15 Thread Goswin von Brederlow
Philipp Matthias Hahn <[EMAIL PROTECTED]> writes: > Hi! > > On Sat, Aug 12, 2006 at 09:34:52PM +0200, Goswin von Brederlow wrote: >> Peter Samuelson <[EMAIL PROTECTED]> writes: >> >> > [Goswin von Brederlow] >> >> Instead move the things in etc that need writing to other places: >> >> >> >> 1) l

Re: Is inability to operate with root read-only (and separate /etc, /dev, etc) a bug or design decision?

2006-08-14 Thread Philipp Matthias Hahn
Hi! On Sat, Aug 12, 2006 at 09:34:52PM +0200, Goswin von Brederlow wrote: > Peter Samuelson <[EMAIL PROTECTED]> writes: > > > [Goswin von Brederlow] > >> Instead move the things in etc that need writing to other places: > >> > >> 1) link /etc/mtab to /proc/mounts and create a dummy /proc/mounts

Re: Is inability to operate with root read-only (and separate /etc, /dev, etc) a bug or design decision?

2006-08-13 Thread Jörg Sommer
Hello Peter, Peter Samuelson <[EMAIL PROTECTED]> wrote: > > [Goswin von Brederlow] >> Instead move the things in etc that need writing to other places: >> >> 1) link /etc/mtab to /proc/mounts and create a dummy /proc/mounts on / >>for when /proc isn't mounted (works with quota in current kern

Re: Is inability to operate with root read-only (and separate /etc, /dev, etc) a bug or design decision?

2006-08-12 Thread Goswin von Brederlow
Peter Samuelson <[EMAIL PROTECTED]> writes: > [Goswin von Brederlow] >> Instead move the things in etc that need writing to other places: >> >> 1) link /etc/mtab to /proc/mounts and create a dummy /proc/mounts on / >>for when /proc isn't mounted (works with quota in current kernels). > > Does

Re: Is inability to operate with root read-only (and separate /etc, /dev, etc) a bug or design decision?

2006-08-12 Thread Peter Samuelson
[Goswin von Brederlow] > Instead move the things in etc that need writing to other places: > > 1) link /etc/mtab to /proc/mounts and create a dummy /proc/mounts on / >for when /proc isn't mounted (works with quota in current kernels). Does the wrong thing with (a) user and (b) loop mounts.

Re: Is inability to operate with root read-only (and separate /etc, /dev, etc) a bug or design decision?

2006-08-12 Thread Goswin von Brederlow
Daniel Dickinson <[EMAIL PROTECTED]> writes: > A little while back I tried to setup a system that used a read-only > root filesystem during regular operation and ran into some problems > during boot. The first is that /etc needs to be read-write but init > scripts break badly if /etc is not on th

Re: Is inability to operate with root read-only (and separate /etc, /dev, etc) a bug or design decision?

2006-08-12 Thread Marco d'Itri
On Aug 12, Daniel Dickinson <[EMAIL PROTECTED]> wrote: > A little while back I tried to setup a system that used a read-only > root filesystem during regular operation and ran into some problems > during boot. The first is that /etc needs to be read-write but init > scripts break badly if /etc is

Is inability to operate with root read-only (and separate /etc, /dev, etc) a bug or design decision?

2006-08-12 Thread Daniel Dickinson
A little while back I tried to setup a system that used a read-only root filesystem during regular operation and ran into some problems during boot. The first is that /etc needs to be read-write but init scripts break badly if /etc is not on the root filesystem (probably could be fixed in initramf