Re: Update re: read-only root filesystem

2003-06-24 Thread Ola Lundqvist
Hello On Sat, Jun 21, 2003 at 01:12:20PM +0200, Thomas Hood wrote: > Some progress has been made toward the goal of making > Debian easier to use with a read-only root filesystem. > Action has been taken to remove variable files from /etc/, > or at least to make it possible to do so locally, in th

Re: Update re: read-only root filesystem

2003-06-22 Thread Steve Langasek
On Sun, Jun 22, 2003 at 11:16:54AM +0200, Xavier Roche wrote: > > this is not a problem due to devpts filesystem. > Okay, using devfs it works perfectly. > A remaining problem is also Samba: > [2003/06/22 11:09:07, 0] passdb/machine_sid.c:pdb_generate_sam_sid(85) > unable to open or create fil

Re: Update re: read-only root filesystem

2003-06-22 Thread Matthew Garrett
Thomas Hood wrote: >No need. It is sufficient that /tmp/ and /dev/ be separate, writable, >filesystems. It is a local decision whether to make these tmpfs and >devfs, respectively. I've successfully run without a writeable dev but with devptsfs. How much "writeability" is required depends on ho

Re: Update re: read-only root filesystem

2003-06-22 Thread Marco d'Itri
On Jun 22, Xavier Roche <[EMAIL PROTECTED]> wrote: >[2003/06/22 11:13:11, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(237) > startsmbfilepwent_internal: failed to set 0600 permissions on password file > /etc/samba/smbpasswd. Error was Read-only file system > .unable to open passdb database.

Re: Update re: read-only root filesystem

2003-06-22 Thread Marco d'Itri
On Jun 22, Xavier Roche <[EMAIL PROTECTED]> wrote: >Dunno.. shall we consider devfs and tmpfs as standard (which is IMHO a >good idea) for future releases? For your ro-root system: definitely yes. For debian, don't dare. -- ciao, | Marco | [1679 corp.qbtCr/Hg]

Re: Update re: read-only root filesystem

2003-06-22 Thread Marco d'Itri
On Jun 22, Thomas Hood <[EMAIL PROTECTED]> wrote: >The question is: Should we concede that a separate /dev/ fs is >required for running with a read-only root filesystem, or should we >take steps to eliminate fiddling with /dev/ files? I haven't Yes. Consoles *must* have their ownership changed

Re: Update re: read-only root filesystem

2003-06-22 Thread Thomas Hood
On Sun, 2003-06-22 at 11:52, Xavier Roche wrote: > Another remark for the HOWTO : mounting /tmp in "tmpfs" (since 2.4.1 ?) > allows you not to resevre space for /tmp on a specific partition Remark added. > > The question is: Should we concede that a separate /dev/ fs is > > required for running w

Re: Update re: read-only root filesystem

2003-06-22 Thread David Weinehall
On Sun, Jun 22, 2003 at 11:52:45AM +0200, Xavier Roche wrote: > > To tell the truth, I didn't realize that so many files in /dev/ > > were being fiddled. Obviously, one solution to the problem is > > to have a separate writable /dev/ filesystem, e.g., devfs. > > Note that devfs is still "experime

Re: Update re: read-only root filesystem

2003-06-22 Thread Martijn van Oosterhout
On Sun, Jun 22, 2003 at 11:32:57AM +0200, Thomas Hood wrote: > On Sun, 2003-06-22 at 01:02, Xavier Roche wrote: > > There are other problems : for example it seems that the system > > changes the /dev/ttyXX or /dev/pts/XX ownership depending on who is being > > logged in.. > > To tell the truth

Re: Update re: read-only root filesystem

2003-06-22 Thread Xavier Roche
> To tell the truth, I didn't realize that so many files in /dev/ > were being fiddled. Obviously, one solution to the problem is > to have a separate writable /dev/ filesystem, e.g., devfs. Note that devfs is still "experimental" in 2.4 Another remark for the HOWTO : mounting /tmp in "tmpfs" (s

Re: Update re: read-only root filesystem

2003-06-22 Thread Thomas Hood
On Sun, 2003-06-22 at 01:02, Xavier Roche wrote: > There are other problems : for example it seems that the system > changes the /dev/ttyXX or /dev/pts/XX ownership depending on who is being > logged in.. To tell the truth, I didn't realize that so many files in /dev/ were being fiddled. Obvio

Re: Update re: read-only root filesystem

2003-06-22 Thread Xavier Roche
> this is not a problem due to devpts filesystem. Okay, using devfs it works perfectly. A remaining problem is also Samba: [2003/06/22 11:09:07, 0] passdb/machine_sid.c:pdb_generate_sam_sid(85) unable to open or create file /etc/samba/MACHINE.SID. Error was Read-only file system So actually s

Re: Update re: read-only root filesystem

2003-06-21 Thread Bernd Eckenfels
On Sun, Jun 22, 2003 at 01:02:55AM +0200, Xavier Roche wrote: > or /dev/pts/XX ownership depending on who is being > logged in.. this is not a problem due to devpts filesystem. It may be a problem for /dev/cdrom. You can ignore it (use a sane cdrom group) or you can use dev filesystem. For the

Re: Update re: read-only root filesystem

2003-06-21 Thread Xavier Roche
[I'm CC'ing to the debian-devel list] Thomas Hood wrote: >>Another small problem occurs when trying to keep /dev in ro: >># /etc/init.d/sysklogd start >>Starting system log daemon: syslogdchmod: changing permissions of >>`/dev/xconsole': Read-only file system > > This occurs when /etc/init.d/sysk

Re: Update re: read-only root filesystem

2003-06-21 Thread Xavier Roche
[I hope I did not sent twice this mail] > Packages that still employ variable files in /etc/ include: > mount, ifupdown, dhcpcd, linuxlogo, ppp, util-linux. > Fortunately, some of the files can be replaced by symlinks. > See my README file at > http://panopticon.csustan.edu/thood/readonly-root

Re: Update re: read-only root filesystem

2003-06-21 Thread Xavier Roche
> Packages that still employ variable files in /etc/ include: > mount, ifupdown, dhcpcd, linuxlogo, ppp, util-linux. > Fortunately, some of the files can be replaced by symlinks. > See my README file at > http://panopticon.csustan.edu/thood/readonly-root.html > for (incomplete) information. >