Re: Problems opening fd for /dev/console...
Ben Collins wrote: > > Odd, mine is: > > crw---1 root root 5, 1 Jun 9 19:52 /dev/console > > So I don't know where your perms problem is coming from. Ahh, wait, your > problem is an exec, not the console. Blah, do this: > > chmod 755 / > > This is a known problem with the May 2.2.15 boot-floppies images. Fixed in > the June set. Thank you!!! Yeah!!! :) Fixed it of course. I used the latest (as of Friday) tftpboot.img since booting off the boot floppies I made locked up as soon as it asked for the ramdisk during the boot sequence -- simply sat there with the prompt asking for the disk. Anyways, thanks... never would have thought of that. Hopefully someone else can find the solution in the mailing list archives now :) Brian Macy
Re: Problems opening fd for /dev/console...
On Mon, Jun 12, 2000 at 06:59:09AM -0700, Brian Macy wrote:
> Ben Collins wrote:
> >
> > > execve("/usr/lib/man-db/man", ["man"], [/* 18 vars */]) = -1 EACCES
> > > (Permission denied)
> > > write(2, "execv: Permission denied\n", 25execv: Permission denied
> > > ) = 25
> > > exit(-13) = ?
> > >
> > > I also get several of these in the strace output but I'm assuming it is
> > > also related to /dev/console.
> >
> > What are the perms on /dev/console? What are the perms also on /dev/ttyS0?
>
> crw--w--w-1 root tty5, 1 Jun 11 22:49 console
> crw--w--w-1 root root 4, 64 Jun 11 23:32 /dev/ttyS0
> crw--w--w-1 root tty4, 0 Jun 11 22:49 /dev/tty0
>
> Tried changing ttyS0 to be owned by group tty but made no difference.
> Which as a side not both stock debian 2.2.15 and my own 2.2.16 exhibit
> the same problems.
Odd, mine is:
crw---1 root root 5, 1 Jun 9 19:52 /dev/console
So I don't know where your perms problem is coming from. Ahh, wait, your
problem is an exec, not the console. Blah, do this:
chmod 755 /
This is a known problem with the May 2.2.15 boot-floppies images. Fixed in
the June set.
--
---===-=-==-=---==-=--
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] '
`---=--===-=-=-=-===-==---=--=---'
Re: Problems opening fd for /dev/console...
Ben Collins wrote:
>
> > execve("/usr/lib/man-db/man", ["man"], [/* 18 vars */]) = -1 EACCES
> > (Permission denied)
> > write(2, "execv: Permission denied\n", 25execv: Permission denied
> > ) = 25
> > exit(-13) = ?
> >
> > I also get several of these in the strace output but I'm assuming it is
> > also related to /dev/console.
>
> What are the perms on /dev/console? What are the perms also on /dev/ttyS0?
crw--w--w-1 root tty5, 1 Jun 11 22:49 console
crw--w--w-1 root root 4, 64 Jun 11 23:32 /dev/ttyS0
crw--w--w-1 root tty4, 0 Jun 11 22:49 /dev/tty0
Tried changing ttyS0 to be owned by group tty but made no difference.
Which as a side not both stock debian 2.2.15 and my own 2.2.16 exhibit
the same problems.
-rwsr-xr-x1 man root89408 Apr 6 19:34
/usr/lib/man-db/man
Brian Macy
Re: Problems opening fd for /dev/console...
> connect(4, {sin_family=AF_INET, sin_port=htons(768),
> sin_addr=inet_addr("63.204.197.52")}}, 16) = 0
> brk(0x29000)= 0x29000
> write(4, "\200\0\0D`\265\253\324\0\0\0\0\0\0\0\2\0\1\206\244\0\0"...,
> 72) = 72
> poll([{fd=4, events=POLLIN, revents=POLLIN}], 1, 25000) = 1
> read(4, "\200\0\2p`\265\253\324\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4000) = 628close(5)= -1 EBADF (Bad file
> descriptor)
> close(4)= 0
> close(3)= 0
> munmap(0x50019000, 8192)= 0
> setgroups(1, [100]) = 0
> setuid(6) = 0
> execve("/usr/lib/man-db/man", ["man"], [/* 18 vars */]) = -1 EACCES
> (Permission denied)
> write(2, "execv: Permission denied\n", 25execv: Permission denied
> ) = 25
> exit(-13) = ?
>
> I also get several of these in the strace output but I'm assuming it is
> also related to /dev/console.
What are the perms on /dev/console? What are the perms also on /dev/ttyS0?
> rt_sigpending(ptrace: umoven: Input/output error
No, just an strace bug.
> Also, first time using a Sun... here's what I found with the latest
> potato:
> - pump doesn't get run at startup... no resolv.conf, etc
File a bug on pump, and try to see what is causing it to fail it's startup
script.
> - no libnss1-compat available
That's because we never released sparc with libc6 2.0 :) That's the only
reason for libnss1-compat on other archs.
Ben
--
---===-=-==-=---==-=--
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] '
`---=--===-=-=-=-===-==---=--=---'
