Bug#392209: fgetty: Could not chown/chmod tty device
Hi Gerrit! On 11/15/06, Gerrit Pape <[EMAIL PROTECTED]> wrote: On Tue, Nov 14, 2006 at 10:17:15PM -0200, Nelson A. de Oliveira wrote: > I am just sending this email to say that what I have told you on the > last email keeps the same with the updated fgetty (version 0.6-4). Hmm, that's strange. Can you please post the exact line from your /etc/inittab for starting fgetty? My full inittab is attached. tty1 and tty2 is fgetty and there don't start (while tty3 works normally). Thank you! Regards, Nelson inittab.gz Description: GNU Zip compressed data
Bug#392209: fgetty: Could not chown/chmod tty device
On Tue, Nov 14, 2006 at 10:17:15PM -0200, Nelson A. de Oliveira wrote: > I am just sending this email to say that what I have told you on the > last email keeps the same with the updated fgetty (version 0.6-4). Hmm, that's strange. Can you please post the exact line from your /etc/inittab for starting fgetty? Regards, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392209: fgetty: Could not chown/chmod tty device
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]
Bug#392209: fgetty: Could not chown/chmod tty device
On Fri, Nov 10, 2006 at 08:50:53PM -0200, Nelson A. de Oliveira wrote:
> Hi Gerrit!
>
> On 11/10/06, Gerrit Pape <[EMAIL PROTECTED]> wrote:
> >unfortunately I cannot teproduce the problem. On a current sid system,
> >your inittab entry works just fine for me. Did you change anything
> >special on your system, such as security patches to the kernel, extended
> >access permissions/restrictions or similar?
>
> The Kernel... the only thing that I change here is the Kernel. And
> booting with Debian's Kernel fgetty works without problem. The guilty
> is my 2.6.18-mm1 Kernel! :-)
Hi Nelson, thanks for checking this.
> The strange thing is that mingetty works here (and fgetty is derivated
> from mingetty). But anyway, you can close this bug.
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:
$ apt-get source fgetty
...
$ cd fgetty-0.6/
$ patch -p0 ? a.out
? test.c
Index: fgetty.c
===
RCS file: /cvs/fgetty/fgetty.c,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 fgetty.c
--- fgetty.c16 Feb 2004 10:07:55 - 1.1.1.1
+++ fgetty.c13 Nov 2006 14:11:40 -
@@ -76,8 +76,12 @@
void open_tty() {
struct sigaction sa;
int fd;
- if (chown(tty,0,0) || chmod(tty,0600))
-error("could not chown/chmod tty device\n",1);
+ if (chown(tty,0,0) || chmod(tty,0600)) {
+if (errno==EROFS)
+ write(2,"fgetty: warning: could not change owner/permissions of tty:
readonly filesystem\n",80);
+else
+ error("could not chown/chmod tty device\n",1);
+ }
sa.sa_handler=SIG_IGN;
sa.sa_flags=0;
sigemptyset(&sa.sa_mask);
Bug#392209: fgetty: Could not chown/chmod tty device
Hi Gerrit! On 11/10/06, Gerrit Pape <[EMAIL PROTECTED]> wrote: unfortunately I cannot teproduce the problem. On a current sid system, your inittab entry works just fine for me. Did you change anything special on your system, such as security patches to the kernel, extended access permissions/restrictions or similar? The Kernel... the only thing that I change here is the Kernel. And booting with Debian's Kernel fgetty works without problem. The guilty is my 2.6.18-mm1 Kernel! :-) The strange thing is that mingetty works here (and fgetty is derivated from mingetty). But anyway, you can close this bug. Thank you very much for your attention. Best regards, Nelson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392209: fgetty: Could not chown/chmod tty device
tags 392209 + unreproducible thanks. On Tue, Oct 10, 2006 at 04:03:01PM -0300, Nelson A. de Oliveira wrote: > I am trying to use fgetty here on my system, but without success. > > The error messages that appear are: > > could not chown/chmod tty device > (the above message is repeated a lot of times) > INIT: Id "2" respawning too fast: disabled for 5 minutes > > And then I get an unusable console. > > With mingetty and getty it's working normally. > > The config on inittab is: > > 2:2345:respawn:/sbin/fgetty tty2 > > If changing to "2:2345:respawn:/sbin/mingetty tty2" or > "2:2345:respawn:/sbin/getty 38400 tty2" it works. Hi Nelson, unfortunately I cannot teproduce the problem. On a current sid system, your inittab entry works just fine for me. Did you change anything special on your system, such as security patches to the kernel, extended access permissions/restrictions or similar? Regards, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392209: fgetty: Could not chown/chmod tty device
Package: fgetty Version: 0.6-3 Severity: important Hi! I am trying to use fgetty here on my system, but without success. The error messages that appear are: could not chown/chmod tty device (the above message is repeated a lot of times) INIT: Id "2" respawning too fast: disabled for 5 minutes And then I get an unusable console. With mingetty and getty it's working normally. The config on inittab is: 2:2345:respawn:/sbin/fgetty tty2 If changing to "2:2345:respawn:/sbin/mingetty tty2" or "2:2345:respawn:/sbin/getty 38400 tty2" it works. Thank you very much! Best regards, Nelson -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-mm1 Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
