**** ME:
>I've just installed SLS 99p9 on my 486DLC and I am getting a few puzzling
>messages at boot time. Firstly, there is a "This is an uncheck file system.
>Please run e2fsck" warning, which I cannot get rid of. I have run e2fsck
>several times now - successfully, as far as I can tell, but still the
>message won't go away. Are there some options I need to give?
---- cam:
I get this and ignore it. I think you have to do a fsck while the
file system is unmounted. (BTW, I know I shouldn't really ignore it but
I know the fs isn't corrupt!)
---- doolitt:
I can't figure that one out either. If you get an answer, would you
e-mail it to me? The noise level is still quite high, and I might
miss it if you post it.
---- peterc:
Yes --
e2fsck -rv /dev/???
to repair the disc, as well as check it.
Anyway, with pl9 if you're using ext2fs for the root partition, it
doesn't unmount root at the last, so you'll get the message again next
time round. Upgrade to pl12, and use the latest bootutils, arrange to
boot with a readonly root and check it then.
---- bam:
No it doesn't go away. Not unless you get pl10 or pl11 and bootutils.
**** ME:
> Later, there was a message about inetd, claiming that it couldn't find an
> /etc/inet directory. I created this dir, and the complaint disappeared, but
> a whole new batch appeared for named - claiming that it could find the
> various named.* files anymore.
---- peterc:
You need to configure named.
---- bam:
The net stuff in pl9 was highly questionable your best bet is forget
it and get pl10 or 11
**** ME:
> Emacs gives me a segmentation fault, core dumped when ruN. I suppose I need to
> get an update.
---- doolitt:
Emacs is probably fine, but it might be trying to shared-link to the X libraries.
Do you have X properly installed on your machine? If not, there are binaries
for emacs around that do not require it. Sorry to not be more specific.
---- peterc:
Known problem -- the emacs distributed with SLS is broken.
**** ME:
>I can't do anything with the /dev/modem device, as it claims that the device
>is in use all the time. I can, however, use the /dev/ttyS1.
---- doolitt:
Sometimes permissions on the serial ports get messed up. Check that out.
---- peterc:
I don't know what /dev/modem is -- is it the same as /dev/cua0? (Yes)
---- bam:
My soulution to this is usually ```rm /dev/modem'' and forget it.
Giving ttys multiple names causes trouble with lockfiles.
**** ME:
>I want to set up my modem to be able to login via it. What lines should I
>be putting it which files? Is it possible to set up one of the virtual
>consoles so it can monitor output to the modem line? (And even maybe allow
>input from that console too?)
---- cam:
get getty_ps2.0.7b if you want to do logins via modem - also get the
serial FAQ. If you have problems then talk to me, as I've done it.
No - you can't monitor what is going on with the serial line via the
consoles. That would require modifying the kernel. This was discussed
on c.o.l a while back.
---- doolitt:
I haven't tried modem access, but I hooked up my old 286 as a terminal.
You need to modify /etc/inittab (and then get the init process to reread
it by doing an "init q" as root) to tell it to run "getty" on that terminal
line. You may also need to monkey with /etc/gettydefs, check the man pages if
it doesn't work right away. I recommend against letting modem users login
as root (better to force people to use a real name and then su to root),
but if you have your heart set on it you need to tweak the CONSOLE line in
/etc/login.defs.
---- nygren:
You can get Linux to wait for a serial port logins with the getty command.
(I haven't tried this with Linux, but it should work on most UNIX systems).
Try:
getty /dev/modem
(It defaults to 9600 bps, I think). You will have to set the modem to
auto answer first... There may be a better solution, but....
---- peterc:
Set up getty on /dev/ttyS[01] (whichever you plug it into). In
/etc/inittab. (depending on which version of init you're using).
As far as I know you can't then monitor the output.
---- bam:
I wish I knew. I got this to work with my old 2400baud modem but since
I've upgraded to a fast V32bis modem I can't get Linux to answer the phone.