/etc/defaults/rc.conf 4.1-STABLE-200-08-18
Hello, After manually updating /etc from cvsupped sources (200-08-18) i noticed that /etc/rc.conf doesn't get (properly) loaded. Network daemons that are disabled in /etc/rc.conf get started, other switches don't work (firewall_quiet). It looks as if /etc/rc.conf doesn't get loaded at all What i did was: make buildworld etc. (steps in handbook & UPDATING) cd /usr/src/etc make DESTDIR=/var/tmp/root distrib-dirs distribution cd /var/tmp/root/etc cp rc* /etc/ (most of the rc files was changed) cd defaults cp * /etc/defaults/ (some changes here too) updated most if not all other files Could it be that i missed something? BTW: Temporarily fixed it myself by putting [ -f /etc/rc.conf ] && . /etc/rc.conf just after the last comment block in /etc/defaults/rc.conf. Hope that doesn't break anything :)... -- Ago [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Update perl along with src
On Tue, 22 Aug 2000, Dan Larsson wrote: > This is just a thought, would it be possible to update the perl modules > along with the source when suping the src? make.conf feature? Which perl modules? Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: error with make buildkernel 4.1-RC -> 4.1-release
On Mon, Aug 21, 2000 at 11:49:47PM -0700, Kent Stewart wrote: > > > Ben Smithurst wrote: > > > > Kent Stewart wrote: > > > > > About half of the time I run cvsup in the gui mode so that I can save > > > the log to disk. > > > > you can save the log to disk much easier in non-GUI mode, by the way. > > > > # cvsup -g -L2 supfile 2>&1 | tee cvsup.log > > That is true. I hadn't even thought about doing it that way. Then, I > make a slight command and end up with a couple of ways of handling it. > I think one of the advantages of the GUI, it might be the only > advantage, is that it lets you scroll through them first. I can use > more to do that using the tee but cvsup has a nice scrollbar in the > GUI mode. > Hmm, are you aware of some useful utilities hidden away in the contrib directory of the cvsup-bin tarball (that don't get installed by the port)? My favourite is cvsup2html which makes all the "Edit" and "Checkout" lines into links to the CVS repo on freefall? # cvsup2html < /usr/sup/cvsup.log > /usr/sup/cvsup.html cvsupchk is also useful; found loads of redundant files in my tree. >From the README: This directory contains various utilities contributed by CVSup users. Please contact the individual authors of the utilities if you find bugs or have questions about them. cvsup2html Convert cvsup client log output into a web page, with each filename serving as a link to the cvsweb page for that file. cvsup2httplog Convert a cvsupd log file to standard httpd log file format, so that it can be analyzed by tools such as webalizer. cvsupchk Check for extraneous files in a tree maintained by CVSup. cvsupwho Show who is currently using your CVSup server. > I also happen to like to do things like this in the command line mode. > It looks like I will have a script that saves from the command line > and one to fire it off in the GUI mode. > > BTW, I like the mergemaster addition to 18.4.7. I saw the commit and > immediately updated the handbook on all three of the systems I use > FreeBSD on. > > Thanks, > > Kent > > > > > > -- > > Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D > > -- > Kent Stewart > Richland, WA > > mailto:[EMAIL PROTECTED] > http://kstewart.urx.com/kstewart/index.html > FreeBSD News http://daily.daemonnews.org/ > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- 4.4 - The number of the Beastie 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:[EMAIL PROTECTED]http://www.radan.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
4.1 /etc/rc.conf and IPv6...
This is for the net gurus on this list. My 4.1 stuff builds-- though *not* matching the src/UPDATING instructions exactly. Everything looks go for a `shutdown now' to single-usr or a reboot and boot -s. Can I just drop in my current `ifconfig ed1' line (as ed0')? how do I join the v6 world? Currently, in /etc/rc.conf.local is: network_interfaces="lo0 ed1"# List of network interfaces (lo0 is loopback). ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. ifconfig_tun0="inet 207.108.223.55 207.108.223.19 netmask 0xff00" # ed1 configuration for tao (ed1 in FBSD-3.2) ifconfig ed1 inet 10.0.0.1 netmask 255.255.255.0 I'm guessing that this is likely to work in a 4.1 /etc/rc.conf.local. Am I being too optimistic? gary -- Gary D. Kline [EMAIL PROTECTED] Public service Unix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: DoS attacks and FreeBSD.
At 01:58 AM 8/22/00 -0700, Kris Kennaway wrote: >On Tue, 22 Aug 2000, Noor Dawod wrote: > > > Yes, it can, and I've alreaedy done just that. But then again, all other > > legitimate visitors will be locked out... > >Depends how smart the rate-limiting is. If it's at the application level >you know the connection (probably) isn't spoofed, which means you can >rate-limit per IP. In "Apache Modules with Perl and C" there is an example. It goes a bit further than IP by concatenating the IP with the user agent, which won't work if all the users behind a firewall/proxy have the exact same agent name, but then some hackery could be done for an exemption list. There are several variations or combinations that could be used. However, the example used might be better written in C for busy sites, which also avoid the memory overhead of using perl. There is still the problem of making a connection and sitting idle to tie up a process. The timeout could be reduced, but there might be problems for those with slow connections. Suffice to say there are always compromises, but with little work one can block most malicious spiders, etc with a combination of access controls. Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Scrapbooking Web Site - www.gonescrappin.com
Announcing a great new Scrapbooking Web Site: www.gonescrappin.com. Our site has an exclusive new way to "Shop by Layouts!" Sign up for our newsletter and get 10% off your order until August 31. Hope you'll check it out! The Gone Scrappin' Team To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How can I obtain -stable for previous date ?
[EMAIL PROTECTED] wrote: > I'm obtain -stable (RELENG_4) every 2 days via cvsup. > And do make world every time... > But after Aug 20, the system became unstable ;( > It locks on hard loading (hard HDD usage), > like a make release or even make buildworld ;( > No panic, no crashdump, nothing, full lock... > Just many HDD problems after hard reboot ;( Look at the date= option in CVSup. date=[cc]yy.mm.dd.hh.mm.ss This specifies a date that should be used to select the revi- sions that are checked out from the CVS repository. The client will receive the revisions that were in effect at the specified date and time. So perhaps you want src-all date=2000.08.20.00.00.00 tag=RELENG_4 or something to get the code from midnight on the 20th August. But ideally you should try to find what is causing the problem, of course. I assume that will work anyway, I've never actually used the date option in CVSup myself. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ATA66 cable being ignored?
Steve Coles wrote: > "ad1: ATA-4 disk at ata0 as slave" > Are you sure the Maxtor is UDMA-66? Isn't "ATA-4" UDMA-33? Very good point. In fact, this Maxtor disk is at least a year old -- truly ancient by modern standards :-} -- so I'm pretty sure it's not UDMA66. As I recall, the interface cable that originally came in the box with this particular drive was an older, 40-wire cable. So, until such time as I can rearrange my hardware -- either by upgrad- ing the old Maxtor to a newer drive, or else by freeing up a spot for the older drive on the secondary ATA controller -- I guess I'll just have to endure slower disk throughput. I suppose I'll somehow manage to survive. :-} This brings up another question, though. Is there any way to redo the kernel's device probe output so it doesn't try to blame the cable in cases like this? For example, if an ATA controller has two devices, and one is ATA-5 (or better?) but the other is not, then ata-dma.c could say something like "can't do UDMA66 with fast/slow device mix". Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Numbering of fxp devices
On Tue, 22 Aug 2000, Fred Clift wrote: > > other way around. The order stayed this way for a couple of weeks during > > which I tracked -stable and made world frequently, but after one > > upgrade, the box came up with the on-board card claiming to be fxp0. > > However, not long afterwards, it reverted to the original behaviour. > > > > Now, obviously the numbering doesn't matter all that much. What _does_ > > matter is if the numbering is unpredictable at boot time (worst case) or > > if it may be reversed after a remote upgrade. Is this down to pure fluke > > or can I lock down the order in some way? > > > I am not directly aware of what recent changes would have caused > the change in probe order, but I can give you some ideas about > where to look and then offer my comments about what I belive would > be ideal. > > in FreeBSD <= 3.X it appears that all pci-to-pci busses were > probed first, and then devices on them were probed in some fixed > order. > > In FreeBSD >= 4.0 the 'newbus' code replaced a lot of the old bus > code including probing and now the buses are probed kind of in a > depth-first fashion, finding all devices on a particular bus and > then moving on to another. Aparently, from your results, the > order that the busses are probed has been changed or something > similar. > > I pitty the guy with whom I exchanged emails a while back that is > running a 6 or 8 port 'router' all with fxp cards. He was running > 3.4 last I knew and was planning on waiting a LONG time before > upgrading to 4.X because of the relative difficulty of figuring > out which cards when where. That would be me, probably. :-) 7 NICs, one of which is dual-port, for a total of 8 ports. I recently moved all of those NICs from a Compaq Proliant 3000 running 3.4-STABLE into a new Proliant ML530 running 4.1-STABLE. The card order is definately weird, but that isn't so much FreeBSD's fault. Compaq was nice enough to label primary, secondary, and tertiary PCI bus slots on the back of the machine, but they aren't in order anyway. What I ended up doing was booting the system with all the cards installed, noting the MAC address of each interface, and then comparing that to physical slot locations. Not as nice as the sequential ordering in the Proliant 3000, but not a big deal either, as long as it doesn't change on me in the future without some warning. :-) > What I would find to be the best of all possible worlds is if you could > wire-down pci-card instances to particular instances of a driver - ie I > want the first card on bus 2 to be fxp0 and the second card on bus 1 to be > fxp1, etc... Of course this would depend on finding the busses in the > right order, but... This would be nice. But, if bus or device ordering changes, you'd still be up the same creek. You'd have to wire things down in a card-specific way and not a bus/slot-specific way. > Unfortunately, I'm, uh, somewhat unexperience in this (and most of the > rest) of the code and when I looked at it, all I got was a headache. How > hard would it be to either provide a consistent mapping or to allow the > hard-wiring of devices to drivers? -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Update perl along with src
This is just a thought, would it be possible to update the perl modules along with the source when suping the src? make.conf feature? Regards +-- Dan Larsson | Tel: +46 8 550 120 21 Tyfon Svenska AB | Fax: +46 8 550 120 02 Public PGP keys | finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
