Re: Solved: Re: chroot issues with accessing /dev/ entries

2008-04-28 Thread Hannah Schroeter
Hi! On Sun, Apr 27, 2008 at 04:47:53PM +0200, Torsten wrote: >>>OK, thank you, that got me onto the right track, now I think I know what >>>the problem is: mount_mfs. >>>/sbin/mount_mfs -s 9 swap /mnt >>>Is there a way to have devices under that mountpoint? >>Of course, just mknod(8) them (ea

Solved: Re: chroot issues with accessing /dev/ entries

2008-04-27 Thread Torsten
OK, thank you, that got me onto the right track, now I think I know what the problem is: mount_mfs. /sbin/mount_mfs -s 9 swap /mnt Is there a way to have devices under that mountpoint? Of course, just mknod(8) them (each time after creating the mfs), Thanks everybody for your help. For wha

Re: chroot issues with accessing /dev/ entries

2008-04-27 Thread Torsten
I am setting up an embedded system that's supposed to run from RAMDISK only. You really should not do this. The RAMDISK kernel uses the SMALL_KERNEL option, and this can have all sorts of unknown effects. I appreciate you comment, but it seems I'm missing something or there's a misunderstand

Re: chroot issues with accessing /dev/ entries

2008-04-27 Thread Theo de Raadt
> >> I am setting up an embedded system that's supposed to run from RAMDISK > >> only. > > > > You really should not do this. The RAMDISK kernel uses the > > SMALL_KERNEL option, and this can have all sorts of unknown effects. > > I appreciate you comment, but it seems I'm missing something or

Re: chroot issues with accessing /dev/ entries

2008-04-26 Thread Theo de Raadt
> I am setting up an embedded system that's supposed to run from RAMDISK > only. You really should not do this. The RAMDISK kernel uses the SMALL_KERNEL option, and this can have all sorts of unknown effects. It is castrated Unix, for the purpose of installation. For now, what that option chang

Re: chroot issues with accessing /dev/ entries

2008-04-26 Thread Hannah Schroeter
Hi! On Sat, Apr 26, 2008 at 05:51:22PM +0200, Torsten wrote: >>># tcpdump >>>tcpdump: Failed to open bpf device for fxp0: Device not configured >>Is /tmp mounted "nodev"? >OK, thank you, that got me onto the right track, now I think I know what >the problem is: mount_mfs. >This is how I set up

Re: chroot issues with accessing /dev/ entries

2008-04-26 Thread Mike Erdely
On Sat, Apr 26, 2008 at 05:51:22PM +0200, Torsten wrote: > Is there a way to have devices under that mountpoint? If you mount it without "nodev", refer to MAKEDEV(8). -ME

Re: chroot issues with accessing /dev/ entries

2008-04-26 Thread Torsten
# tcpdump tcpdump: Failed to open bpf device for fxp0: Device not configured Is /tmp mounted "nodev"? OK, thank you, that got me onto the right track, now I think I know what the problem is: mount_mfs. This is how I set up the ramdisk: /sbin/mount_mfs -s 9 swap /mnt Is there a way to

Re: chroot issues with accessing /dev/ entries

2008-04-26 Thread Mike Erdely
On Sat, Apr 26, 2008 at 03:58:25PM +0200, Torsten wrote: > # tcpdump > tcpdump: Failed to open bpf device for fxp0: Device not configured Is /tmp mounted "nodev"? Look at mount(8). -ME