Re: what the heck is ftime and why is the reference undefined???????
See the manpage on ftime(3) (especially the first and second lines of DESCRIPTION) - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BIOS statistics
On Thu, 7 Sep 2000, Jason Kraft wrote: Is there any way to gather BIOS statistics within FreeBSD? I would like to monitor internal CPU temperature, and fan speeds. When I go into the BIOS menu, I can see these statistics, but don't really do any good since most of these gauge values rise after the machine has been on for long periods of time. lmmon, wmlmmon, consolehm, wmhm, healthd (in ports/sysutils) - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: freebsd port of netboot?..
On Tue, 29 Aug 2000, Christopher Stein wrote: .. does anyone know if this exists? It would speed up the panic-edit-compile-boot-copy-boot kernel hacking cycle by transforming it to panic-edit-compile-netboot. Does this help? jedgar@splat:/usr/ports$ make search key=netboot Port: etherboot-4.6.1 Path: /usr/ports/net/etherboot Info: Netboot FreeBSD a.out/ELF kernels Maint: [EMAIL PROTECTED] Index: net B-deps: gettext-0.10.35 gmake-3.79.1 nasm-0.98 R-deps: - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 2 inetd's with 2 nics
On Sun, 13 Aug 2000, Leif Neland wrote: Is it possible and a good idea to have one inetd for the inside nic and another with fewer services for the outside on a gateway machine, or should I just use ipfw/ipchain for this? Depends on why you want them separate. You could use the -a option to run separate instances or use tcp_wrappers (integrated in inetd), ipf, or ipfw to limit acccess. - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How do I change serial console tty speed?
On Tue, 8 Aug 2000, Bob Willcox wrote: Hi All, I have tried everything I could think of to raise the speed of my system's serial console from 9600 baud to something faster w/o any success. The things that I have tried are: setting "options CONSPEED=38400" in my kernel config file and putting a "set CONSPEED=38400" in the /boot/loader.rc file to no avail. See /etc/defaults/make.conf WRT BOOT_COMCONSOLE_SPEED, set the appropriate value in /etc/make.conf, and compile/install the boot blocks. - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: God I feel stupid (gcc issue)
On Tue, 8 Aug 2000, Laurence Berland wrote: So I thought, "we don't define __GNUC__?" I figured I'd check. After much mind wracking, I can't for the life of me figure out how to get gcc to output a list of what is and isnt defined by default... help! From 4.1-STABLE: jedgar@wopr:~$ cpp -v Using builtin specs. gcc version 2.95.2 19991024 (release) /usr/libexec/cpp -lang-c -v -Di386 -Dunix -D__FreeBSD__=4 -D__FreeBSD_cc_version=41 -D__i386__ -D__unix__ -D__FreeBSD__=4 -D__FreeBSD_cc_version=41 -D__i386 -D__unix -Acpu(i386) -Amachine(i386) -Asystem(unix) -Asystem(FreeBSD) -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -D__ELF__ - GNU CPP version 2.95.2 19991024 (release) (i386 FreeBSD/ELF) *snip* ----- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.1 ISO CRC
On Wed, 2 Aug 2000, Dimitar Peikov wrote: Hi, Could someone send me CRC code for the 4.1 ISO image or to be available on ftp server for downloading? Is something wrong with CHECKSUM.MD5 that sits alongside 4.1-install.iso at ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/ - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: UFS inodes readig ...
On Wed, 19 Jul 2000, Dmitry samersoff wrote: Please Help! Does anyone have simple code reading ufs partion inode-by-inode with inode description too? (My designer remove some very significant files and it's my last chance ;-(( ) fsdb(8) - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: RELENG_4 build broken?
On Thu, 13 Jul 2000, Rene de Vries wrote: Hello, Today and yesterday I tried to build a freshly cvsup-ed RELENG_4 source tree, both builds failed. Did I forget/miss something, or did someone break the build? You seem to have missed a couple dozen messages regarding this problem and the working solution(s) provided (though not committed). In addition, problems with the -STABLE branch should go to [EMAIL PROTECTED], not -hackers. - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ld static search path?
On Tue, 11 Jul 2000, Matthew Hagerty wrote: Greetings, I posted this to questions, but have not received any reply. I was hoping someone here in hackers could help... Thanks. Original Post - Could someone tell me how I can find out what the *static* search path for ld is? Also, how can I add my own directories to the static search path? If you are speaking of static libraries, I believe it defaults to /usr/lib. When compiling use the -L flags to specify other dirs (e.g. -L/usr/local/lib -lmylib). - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: libnsl and libdl not found.
On Thu, 22 Jun 2000, Bageshri Kundu wrote: Hi, I am porting some MPLS conformance tester code from Linux to Free BSD which needs libnsl libdl to be linked in. When I do a make, I get the error saying that these 2 files are not found and nor do they seem to be present in the machine. Doesn't FreeBSD come with these libraries? Otherwise is there a way to get these from somewhere? How is dynamic linking done on Free BSD without libdl? Built into libc...just remove the -lxxx - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: i have 4 pwd.db
On Thu, 18 May 2000, Daniel C. Sobral wrote: Dylan parker wrote: I want desencrypt the files pwd.db Help me please Password files are not decryptable by design. And encrypted passwords are not stored in pwd.db (see spwd.db) - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BROKEN_KEYBOARD_RESET
On Fri, 12 May 2000, Warner Losh wrote: In message [EMAIL PROTECTED] FreeBSD MAIL writes: : Is this the kernel setting to dislable ctrl-alt-delete from resetting : a systtem? If so it seems to be broken in 4.0-RELEASE. : is there another way of doing this? remaping keyboard perhaps? : : # BROKEN_KEYBOARD_RESET disables the use of the keyboard controller to : # reset the CPU for reboot. This is needed on some systems with broken : # keyboard controllers. No. The hot key squence CAD will reboot the system. Or rather it will cause the init process to get a signal that causes it to reboot the system. BROKEN_KEYBOARD_RESET does something different. In the IBM PC and newer compatible machines, the keyboard controller part is connected to a lot of different things, including the reset line to the CPU. Generally one can get a fairly clean reset of the CPU by telling the keyboard controller micro controller to reset the CPU with a nice pulse downt he reset line. Some keyboard controllers didn't think this was important enough to get right, so they don't implement this proplerly. These controllers are generally on the 386 and 486 class of machines and some pentium laptops (exceptions to the rule exist) where the keyboard controller was still a 8042 microcontroller programmed to talk to the keyboard. Since this has been brought up, any reason that BROKEN_KEYBOARD_RESET is not a recognized option (see kern/12927)? - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How to make sure that I compile MD5 based system
On Sat, 8 Apr 2000, Alexey N. Dokuchaev wrote: Hello! I am using FreeBSD 4.0. The thing is, that I want DES sources and libraries hanging around (just in case), but the whole system be MD5 based (including /sbin/init, other utils, and correct links in /lib). I looked at /etc/defaults/make.conf, but didn't and references of this kind, except USA_RESIDENT. So, when making world and stuff, how do I explicitly say to make MD5 system, having *all* the sources, both DES and MD5. Using: #NODESCRYPTLINKS=true # do not replace libcrypt - libscrypt links will ensure your libcrypt is not linked to the des-based libcrypt (libdescrypt). - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How to make sure that I compile MD5 based system
On Sat, 8 Apr 2000, Alexey N. Dokuchaev wrote: On Sat, 8 Apr 2000, Chris D. Faulhaber wrote: On Sat, 8 Apr 2000, Alexey N. Dokuchaev wrote: Hello! I am using FreeBSD 4.0. The thing is, that I want DES sources and libraries hanging around (just in case), but the whole system be MD5 based (including /sbin/init, other utils, and correct links in /lib). I looked at /etc/defaults/make.conf, but didn't and references of this kind, except USA_RESIDENT. So, when making world and stuff, how do I explicitly say to make MD5 system, having *all* the sources, both DES and MD5. Using: #NODESCRYPTLINKS=true # do not replace libcrypt - libscrypt links will ensure your libcrypt is not linked to the des-based libcrypt (libdescrypt). But, AFAIUC, this deals only with libraries. And how about binary executables in /bin, /sbin (e.g., init)? If a program links with libcrypt and libcrypt is linked to libscrypt (MD5 version) instead of libdescrypt (DES version), then that program will use MD5. - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: need help
...redirecting to -questions On Mon, 20 Mar 2000, Mourad Lakhdar wrote: hi every body: when i change in the kernel , i config it , made : make depend while doing make i got the error : /var : write failed , file system is full cpp: /var/tmp/ccT1684.i:No space left on device error code 1 stop so what should i do Remove some files from your /var partition? - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mounting openbsd disks
On Fri, 4 Feb 2000, Warner Losh wrote: I have a need to mount a disk that was partitioned and labeled on OpenBSD. I'm getting the following errors when I try: # disklabel ad2 disklabel: ioctl DIOCGDINFO: Invalid argument root@earth:~# disklabel ad1 disklabel: ioctl DIOCGDINFO: Invalid argument root@earth:~# disklabel /dev/ad1s4 *snip* 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52409704.2BSD 1024 819216 # (Cyl.0 - 519*) b: 1048320 524097 swap# (Cyl. 519*- 1559) c: 164504970unused0 0 # (Cyl.0 - 16319*) e: 262080 15724174.2BSD 1024 819216 # (Cyl. 1559*- 1819) f: 4194288 18344974.2BSD 1024 819216 # (Cyl. 1819*- 5980) root@earth:~# mount /dev/ad1s4a /mnt root@earth:~# ls /mnt .cshrc bootemulroottmp .profilebsd etc sbinusr altroot bsd.old homestand var bin dev mnt sys root@earth:~# - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel modules
On Tue, 1 Feb 2000, Derek White wrote: Hey folks, I just wanted to know if anyone could point out a good online resource like a tutorial or developer guide that explains kernel module development under FreeBSD. See http://thc.pimmel.com/files/thc/bsdkern.html Although not necessarily its indented purpose, this security-related article serves as a fairly complete kld tutorial. I am new to FreeBSD coming from a Linux/BeOS background and am interested in playing around with it to maybe contribute back to the FreeBSD source tree. Maybe this is a dumb question but is developing kernel modules for FreeBSD the same as it is technically for Linux? - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Hardware list idea
On Thu, 2 Dec 1999, Julian Elischer wrote:
Might it be an idea to allow the setup program to have an option
"Send word back to FreeBSD.org that this model of machine works".
or maybe, just a version of send-pr that does that, and uses a different
template:
Laptop: {yes/No}
Manufacturer:
Model:
#If you don't have a model number fill in the following details:
CPU:
SPeed:
BUS bridges:
...
...along with the output of dmesg for better correlation between drivers
and models?
-----
Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never
System/Network Administrator,| claimed they were one, and always
Reality Check Information, Inc. | pointed to someone better.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: wfd0: i/o error, status=51 ready,opdone,check, error=40
On Tue, 2 Nov 1999, Gustavo Vieira Goncalves Coelho Rios wrote: That is the message i get at the console when i try to write some thing in my IDE ZIP drive! Have anyone already faced such a problem ? Does any one here know how to fix it ? Could you provide the relevant part of dmesg WRT to the Zip drive model number. This sounds like what happens when the wfd driver does not properly recognize the Zip drive inquiry string and does not set maxblks to 64 (see PR kern/12095). - Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: wfd0: i/o error, status=51 ready,opdone,check, error=40
On Tue, 2 Nov 1999, Gustavo V G C Rios wrote: "Chris D. Faulhaber" wrote: On Tue, 2 Nov 1999, Gustavo Vieira Goncalves Coelho Rios wrote: That is the message i get at the console when i try to write some thing in my IDE ZIP drive! Have anyone already faced such a problem ? Does any one here know how to fix it ? Could you provide the relevant part of dmesg WRT to the Zip drive model number. This sounds like what happens when the wfd driver does not properly recognize the Zip drive inquiry string and does not set maxblks to 64 (see PR kern/12095). ----- Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. This is what i get from dmesg output: (only relevant part) ... wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): IOMEGA ZIP 100 ATAPI Floppy/14.A, removable, intr, iordis wfd0: medium type unknown (no disk) ppc0 at 0x378 irq 7 flags 0x40 on isa ... That's the same as my problem drive. Apply the patch in the PR for the driver to limit maxblks properly by using a strncmp vs. strcmp. ----- Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Limitations in FreeBSD
On Thu, 28 Oct 1999, Michael Beckmann wrote: Hi ! 1. What is the maximum size of a file on a filesystem ? 2. What is the maximum size of a filesystem ? http://www.freebsd.org/FAQ/install.html#AEN704 - Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NFS /usr/ports
On Tue, 28 Sep 1999, Cillian Sharkey wrote: Hi, When doing a make world upgrade, one can do the compiling on one machine, and then NFS mount /usr/src and /usr/obj from it onto the other machines to do the upgrade, however when doing the same with /usr/ports, it doesn't work quite as well. For example, once you have installed a port on the master machine, you can't do a 'make install' again, unless you delete the file "work/.install_done" for the port in question. Any suggestions ? Try 'make reinstall' ----- Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mrtg,FreeBSD, asus p2b temperature
On Mon, 27 Sep 1999, Leif Neland wrote: Does anybody have any tips for using the above combination for graphing temperatures? You can start with: http://www.fxp.org/~jedgar/lmmon-0.52.tar.gz http://www.fxp.org/~jedgar/wmlmmon-0.52.tar.gz I'm sure you could add snmp hooks in somewhere :) - Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: intpm in STABLE
On Fri, 24 Sep 1999, Ron Rosson wrote: Thank you in replying so promptly. I look forward to seeing it get commited to the STABLE branch. It would be a dream come true to be able to see the temps internally of my servers without having to shutdown and take a look at it thru the bios. If it is not to much trouble or if you need someone to test patches. Please keep me in mind. On a side note, I managed to convince my boss of the potential benefit of monitoring servers in this fashion. He has agreed to allow me to develop a daemon (on company time) for monitoring and logging, BSD licensed even. Personally, I don't want to think about losing the cooling fans in a server with 6 10k RPM U2W drives. :) - Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: help with flaky reboot on 3.1
On Tue, 14 Sep 1999, Stevan Arychuk wrote: Greetings, We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the RELENG_3 branch (used this to take advantage of the KVA modifications that were rolled in after the release). Here are the symptoms we are seeing: 1 machine running a caching squid reverse proxy would spontaneously reboot with no error messages every week or so. This machine was a single CPU only. We were seeing an excessive number of sockets in the CLOSING state, via netstat. The reboots seemed to be co-related to having many such sockets. Suspecting bad TCP stack on the Internet, we did 'sysctl -w net.inet.tcp.always_keepalive=1' This fixed the many CLOSING sockets problem, but did not fix the reboots. Other machines running custom software (Dual CPU) would also spontaneously reboot also with no error messages. The reboots are happening on an increasing frequency, almost to the point of a couple times a day. Sometimes a machine would reboot a couple times a day, then be ok for another week or so. Our software excercies the disk, CPU and network quite a bit, but not excessively. The only machines that are having problems, are production machines directly connected to the Internet. We've had the same machines running internally with longer uptimes, and heavier volumes. Any suggestions/idea's? Sorry about the super-post, I thought detail was important. - Stevan Arychuk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message ----- Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: help with flaky reboot on 3.1
On Tue, 14 Sep 1999, Stevan Arychuk wrote: Greetings, We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the RELENG_3 branch (used this to take advantage of the KVA modifications that were rolled in after the release). Are the kernel and user-land out of sync (kernel sources newer than system sources)? Cheers, Chris p.s. sorry about the prev. reply without comments...Pine's send and cancel keys are too close together :) - Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: help with flaky reboot on 3.1
On Tue, 14 Sep 1999, Stevan Arychuk wrote: Greetings, We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the RELENG_3 branch (used this to take advantage of the KVA modifications that were rolled in after the release). Here are the symptoms we are seeing: 1 machine running a caching squid reverse proxy would spontaneously reboot with no error messages every week or so. This machine was a single CPU only. We were seeing an excessive number of sockets in the CLOSING state, via netstat. The reboots seemed to be co-related to having many such sockets. Suspecting bad TCP stack on the Internet, we did 'sysctl -w net.inet.tcp.always_keepalive=1' This fixed the many CLOSING sockets problem, but did not fix the reboots. Other machines running custom software (Dual CPU) would also spontaneously reboot also with no error messages. The reboots are happening on an increasing frequency, almost to the point of a couple times a day. Sometimes a machine would reboot a couple times a day, then be ok for another week or so. Our software excercies the disk, CPU and network quite a bit, but not excessively. The only machines that are having problems, are production machines directly connected to the Internet. We've had the same machines running internally with longer uptimes, and heavier volumes. Any suggestions/idea's? Sorry about the super-post, I thought detail was important. - Stevan Arychuk To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message - Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: help with flaky reboot on 3.1
On Tue, 14 Sep 1999, Stevan Arychuk wrote: Greetings, We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the RELENG_3 branch (used this to take advantage of the KVA modifications that were rolled in after the release). Are the kernel and user-land out of sync (kernel sources newer than system sources)? Cheers, Chris p.s. sorry about the prev. reply without comments...Pine's send and cancel keys are too close together :) - Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
More press
There is a short but sweet[1] article on ZDNet today regarding FreeBSD: http://www.zdnet.com/zdtv/screensavers/answerstips/story/0,3656,2324624,00.html Not too in-depth, but it gives a good quick overview, calling FreeBSD a true Unix, emphasizing it's history compared to Linux. - Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
More press
There is a short but sweet[1] article on ZDNet today regarding FreeBSD: http://www.zdnet.com/zdtv/screensavers/answerstips/story/0,3656,2324624,00.html Not too in-depth, but it gives a good quick overview, calling FreeBSD a true Unix, emphasizing it's history compared to Linux. - Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: The usage of MNT_RELOAD
On Wed, 8 Sep 1999, Zhihui Zhang wrote: On Wed, 8 Sep 1999, Luoqi Chen wrote: The flag MNT_RELOAD is not documented in mount manpages. From the source code, I find that it is always used along with MNT_UPDATE which can be speficied by user (-u option). Can anyone explain the usage of MNT_RELOAD for me? It seems not to be used normally. It is created almost exclusively for fsck (and similar programs) to update the in core image of the superblock (of / in single user mode) after the on disk version has been modified. Does fsck have to run on a MOUNTED filesystem? If so, your answer makes sense to me: if fsck modifies the on-disk copy of the superblock, it does not have to unmount and then remount the filesystem, it only need to reload the superlock for disk. Filesystems do not have to be mounted to fsck them (in fact, it is generally bad to have them mounted rw when fsck'd); however, in order for the root filesystem to be fsck'd on boot, it must be mounted ro in order to access the fsck program itself. After done fsck'ing, it can remount rw for normal operation, done without actually unmounting the filesystem. - Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [mount.c]: Option user-patch
On Sun, 29 Aug 1999, Natty Rebel wrote:
Quoting JK3 ([EMAIL PROTECTED]):
vs I whacked mount and umount into shape for using an option "user" in
[snip]
vs http://www-i2.informatik.rwth-aachen.de/~stolz/mount.diff
vs http://www-i2.informatik.rwth-aachen.de/~stolz/umount.diff.
vs Discussion welcome!
You can allow non-root users to mount and unmount devices if
the sysctl variable "vfs.usermount" is set to "1".
For example, here's what you need to do to allow floppies to
be mounted:
As `root':
1. # chmod 777 /dev/fd0 # give perms to access the device
2. # sysctl -w vfs.usermount=1
Now users can mount and umount the floppies:
3. $ mkdir ~/my-mount-point
4. $ mount -t msdos /dev/fd0 ~/my-mount-point
5. $ umount ~/my-mount-point
A FAQ entry covering this point is being reviewed and should shortly
be committed.
This procedure can be automated by entering the following command
in /etc/rc.sysctl
sysctl -w vfs.usermount=1
Maybe it's just me, but I think you are confusing this with
{Net|Open}BSD. /etc/rc.sysctl does not exist in FreeBSD.
-
Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never
System/Network Administrator,| claimed they were one, and always
Reality Check Information, Inc. | pointed to someone better.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option user-patch
On Sun, 29 Aug 1999, Chris Piazza wrote:
On Sun, Aug 29, 1999 at 06:30:35PM -0400, Chris D. Faulhaber wrote:
On Sun, 29 Aug 1999, Natty Rebel wrote:
This procedure can be automated by entering the following command
in /etc/rc.sysctl
sysctl -w vfs.usermount=1
Maybe it's just me, but I think you are confusing this with
{Net|Open}BSD. /etc/rc.sysctl does not exist in FreeBSD.
From /etc/rc:
# set sysctl variables early as we can
if [ -f /etc/rc.sysctl ]; then
. /etc/rc.sysctl
fi
Mind you it doesn't look like it was merged into releng_3
Yep, not in -stable ...
... wow, guess I've been blindly going through mergemaster lately with
-current...
-
Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never
System/Network Administrator,| claimed they were one, and always
Reality Check Information, Inc. | pointed to someone better.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option user-patch
On Sun, 29 Aug 1999, Warner Losh wrote:
In message [EMAIL PROTECTED] "Chris
D. Faulhaber" writes:
: Maybe it's just me, but I think you are confusing this with
: {Net|Open}BSD. /etc/rc.sysctl does not exist in FreeBSD.
rc.sysctl does too. I added it.
Excellent. That will be a nice feature to have in 3.x.
-----
Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never
System/Network Administrator,| claimed they were one, and always
Reality Check Information, Inc. | pointed to someone better.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option user-patch
On Sun, 29 Aug 1999, Natty Rebel wrote:
Quoting JK3 (j...@bgl.vsnl.net.in):
vs I whacked mount and umount into shape for using an option user in
[snip]
vs http://www-i2.informatik.rwth-aachen.de/~stolz/mount.diff
vs http://www-i2.informatik.rwth-aachen.de/~stolz/umount.diff.
vs Discussion welcome!
You can allow non-root users to mount and unmount devices if
the sysctl variable vfs.usermount is set to 1.
For example, here's what you need to do to allow floppies to
be mounted:
As `root':
1. # chmod 777 /dev/fd0 # give perms to access the device
2. # sysctl -w vfs.usermount=1
Now users can mount and umount the floppies:
3. $ mkdir ~/my-mount-point
4. $ mount -t msdos /dev/fd0 ~/my-mount-point
5. $ umount ~/my-mount-point
A FAQ entry covering this point is being reviewed and should shortly
be committed.
This procedure can be automated by entering the following command
in /etc/rc.sysctl
sysctl -w vfs.usermount=1
Maybe it's just me, but I think you are confusing this with
{Net|Open}BSD. /etc/rc.sysctl does not exist in FreeBSD.
-
Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never
System/Network Administrator,| claimed they were one, and always
Reality Check Information, Inc. | pointed to someone better.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: [mount.c]: Option user-patch
On Sun, 29 Aug 1999, Chris Piazza wrote:
On Sun, Aug 29, 1999 at 06:30:35PM -0400, Chris D. Faulhaber wrote:
On Sun, 29 Aug 1999, Natty Rebel wrote:
This procedure can be automated by entering the following command
in /etc/rc.sysctl
sysctl -w vfs.usermount=1
Maybe it's just me, but I think you are confusing this with
{Net|Open}BSD. /etc/rc.sysctl does not exist in FreeBSD.
From /etc/rc:
# set sysctl variables early as we can
if [ -f /etc/rc.sysctl ]; then
. /etc/rc.sysctl
fi
Mind you it doesn't look like it was merged into releng_3
Yep, not in -stable ...
... wow, guess I've been blindly going through mergemaster lately with
-current...
-
Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never
System/Network Administrator,| claimed they were one, and always
Reality Check Information, Inc. | pointed to someone better.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: [mount.c]: Option user-patch
On Sun, 29 Aug 1999, Warner Losh wrote:
In message pine.bsf.4.10.9908291829260.61952-100...@pawn.primelocation.net
Chris D. Faulhaber writes:
: Maybe it's just me, but I think you are confusing this with
: {Net|Open}BSD. /etc/rc.sysctl does not exist in FreeBSD.
rc.sysctl does too. I added it.
Excellent. That will be a nice feature to have in 3.x.
-
Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never
System/Network Administrator,| claimed they were one, and always
Reality Check Information, Inc. | pointed to someone better.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: Which device should I make with this error?
On Tue, 13 Jul 1999, eT wrote: During a make release for 3.2-RELEASE I get the following error: Making the regular boot floppy. Compressing doc files... sh -e /usr/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 2880 /R/stage/m fsfd 8000 minimum2 vnconfig: open: Device not configured *** Error code 1 Stop. *** Error code 1 What does this mean and how do I fix it? According to http://www.freebsd.org/FAQ/FAQ244.html#247 : 13.2. How do I make my own custom release? To make a release you need to do three things: First, you need to be running a kernel with the vn driver configured in. Add this to your kernel config file and build a new kernel: pseudo-device vn #Vnode driver (turns a file into a device) Hence the 'vn' in 'vnconfig'... ...or, checking the manpage for vnconfig(8), it references vn(4) (aka pseudo-device vn). - Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Which device should I make with this error?
On Tue, 13 Jul 1999, eT wrote: During a make release for 3.2-RELEASE I get the following error: Making the regular boot floppy. Compressing doc files... sh -e /usr/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 2880 /R/stage/m fsfd 8000 minimum2 vnconfig: open: Device not configured *** Error code 1 Stop. *** Error code 1 What does this mean and how do I fix it? According to http://www.freebsd.org/FAQ/FAQ244.html#247 : 13.2. How do I make my own custom release? To make a release you need to do three things: First, you need to be running a kernel with the vn driver configured in. Add this to your kernel config file and build a new kernel: pseudo-device vn #Vnode driver (turns a file into a device) Hence the 'vn' in 'vnconfig'... ...or, checking the manpage for vnconfig(8), it references vn(4) (aka pseudo-device vn). - Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Adding a PCMCIA modem to pccard.conf (fwd)
On Fri, 9 Jul 1999, Wayne Cuddy wrote: I have a Lucent Venus 56k pcmcia modem. I have been attempting to get it working under FreeBSD 3.1R. I have added an entry to /etc/pccard.conf and found the correct "config index" (i think) using "pccardc dumpcis". After resolving all the resource allocation errors I believe i was able to get the driver allocated. You are welcome to try my config: card "LUCENT-VENUS" "PCMCIA 56K DataFax" config 0x27 "sio2" 10 reset 1000 insert logger -s Lucent-Venus Modem inserted remove logger -s Lucent-Venus Modem removed I found that the 'reset 1000' stopped the system from locking up when you try to access the serial device. Also, change sio2 and irq 10 to whatever your system is configured for. - Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding a PCMCIA modem to pccard.conf (fwd)
On Fri, 9 Jul 1999, Wayne Cuddy wrote: I have a Lucent Venus 56k pcmcia modem. I have been attempting to get it working under FreeBSD 3.1R. I have added an entry to /etc/pccard.conf and found the correct config index (i think) using pccardc dumpcis. After resolving all the resource allocation errors I believe i was able to get the driver allocated. You are welcome to try my config: card LUCENT-VENUS PCMCIA 56K DataFax config 0x27 sio2 10 reset 1000 insert logger -s Lucent-Venus Modem inserted remove logger -s Lucent-Venus Modem removed I found that the 'reset 1000' stopped the system from locking up when you try to access the serial device. Also, change sio2 and irq 10 to whatever your system is configured for. - Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: devices in sysctl MIB?
On Sat, 3 Jul 1999, Chris Costello wrote: On Sat, Jul 3, 1999, Marc Nicholas wrote: I would certainly welcome such info... The info in the /proc filesystem in Linux is certainly nice. (One of the few things that is!). Nice, but misplaced. What does PCI/system version/etc have to do with running processes, exactly? Isn't this what kernfs is for? DESCRIPTION The kernel file system, or kernfs, provides access to information on the currently running kernel... - Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: wfd.c and ATAPI Zip
On Tue, 8 Jun 1999, Junichi Satoh wrote: Hmm... I have an ATAPI ZIP drive: wdc0: unit 1 (atapi): IOMEGA ZIP 100 ATAPI/23.D, removable, intr, iordis wfd1: medium type unknown (no disk) wfd1: buggy Zip drive, 64-block transfer limit set It does not work with your patch. It's a buggy drive. Probably, using only strcmp() is not enough. We shoud distinguish buggy or not using revision number. #I don't know how many revisions are available. :-) --- Junichi Satoh juni...@junichi.org juni...@jp.freebsd.org 12.A, 21.*, and 23.* are known to be buggy...13.A doesn't appear to be. Since the current method of sorting out the revisions doesn't seem to be perfect, would it be acceptible to consider them all buggy unless known not to be (i.e. compare ap-revision instead of ap-model)? - Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: wfd.c and ATAPI Zip
Here is a patch that checks for the revision numbers instead of simply the
inquiry string (and adds my buggy revision):
--- wfd.c.orig Thu Feb 18 17:06:08 1999
+++ wfd.c Mon Jun 7 12:02:25 1999
@@ -243,17 +243,21 @@
return -1;
/*
-* The IOMEGA ZIP 100, at firmware 21.* and 23.* at least
+* The IOMEGA ZIP 100, at firmware 12.A, 21.* and 23.* at least
* is known to lock up if transfers 64 blocks are
* requested.
*/
- if (!strcmp(ap-model, IOMEGA ZIP 100 ATAPI)) {
- printf(wfd%d: buggy Zip drive, 64-block transfer limit
set\n,
- t-lun);
- t-maxblks = 64;
- } else {
- t-maxblks = 0; /* no limit */
- }
+
+ if (!strncmp(ap-model, IOMEGA ZIP 100 ATAPI, 27))
+ if ((!strncmp(ap-revision, 12, 2)) ||
+ (!strncmp(ap-revision, 21, 2)) ||
+ (!strncmp(ap-revision, 23, 2))) {
+ printf(wfd%d: buggy Zip drive, 64-block transfer
limit set\n,
+ t-lun);
+ t-maxblks = 64;
+ } else {
+ t-maxblks = 0; /* no limit */
+ }
-
Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never
System/Network Administrator,| claimed they were one, and always
Reality Check Information, Inc. | pointed to someone better.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: wfd.c and ATAPI Zip
On Mon, 7 Jun 1999, Mike Smith wrote: 12.A, 21.*, and 23.* are known to be buggy...13.A doesn't appear to be. Since the current method of sorting out the revisions doesn't seem to be perfect, would it be acceptible to consider them all buggy unless known not to be (i.e. compare ap-revision instead of ap-model)? Uh, that's what the code does; if it's a Zip drive, it's considered to be buggy regardless of revision. If the string compare isn't matching a drive in the field, it means that Iomega have changed the string and we need to know what the new drives are calling themselves. I have an off-brand (NEC) Zip Drive with: IOMEGA ZIP 100 ATAPI Floppy/12.A which does have buggy firmware; I also have another one with: IOMEGA ZIP 100 ATAPI/13.A that has no problem when I remove the 64 block limitation. In this case, I would use strncmp instead of strcmp to test the first 27 characters. So what you are saying is that we are limiting all Zip drives instead of being based solely on firmware revision? Any reason for that? - Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
wfd.c and ATAPI Zip
I have two boxes with ATAPI Zip Drives:
Box1:
wdc1: unit 1 (atapi): IOMEGA ZIP 100 ATAPI Floppy/12.A,
removable, intr, iordis
wfd0: medium type unknown (no disk)
Box2:
wdc1: unit 0 (atapi): IOMEGA ZIP 100 ATAPI/13.A, removable, intr,
iordis
wfd0: medium type unknown (no disk)
wfd0: buggy Zip drive, 64-block transfer limit set
The drive on Box1 gets timeouts when reading/writing; the drive on Box2
works fine. After checking out /sys/i386/isa/wfd.c, I changed the block
transfer limit to that of buggy drives (64) and the timeouts disappeared.
I tried setting the block transfer limit to unlimited (0) as is used with
non-buggy hardware, no timeouts occurred on Box2.
Comparing the model names with wfd.c's comparison, I see that any model
different that Box2's is *not* buggy:
if (!strcmp(ap-model, IOMEGA ZIP 100 ATAPI)) {
since strcmp returns 0 if the strings match. On my drives, however, the
opposite seems the case.
My thoughts now are:
1) My two drive are somewhat 'rogue' in that they don't conform to the
driver's expectations.
2) When the driver was written, the '!strcmp' should be 'strcmp' since
strcmp returns 0 when equal (-1 or 1 when or ), in which case my patch
makes sense:
--- /sys/i386/isa/wfd.c.origThu Feb 18 17:06:08 1999
+++ /sys/i386/isa/wfd.c Tue Jun 6 08:59:59 1999
@@ -247,7 +247,7 @@
* is known to lock up if transfers 64 blocks are
* requested.
*/
- if (!strcmp(ap-model, IOMEGA ZIP 100 ATAPI)) {
+ if (strcmp(ap-model, IOMEGA ZIP 100 ATAPI)) {
printf(wfd%d: buggy Zip drive, 64-block transfer limit
set\n,
t-lun);
t-maxblks = 64;
3) I've just plain lost it :)
Can anyone else with an ATAPI Zip Drive confirm this?
Regards,
Chris
-
Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never
System/Network Administrator,| claimed they were one, and always
Reality Check Information, Inc. | pointed to someone better.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: Kernel config script
On Mon, 31 May 1999, John Birrell wrote: Why build a kernel at all? The generic kernel should do that application just fine. Only build a custom kernel if you have a good reason to do so. I somewhat agree. A custom kernel is useful for setting up and tuning parameters (e.g. softupdates); however, unlike Linux, we don't have a new kernel every week to reconfigure. - Chris D. Faulhaber jed...@fxp.org | All the true gurus I've met never System/Network Administrator | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
