Re: filename too long???
Theo PAGTZIS wrote: > Hi, > > I have the following fstab file > > # DeviceMountpoint FStype Options Dump > Pass# > /dev/wd0s1b noneswapsw 0 > 0 > /dev/wd0s1a / ufs rw 1 > 1 > /dev/wd0s1f /usrufs rw 2 > 2 > /dev/wd0s1e /varufs 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 rw0 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
Re: psmintr
There was a bug that caused this not too long ago. Try resupping & rebuilding. > > Forgot to mention, it's a 4.1-stable box (PIII-450, 256MB ram, 1024MB > swap) > > On Wed, 23 Aug 2000, FengYue wrote: > > > > > Hi, what does "psmintr: out of sync ( != 0008)." mean? > > I got tons of this message on my console and then my X-window went > > nearly dead. > > > > sounds like my PS/2 mouse's problem? Found the source code in isa/psm.c, > > but have not got any clue what could have caused this. (Have had this > > mouse for last 2 years). > > > > Thanks! > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
fbsd box acting as a wavelan BS
Hi all, Has anyone managed to configure a fbsd box as a Wavelan BS ? Theo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
nfs mount problem
Hello, I am running FreeBSD 4.1. I have made an NFS mount. server:/some/partition /mnt nfs rw 2 2 If I start to bring over files from that mount partition (/mnt) to a local directory, say /some/other/directory, it times out if I open up another terminal and type ls in /some/other/directory.I am not sure if there is something I can put in my fstab to help from this timing out problem. I have read the man pages for mount_nfs and nfsd. Any suggestions? Jason Kraft To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fbsd box acting as a wavelan BS
On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: > Hi all, > > Has anyone managed to configure a fbsd box as a Wavelan BS ? yes it's easy. which wavelan card are you using? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Fwd: kern.ipc.maxsockbuf setting does not work
So I have tracked down the bug to the fact in /sys/kern/uipc_socket2.c of this code fragment in sbreserver(): if ((u_quad_t)cc > (u_quad_t)sb_max * MCLBYTES / (MSIZE + MCLBYTES)) return (0); So why is the test not just this: if ((u_quad_t)cc > (u_quad_t)sb_max) return (0); - JimP -- Forwarded Message -- Subject: kern.ipc.maxsockbuf setting does not work Date: Thu, 24 Aug 2000 10:21:02 -0700 From: Jim Pirzyk <[EMAIL PROTECTED]> I am running a 4.1-RELEASE i386 system and I am trying to increase the maxsockbuf size so I set it in /etc/sysctl.conf like this: kern.ipc.maxsockbuf=524288 And on bootup I see kern.ipc.maxsockbuf: 262144 -> 524288 but when I try to use a larger buffer I get: pirzyk@snoopy:/sys/kern 10>ttcp -r -w512 ttcp-r: buflen=65536, nbuf=2048, align=16384/0, port=5001, sockbufsize=524288 tcp ttcp-r: socket ttcp-r: setsockopt: sndbuf: No buffer space available errno=55 But this should work. Seems the kernel is keeping the old value of 262144. Now I can change it in /usr/include/sys/socketvar.h (SB_MAX) and rebuild the kernel but I do not think this is what was designed. - JimP -- --- @(#) $Id: dot.signature,v 1.9 2000/07/10 16:43:05 pirzyk Exp $ __o [EMAIL PROTECTED] - _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) --- -- --- @(#) $Id: dot.signature,v 1.9 2000/07/10 16:43:05 pirzyk Exp $ __o [EMAIL PROTECTED] - _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
delayed write question
I am wondering what exactly will happen if a delayed write goes wrong. It seems to me that the kernel will just clear the error flag and mark the buffer as delayed write again. This gives the buffer a second chance. But how many chances at most a buffer can get before it is aborted. While this may seem not serious on a local filesystem. Consider the NFS case, if a delayed write to a NFS server fails, how many times will we retry? My understanding is that the user program will not notice these retries or aborts until it closes the file. Am I right? Please clarify this for me. Before 4.0, if we write something to a write-protected floppy, the system will panic. Obviously, this panic does not happen on 4.0+. So I guess that the retries must have a limit. Any help is appreciated. -Zhihui To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: help with restoring sh
On Thu, Aug 24, 2000 at 09:33:37AM +0100, Theo PAGTZIS wrote: > Hi all, > >I have been upgrading from 3.4 to 4.1 and during the reboot I get a > permission denied when it tries to exec the /bin/sh. I am trying to > restore the file with one that is functioning properly..however I do not > know how I should go about correcting my problem. I would appreciate any > help as I am stranded with a server that is down at the moment... With boot -s you on the loader prompt you can boot into single user mode. If asked for the shell to start try /bin/csh which is a different shell and then fix your problem. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: help with restoring sh
Boot from a fix-it floppy and copy it there from the floppy... (and make sure the permissions are correct)... Scot On Thu, 24 Aug 2000, Theo PAGTZIS wrote: > Hi all, > >I have been upgrading from 3.4 to 4.1 and during the reboot I get a > permission denied when it tries to exec the /bin/sh. I am trying to > restore the file with one that is functioning properly..however I do not > know how I should go about correcting my problem. I would appreciate any > help as I am stranded with a server that is down at the moment... > > > Thanks > > Theo > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
help with restoring sh
Hi all, I have been upgrading from 3.4 to 4.1 and during the reboot I get a permission denied when it tries to exec the /bin/sh. I am trying to restore the file with one that is functioning properly..however I do not know how I should go about correcting my problem. I would appreciate any help as I am stranded with a server that is down at the moment... Thanks Theo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
