--- In "jcunningham63" <> wrote:
>
> --- In Triffid Hunter <triffid_hunter@> wrote:
> >
> > On Wed, 26 Dec 2007, Jeff Cunningham wrote:
> >
> > > Hi Triffid,
> > >
> > > Thanks for the info. I don't have a video card so presumably I
> need no
> > > virtual consoles. But how do I change /etc/inittab to refer
terminals
> > > that actually exist? I'm looking at it and it is currently set up
> like
> > > this:
> > >
> > > 1:2345:respawn:/sbin/getty 38400 tty1
> > > T0:23:respawn:/sbin/getty -L ttyAM0 115200 vt100
> > > T1:23:respawn:/sbin/getty -L ttyAM1 115200 vt100
> > >
> > > Doesn't that mean it should be generating /dev/tty1?
> >
> > No, that tells it to use tty1 which doesn't exist, hence it exits
> with an
> > error, but it's set to respawn so init restarts it. Since init isn't
> > stupid, it gives up after a bit and generates the message seen in
your
> > logs. Simply removing or commenting the entry that refers to the
> > nonexistent node should stop the message appearing.
> >
> > > I don't think I'm running dropbear ssh. I installed the latest
stable
> > > version with apt-get when running debian:
> > >
> > > :dev# ssh -v
> > > OpenSSH_4.3p2 Debian-9, OpenSSL 0.9.8c 05 Sep 2006
> > >
> > > But for all I know it has the same requirement as dropbear.
> >
> > yes it does.
> >
> > > So how do I mount a tmpfs over /dev at boot before starting udev?
> I know
> > > just enough about udev to be dangerous.
> >
> > depends how and where udev is started.. I'm surprised it's not
done for
> > you already. Either add it to whichever script starts udev, or
> create your
> > own and ensure it runs before the one that starts udev.
> >
> > That's not your problem though - you get other nodes such as ttyAM0.
> The
> > part you need to sort out is creating and mounting /dev/pts before
sshd
> > and/or telnet start.
> >
>
> I tried advancing the ssh startup script from S21 to S22 (past the nfs
> stuff and way past the udev stuff), but that didn't help. It looks to
> me like /dev/pts is definitely created and mounted prior to ssh being
> launched.
>
> I can see I'm way over my head on this udev problem. Without some more
> specific instructions on how to fix it I guess I'll have to chalk it
> up to being "not ready for prime time" and go back to the 2.4 kernel.
> I've spent the better part of the last three days on this and I'm not
> much closer than I was when I started. If I can't SSH into the box I
> can't use it. I don't understand how the tarballs on the 2.6 page at
> TS could work for anyone though without modification. The sarge-udev
> root file system can't work with SSH as is.
>
> Thanks for all your help anyway.
>
> --Jeff
>
I ran into the same issue and just found a solution. You need to make
a small edit to /etc/fstab to mount devpts with default options:
none /dev/pts devpts defaults 0 0
this is now working for me at least.
- Doug
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|