Theo PAGTZIS wrote: > Hi, > > I have the following fstab file > > # Device Mountpoint FStype Options Dump > Pass# > /dev/wd0s1b none swap sw 0 > 0 > /dev/wd0s1a / ufs rw 1 > 1 > /dev/wd0s1f /usr ufs rw 2 > 2 > /dev/wd0s1e /var ufs rw 2 > 2 > /dev/wcd0c /mnt/cdrom cd9660 ro,noauto 0 > 0 > /dev/fd0 /mnt/floppy msdos rw,noauto 0 > 0 > proc /proc procfs rw 0 > 0 > > # you want to get the essential ports in one place to do one build and > multi installs - faster > starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_port_pool > /usr/pool nfs rw 0 0 > starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/master_distfiles_ports > /usr/ports/distfiles nfs rw 0 0 > > # this needs a soft link on the mounted folder, on the root dir > >starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_config/elikonas > /backupETC nfs rw 0 0 > > When I try to mount these stores I get : > > nfs: > starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_port_pool: > File name too long > nfs: > starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/master_distfiles_ports: > File name too long > nfs: > >starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_config/elikonas: > File name too long > > This was not the case with Fbsd 3.4 > > Why is this happening? Is it because of the device name change because > the machine boots fine without asking for an ad0 device set > > Theo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
