Re: [Soekris] mounting /dev in RAM in OpenBSD
Chris Cohen wrote: Yes, i know. But, with my cf mounted ro I wasn't able to login via ssh. Yes. I've just tested mounting the CF ro and SSH does indeed not get me through to a shell, even with /tmp and /var each in an mfs. I haven't yet set up a log server to see what the specific errors are, but that's probably not necessary, yet. ... I think someone on misc@ told me to place /dev in an mfs. Did that and everything worked fine... Would you post how you've managed to put /dev into RAM? I've tried a few ways that have each prevented the system from completing its boot process. Regards, -Lars ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] mounting /dev in RAM in OpenBSD
Chris Cohen wrote: Yes, i know. But, with my cf mounted ro I wasn't able to login via ssh. I think someone on misc@ told me to place /dev in an mfs. Did that and everything worked fine. I think openssh needs write access to the ttyp devices. Never occurred to me. Thanks. I would have tripped over that myself I'm sure. Chris -)- -- Implementing CIFS - the Common Internet FileSystem ISBN: 013047116X Samba Team -- http://www.samba.org/ -)- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)- [EMAIL PROTECTED] OnLineBook -- http://ubiqx.org/cifs/-)- [EMAIL PROTECTED] ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] mounting /dev in RAM in OpenBSD - RESOLVED
It looks like the trick was to mount the mfs version of /dev on top of the regular /dev, the system did not like to boot with only a read-only /dev or with only a mount point for /dev Currently the system successfully boots read only and SSHd accepts logins. Below is /etc/fstab for the adjustments I have made to an otherwise plain vanilla OpenBSD 4.2. Later, after Christmas or so, I'll look into adjusting the sizes and such. Have to clean up now for a few days... -Lars /dev/wd0a / ffs ro,noatime 1 1 /dev/wd0d /data ffs rw,nodev,nosuid 1 2 swap /var mfs -P/var.base,-s16000,noexec,async,nosuid,nodev,noatime,rw 0 0 swap /tmp mfs noexec,async,nosuid,nodev,noatime,rw,-b4096,-i1024,-s21200,-m0 0 0 swap /dev mfs rw,-P/dev.orig,-b4096,-i1024,-s21200,-m0,nosuid 0 0 ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] mounting /dev in RAM in OpenBSD
Chris Cohen [EMAIL PROTECTED] wrote: Openssh needs to write to some devices. (Don't know which ones..) sshd wants to change permissions on /dev/ttyXX when you login so that only you can write to it (or your group) - i originally dealt with this in flashdist by making /dev/ttyXX symbolic links to the actual devices at writeable (mfs) /var/run/dev/ttyXX. unfortunately, sshd uses login() to write your login entries to utmp, which fails if ttyname() decides that your device is not an actual character device. this was a problem with flashdist, symbolic links caused ttyname() to fail so utmp was always empty - and then i moved /dev to full mfs ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
