Hi! On 11/13/06, Gerrit Pape <[EMAIL PROTECTED]> wrote:
mingetty has a workaround for readonly /dev filesystems, maybe that's the problem you have. Could you try the attached patch?, I would apply a similar workaround if it works for you:
No. It isn't working. I don't know if it's good or bad, but now there aren't messages saying that couldn't chow/chmod tty (using both the unpatched and the patched version of fgetty). I am using the same Kernel as before (but maybe some package was updated) Everything runs fine and when fgetty is going to be started, it just doesn't appear. What is happening on tty1 is: (...) Checking battery state... Running local boot scripts (/etc/rc.local). And then nothing else (fgetty was supposed to start after rc.local, right?) On other ttys they just stay black. So I put some "write" to see where fgetty was stopping. Running "fgetty" inside a terminal emulator: ***1***Segmentation fault (1 is on line 266 of the patched fgetty.c) And "fgetty tty3", as normal user and inside the terminal emulator: ***1******2******3******4***could not chown/chmod tty device So it looks that fgetty is working. But rebooting the computer, nothing is displayed, as before. It looks that fgetty isn't being called? (or it's dying before my write). With Debian's Kernel if prints my numbers and works OK. mingetty is always working (with any Kernel). fgetty was compiled on an updated unstable chroot (using pbuilder) and my system is an updated unstable too. Thank you! Best regards, Nelson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
