RE: compress bootdisk
Please let me know if you have any info on how to set up such a diskless firewall. In particular, would such a box be able to run NAT and simulate linux's IP masquerading? I am in the same boat... I have a 4.1rc2 box that is the most reliable box on my home network, but I am still running Linux on the firewall box to take advantage of the ease of the IP masquerading features. Regards, Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com [EMAIL PROTECTED] [EMAIL PROTECTED] Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 On Wednesday, February 21, 2001 7:54 AM, Andrew Hesford [SMTP:[EMAIL PROTECTED]] wrote: This is interesting. I've been messing around with a diskless freebsd firewall, and I've always had tight constraints with loader and the kernel. I've all but given up due to lack of time and too many failures, and have resorted to using linux. kgzip sounds promising, though. What do I need to do, just `disklabel -Brw` the diskette, newfs it, and dump a kernel.gz in the root directory? On Wed, Feb 21, 2001 at 02:41:19PM +, Ian Dowse wrote: In message [EMAIL PROTECTED], Andrew Hesford writes: kzip and kgzip strip the kernel of its symbols, so that it is ultra-compact for rescue and install disks. More importantly, kgzip produces an ELF kernel image that can be loaded directly by the bootblocks. To boot a kernel compressed with gzip requires loader(8) which takes up 100-200k of disk space. -- Andrew Hesford - [EMAIL PROTECTED] 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-stable" in the body of the message
Re: FreeBSD 4.3 RELEASE schedule
On Wed, Feb 21, 2001 at 07:42:26AM -0800, David Wolfskill wrote: Now, to illustrate the danger of appearing to "set precedent", is there hope that PRs in http://www.freebsd.org/cgi/query-pr.cgi?pr=24102 and http://www.freebsd.org/cgi/query-pr.cgi?pr=23328 could be taken care of prior to 4.3-RC, as well? I'm already working on these PRs. I didn't have time last weekend to finish, but they (at least PR#24102) is in motion on a 5.0-CURRENT machine. Just need to review results and commit. -- wca PGP signature
Re: Tracking -docs like -stable
Kenneth, On Tue, Feb 20, 2001 at 08:04:04PM -0500, Kenneth W Cochran wrote: Hello -stable -docs: I'm trying to "track" documentation similarly to -stable. I can cvsup the "docs-supfile" Just Fine, but what needs to be done afterward? Chapter 7 of the FDP Primer, at http://www.freebsd.org/tutorials/docproj-primer/ should help. After cvsup of doc-all, in what directory should I be when making/building? Depends. If you've pulled down the whole repository you will need to check out the doc/ hierarchy first, something like % cd % mkdir doc-cvs % cd doc-cvs % cvs -d /home/ncvs checkout doc % cd doc Alternatively, if you've just pulled down the most current files then you will have told CVSup where to put them, probably somewhere like /usr/doc. If you want to build all the documentation, start at the root directory of the checked out docs (e.g., /usr/doc/, or $HOME/doc-cvs/doc if you follow the example above), and run make(1). If you want to build all the documentation for a specific language and encoding, then cd(1) down a level, eg % cd en_US.ISO_8859-1 If you want to build all the articles, or books, for a specific language then cd(1) down one more level % cd books or % cd articles If you want to build a specific document, such as the FAQ, cd(1) down in to it's directory % cd faq before running make(1). What are the relevant make-targets for documentation Typically, you will do something like this % make FORMATS=format target where format is one or more of html html-split txt ps pdf pdb rtf (if you want to build multiple formats at once then you have to protect the spaces from the shell, either something like % make "FORMATS=html ps" ... or % make FORMATS=html\ ps ... target should be one of -blank- If you don't specify a target, or you specify all a target called "all" then the document will be converted to the FORMATS you list. clean Removes the formatted document, and any intermediate files created by the build process. install Installs the document, typically somewhere under /usr/share/doc -- this path is controlled by the DOCDIR variable. package Builds a FreeBSD package of the formatted document that can be manipulated (installed, queried, etc) with the FreeBSD pkg_* commands. lintBoth these targets will verify that the document validateis valid according to the DTD it claims to comply with. where can I find them? Chapter 7 of the primer (in theory). I've just had a look at that, and it's as enlightening as it could be. I would be very grateful for submissions that cleaned it up. If you just want to quickly check that a particular format builds you can give the target filename. For example, % cd doc/en_US.ISO_8859-1/books/faq % make book.html will generate the FAQ as one large HTML document. You could also do % make index.html # Lots of little HTML files % make book.ps # Postscript % make book.pdf # PDF ... How do I properly omit building the .pdf and .ps versions? Make sure that the FORMATS variable doesn't contain "pdf" or "ps". By default, it doesn't. I can't find anything in The Books (Lehey v3 the Handbook) the docproj Web-site seems targeted toward documentation "authors" not toward documentation "trackers." The textproc/docproj port is installed. Incidentally, you will probably need to update this, as I committed some changes to it last night, to pull in eps2png and the netpbm utilities, which are required now that we support graphics in the documentation. Hope that helps, N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.2 STABLE: libssl.so undef: sk_X509_NAME_value
Matthew Reimer wrote: Do you have the openssl port installed? Since openssl was imported to -stable, the port is not necessary and can actually get in the way. Try deleting it (pkg_delete openssl-xxx). BTW, same goes for the ssh port. No, I haven't installed either of those. This box started life running 4.2-RELEASE. The only thing I changed today was cvsup-ing to -STABLE. It did "Checkout src/secure/lib/libssl/Makefile" however. Hm. Kris, oh, Kris... g. I did a diff betwixt -RELEASE and -STABLE, guess what. The usual change in the header, most of the changes were due to cleanup in whitespaces, but one stuck out: 14,19c14,19 SRCS+= bio_ssl.c s23_clnt.c s23_lib.c s23_meth.c s23_pkt.c s23_srvr.c \ s2_clnt.c s2_enc.c s2_lib.c s2_meth.c s2_pkt.c s2_srvr.c s3_both.c \ s3_clnt.c s3_enc.c s3_lib.c s3_meth.c s3_pkt.c s3_srvr.c ssl_algs.c \ ssl_asn1.c ssl_cert.c ssl_ciph.c ssl_err.c ssl_err2.c ssl_lib.c \ ssl_rsa.c ssl_sess.c ssl_stat.c ssl_txt.c t1_clnt.c t1_enc.c \ t1_lib.c t1_meth.c t1_srvr.c --- SRCS+=bio_ssl.c s23_clnt.c s23_lib.c s23_meth.c s23_pkt.c s23_srvr.c \ s2_clnt.c s2_enc.c s2_lib.c s2_meth.c s2_pkt.c s2_srvr.c \ s3_both.c s3_clnt.c s3_enc.c s3_lib.c s3_meth.c s3_pkt.c \ s3_srvr.c ssl_algs.c ssl_asn1.c ssl_cert.c ssl_ciph.c \ ssl_err.c ssl_err2.c ssl_lib.c ssl_rsa.c ssl_sess.c ssl_stat.c \ ssl_txt.c t1_clnt.c t1_enc.c t1_lib.c t1_meth.c t1_srvr.o \ Indeed the patched release has one modifcation too many. I'll see what'll happen when I patch the patch and rebuild. Not that I'm voluntering, mind :)... but I think the development of a standardised test suite would be a good thing. A major undertaking given the complexity no doubt. Yet such a suite has more repeatability than mere wetware humans. Ah well, one can dream. Roelof PS if it works out I'll submit a PR -- Home is where the (@) http://eboa.com/ is. Nisser home -- http://www.Nisser.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
PS/2 mouse problem solved
Last time I forgot to say that I was getting those ``psmintr out of sync'' messages. Now, I set flags 0x100 for the psm0 device and everything runs just fine (with the KVM switch). Thank you everyone who responded to me the first time. -- ,oOo.Bc -=EEKrzysztof Parzyszek [EMAIL PROTECTED] 11/29/2000 3:41pm -'7' `L'---Entropy isn't what it used to be... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: PS/2 mouse problem solved
I could be wrong here but most of the new motherboards being released (all of the new via chipsets after the mvp series as well as the intel i8x0 series) support hot-swap of ps/2 as long as the computer is booted with it. They are supposed to give an audible beep when the user reinserts the connection to the device so you know it is properly connected. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tyler McGeorge Sent: Wednesday, February 21, 2001 5:04 PM To: Matt Heckaman; Krzysztof Parzyszek Cc: FreeBSD-STABLE Subject: Re: PS/2 mouse problem solved Just as a note, I would like to confirm that PS/2 is NOT hotswap. However, it rarely fries the motherboard or device. But, if you can avoid plugging while the machine is on, you'll be safe. Unplugging is relatively more safe. --- Matt Heckaman [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 21 Feb 2001, Krzysztof Parzyszek wrote: ... : Plugging and unplugging a PS/2 device when the computers are on scares : me. I heard it can fry the motherboard. I don't touch the cables after : turning everything on. I don't have any problems after switching banks : on the KVM back and forth. Oh for real? I had never heard that. The unplug wasn't intentional though, the stupid cable likes to come out when I'm cleaning and have to lift up the KVM to clean under it, it comes out about 20% of the time :P : I guess I have seen someone mention it either on this mailing list or : on -questions some time ago. I'll look around, though it'll be hard to weed it out from PS/2, KVM, etc keywords. Ah well, I've got time :) * Matt Heckaman - mailto:[EMAIL PROTECTED] http://www.lucida.ca/pgp * * GPG fingerprint - 53CA 8320 C8F6 32ED 9DDF 036E 3171 C093 4AD3 1364 * -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (FreeBSD) Comment: http://www.lucida.ca/pgp iD8DBQE6lDfSMXHAk0rTE2QRAju8AJ0SZXwGiCkf4O3pYFU3CY3xgMl5UwCeKtXZ JwGOVKzDOl1lU0WuWiF29Eg= =EOwX -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message __ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices! http://auctions.yahoo.com/ 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-stable" in the body of the message
Re: Hello
On Wed, Feb 21, 2001 at 12:20:32PM -0800, Glen Gross wrote: The default /sys/i386/conf/KERNEL build file does not have the networking features enabled; you will need to bring in the appropriate files from LINT and recompile. Read /usr/src/UPDATING for details. There is no /sys/i386/conf/KERNEL. The kernel which is installed by the standard install process is generated from /usr/src/sys/i386/conf/GENERIC and includes most network drivers. The only missing drivers I can think of are the ti and sk Gigabit Ethernet drivers and the Token Ring driver though there are probably a few more minor ones. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 PGP signature
RE: Hello
I did mean to refer to the GENERIC file. But are the necessary protocols, etc. included to enable networking? I also recall that there was talk about disabling inetd by default. Do we still need inetd_enable="YES" in /etc/rc.conf? On Wednesday, February 21, 2001 12:28 PM, Brooks Davis [SMTP:[EMAIL PROTECTED]] wrote: On Wed, Feb 21, 2001 at 12:20:32PM -0800, Glen Gross wrote: The default /sys/i386/conf/KERNEL build file does not have the networking features enabled; you will need to bring in the appropriate files from LINT and recompile. Read /usr/src/UPDATING for details. There is no /sys/i386/conf/KERNEL. The kernel which is installed by the standard install process is generated from /usr/src/sys/i386/conf/GENERIC and includes most network drivers. The only missing drivers I can think of are the ti and sk Gigabit Ethernet drivers and the Token Ring driver though there are probably a few more minor ones. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 File: ATT00012.att Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com [EMAIL PROTECTED] [EMAIL PROTECTED] Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cvsup confusion
At 09:07 2/21/2001 -0800, you wrote: There is a problem with this approach. Suppose everybody did it that way. Then at exactly the same time each week, everybody in a given time zone would be trying to CVSup from their nearby mirrors. The mirrors would quickly fill up, and you'd be retrying for hours, along with everybody else in your time zone. That starts off around a "probably true" and progresses on to "nearly ludicrous." ;) 1. The higher you go in bandwidth (to end-users), the less users that have that kind of bandwidth. While the possibility of the mirrors getting congested is certainly possible, it's just as improbable. Let Y be the number of cvsup mirrors in the US, and X be the number of freebsd boxes in the US. Now, X/Y is the ratio of freebsd boxes to cvsup mirrors. It doesn't take a rocket scientist to determine that number will be ridiculously overburdened, probably in the neighborhood of a quarter million to one (NOTE: I'm totally pulling that number out of my ass, but it doesn't seem too unreasonable. As of Jan. 2001, out of 27 million sites checked, 15 million were running apache. 250k of them being freebsd would mean about 1 in 60 are freebsd.. I expect that number is probably higher.). With 250,000 estimated sites cvsupping to each server, If each server was assigned a unique time to (just begin) it's cvsup, spaced one hour apart, it would take 28 years for each server to cvsup just once. This is obviously not the case. Possible explainations are that I've overestimated the number of machines cvsupping (just 10k machines though would take over a year); that the machines cvsupping, in general, have far less bandwidth than the machines running the cvsup mirrors; etc. The bottom line of this explaination is simple. If every machine running freebsd was also cvsupping, it wouldn't matter -what- time they decided to do it at, the servers would be under full load constantly.. so saying "if everyone in one timezone did that, it would drag the server down" is a moot point. The servers do get dragged down, but if you'll notice, in general the lower numbered mirror you go with, the slower it is, almost any time of day, on any day of the month. People are just too lazy to pick a mirror thats close to them, or further down the "cvsupit" list than the first one they see. It's much better to pick a random time and put it in your crontab. I disagree. I think it would be "much better" if this was truly a concern, to change the time that your periodics are executed, or to simply pick a different mirror that isn't saturated when your default periodic runs. ... In any case, to the original poster, regardless of how you decide to schedule your updates, you'll alleviate the problem by doing as was suggested and reading the manpage, or (a better solution imho, but reading the manpage anyway is always a great idea) condensing the three seperate cvsupfiles you have into one and only invoking one copy of cvsup to begin with. ---signature file--- PGP Key Fingerprint: 446B 7718 B219 9F1E 43DD 8E4A 6BE9 D739 CCC5 7FD7 "I don't think [Linux] will be very successful in the long run." "My experience and some of my friends' experience is that Linux is quite unreliable. Microsoft is really unreliable but Linux is worse." -Ken Thompson, Interview May 1999. http://www.freebsd.org FreeBSD - The Power to Serve http://www.rfnj.org Radio Free New Jersey - 375 streams - 96kbps @ 44.1khz http://namespace.org -- http://name.space Resist the ICANN! Support name.space! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: PS/2 mouse problem solved
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Krzysztof Parzyszek Sent: Wednesday, February 21, 2001 1:47 PM To: Matt Heckaman Cc: FreeBSD-STABLE Subject: Re: PS/2 mouse problem solved On Wed, Feb 21, 2001 at 04:33:19PM -0500, Matt Heckaman wrote: I'm curious, what kind of KVM do you have? StarView SV201 I have a Belkin Omniview SE here, and I have a little problem with it. If I unplug the main PS/2 cable (attached to mouse) then plug it back in, I lose the mouse in FreeBSD, however, if I cycle the banks on the KVM I get a mouse back, but it is eratic and out of control (even if I kick out of X and use moused on the console). Plugging and unplugging a PS/2 device when the computers are on scares me. I heard it can fry the motherboard. I don't touch the cables after turning everything on. I don't have any problems after switching banks on the KVM back and forth. I hot swap ps2 devices all the time and have NEVER had any ill effect other than the mouse/kb not working, requiring a reboot sometimes. Often(YMMV), hot plugging them unfreezes a mouse or kb, in my experiance. While it might not be the BEST thing to do, it has NEVER hurt anything *I've* done it on. A reboot is required to fix it. Has anyone else seen this? There are no errors logged on the console when this happens :( I've seen it on Omniview pro's before. OF I guess I have seen someone mention it either on this mailing list or on -questions some time ago. -- ,oOo.Bc -=EEKrzysztof Parzyszek [EMAIL PROTECTED] 11/29/2000 3:41pm -'7' `L'---Entropy isn't what it used to be... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
multiple copies of freebsd-stable
I have multiple identical boxes. I want to build freebsd-stable on one of them and then copy to others. Does any automation exist to do this, or do I have to push the entire /usr/src directory and then run the install/merge process ? Please advise. TIA, George To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: syslog changes in 4.2-stable?
On Wed, Feb 21, 2001 at 06:20:13PM +0900, Hajimu UMEMOTO wrote: lists Thanks, yes, that works...but, ugh. So some backward-compatibility was broken lists in 4.2-STABLE...and that should probably be fixed... It is security reason. The -s option is specified by default under 4.X or later. If you need, you can still enable insecure mode by omitting -s from syslogd_flags in /etc/rc.conf. However, if you intend to log within the host, it is not recommended. Please refer manpage of syslogd. uh, nope, it failed even on a 4.2-STABLE machine (which I use as a loghost for the local network) that has syslogd running as: 37894 ?? Ss 0:03.27 syslogd -n -vv -a 10.10.10.0/24 unless I force it to use the unix domain socket as suggested above. But that gave me an idea -- I forced logger to use PF_INET by specifying the -h option, and that doesn't work -- I even tried adding -a 127.0.0.1/32 to the syslogd command line hoping that that might make a difference: 41337 ?? Ss 0:00.01 syslogd -n -vv -a 10.10.10.0/24 -a 127.0.0.1/32 but that doesn't help either. The syslog host is 10.10.10.5 and I tried both: logger -h 10.10.10.5 -p 'crit' "this is a test" logger -h 127.0.0.1 -p 'crit' "this is a test" and neither worked. However it is receiving syslog messages from other hosts without a problem where I have it specified in their syslog.conf as: *.* @10.10.10.5 (I noticed that kern.debug and possibly kern.info messages don't get relayed, but that is another thread and I almost understand why that is but couldn't find it in the syslogd code) There is something screwy about the PF_INET stuff which neither logger nor Sys::Syslog like...and this is broken in regards to previous behaviour. Thanks, Adi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: multiple copies of freebsd-stable
From: [EMAIL PROTECTED]
Date: Wed, 21 Feb 2001 14:33:29 -0600
I have multiple identical boxes. I want to build freebsd-stable on one of
them and then copy to others.
Does any automation exist to do this, or do I have to push the entire
/usr/src directory and then run the install/merge process ?
Well, if you NFS mount /usr/{obj,src}, you don't really need to "push"
them. I think I sketched how I do this between 3 - 10 days ago, so that
should be in the -stable archives. And others have discussed this sort
of thing, as well.
Depending on the number of the boxes (and their ability to netboot), you
may find alternatives, such as some of the stuff that Alfred Perlstein
has posted about, to your liking. Doug Ambrisko put something similar
together here which I've used (and hacked a bit).
Cheers,
david
--
David Wolfskill [EMAIL PROTECTED] UNIX System Administrator
Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: cvsup confusion
In article [EMAIL PROTECTED], Mark Drayton [EMAIL PROTECTED] wrote: I wrote a small script to cvsup stable, ports and doc every couple of days by running cvsup supfile logfile for each collection. Somehow this script appears to have 'gone wrong' leaving several copies of cvsup running at once. Is running more than one copy of cvsup at once likely to have damaged /usr/src or /usr/ports? I don't know whether it would mess up your files or not, but it's definitely something that won't work right in general. Check out cvsup's "-l" option in the cvsup man page to keep this from happening. Or run it under lockf(1). Sorry if these are common questions - I searched the archives but couldn't find anything. Searching the archives is fine. But don't forget, there's a great big manual page too. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
