Re: adding DHCP client to src/contrib/
"David O'Brien" writes: > I am planning on adding the Wide-DHCP client to src/contrib/ and > src/sbin/ in a few days. > > I have it bmaked and ready go to. I have choosen the WIDE client because > it is much smaller space-wise than the ISC client and its configuration > is simplier. > > The plan is to make a boot floppy / boot CDROM with a DHCP client on it. Having just read all the emotional arguments, I have a technical one: What impact will this have on the rc files? How will it affect rc.conf, seeing as it overrides several values therein? What happens if your lease expires and doesn't get renewed, or gets renewed with a different IP address? Having seen the complete mess that DHCP client support made of Solaris' init files (and they were bad to start with!), I'm keen to not see the same convolution made here. -- When I said "we", officer, I was referring to myself, the four young ladies, and, of course, the goat. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
I'm not convinced that DHCP CLIENT needs to have everything wide open. It sends a broadcast, but the response is directed. On Mon, 8 Feb 1999, Sean Eric Fagan wrote: > In article > <19990209082922.17759.qmail.kithrup.freebsd.curr...@rucus.ru.ac.za> you write: > >- DHCP-WIDE requires you to have bpf configured into your kernel > > for a GENERIC kernel, this is VERY BAD - is there a more elegant > > way to handle this? I certainly would not like to see the > > generic kernel in the distribution going out into the world with > > bpf enabled. > > So does isc-dhcp. > > There's really no other way to do it: you need the ability to grab packets > that come from an unidentified machine, which doesn't have an IP address. You > could write some other method of doing this -- and then put it into every > single ethernet (et al) device driver -- or you could just use BPF, which > really isn't all that large. > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> It may even be necessary to use bpf initially, but there must be a more > elegant way - having a quick look around - it would be a good idea to > look at the code which already exists in libstand > (/usr/src/lib/libstand/bootp.c). There is. Date: Wed, 16 Sep 1998 15:20:45 -0400 (EDT) From: Garrett Wollman Message-Id: <199809161920.paa07...@khavrinen.lcs.mit.edu> ..snip.. The problem is that the network code assumes, at a very deep level, that you can't have any IP traffic until you have an address configured (and this is wrong, but requires work to fix). -GAWollman Unfortunately, I don't have the knowledge of the part of the kernel that needs changing. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> David's original email said he was going to commit without giving > a justification. I call it bloat, then the justifications pour in. I may have been too close to the situation. JKH asked for a DHCP client on -STABLE a few days ago to add to the boot floppy. He now has one. I was taking the "contribute code, not ideas with no one to act on them" route. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
On Mon, Feb 08, 1999 at 11:10:53PM -0800, Mike Smith wrote: > > There are any number of reasons for going with the ISC client, > including an involved ISC developer that's keen to help it happen. The WIDE project has been very responsive in the past in supporting their products on FreeBSD. Unless this person is a committer, or there is another committer wanting to carry the issue, I use the WIDE client daily. There are good reasons to with with either client. I'm not sure what best criteria to use in picking one other, except support and maintenance. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> > *DO* *NOT* *SUPPORT* *STATIC* *IP* *ASSIGNMENTS*. How can we make this any > > clearer to you? Its fine to say `I don't want to see DHCP in the base > > system' > Then, *BUY* the cd-rom and support the FreeBSD project. Maybe Gary isn't yelling loud enought, so let me try. I AM part of the FreeBSD Project. I'm contributing about as much as I possibly can. My home machines are on the campus Ethernet. *STATIC* *IP* *ASSIGNMENTS* *DO* *NOT* *EXIST*. If you care to see the 80-some-odd ports I maintain to continue to be so; you will not mind me being able to get an IP address for my test boxes will you? Of course I could just install the 3.0-R CDROM, but then I guess you might get upset when the ports I maintain don't work on the upcoming release. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> What impact will this have on the rc files? How will it affect > rc.conf, seeing as it overrides several values therein? Most basic, you would have ``network_interfaces="lo0 fxp0"'' as usual, but no "ifconfig_fxp0="inet " line. Rather you would have a ``/etc/start_if.fxp0'' file with: /sbin/dhcpc fxp0 sleep 10 in it. If you want to assign your own hostname, you may continue to do so in the normal manner. If you use ``dhcpc -n fxp0'', dhcpc will do ``hostname <...>'' with the hostname returned by the DHCP server. If you want to specify your /etc/resolv.conf file, you may do so. Or use ``dhcp -r fxp0'' to create one for you. > What happens if your lease expires and doesn't get renewed, or gets > renewed with a different IP address? You will get "no route to host" type messages. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> Would you please settle on a set of misinformation and stick with it? > > isc-dhcp's client *does* have a very extensive configuration file. Same > parser as the server. Ok! So I'll stop passing on this information, I'll try it again. Last time I used ISC-dhclient, it did infact REQUIRE a configuration file. Now a zero length file might of done the trick.. but it bitched about a non-existent file. and would not fetch an IP address for me when I ran it. So maybe it is a documentation over-site. Maybe now it says "configuration file not found, using built-in defaults". Contract with the WIDE-dhcpc which Just Worked(tm). -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
3.0 install woes
I took a 3.0 kernel #3 floppy and tried to install 3.0 on two systems and both failed: 1. System: PCB Motherboard , Amd 386/40, Cyrix FasMath (w/ or w/o) 8 MB, IDE IBM DHEA 38451 (16384/16/63) The most I could achieve was booting up into blue install screen mode but got hung during probing devices (only NE2000, VGA and IDE controller present, nothing fancy). 2. System ASUS P55T2P4, same HD, but also SCSI disks and a Syquest removable medium. P5/200, 128 MB, xl0 network device. Symptoms: at boot: prompt there is a long beep (for a second or so) finds xl0, SCSI disks but wdc0 and wdc1 are not found !. (although the HD is there in the BIOS) Comes up into install mode, but when choosing custom->partition there are No disks found. -- Chris Christoph P. U. Kukulies k...@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
On Mon, Feb 08, 1999 at 04:32:39PM -0800, Steve Kargl wrote: > > If we want FreeBSD to have any credibility as a workstation OS, we > > need DHCP. It should be possible for a user or admin to smack in the > > boot floppy, have it autoconfigure the selected network interface, and > > perform an FTP installation. > > > > So, we'll import a pop server, apache, g77, ad nauseam > to increase the credibility of FreeBSD as a workstation OS. That's senseless what you said. You certainly are able to imagine that in some networks you can't have static IP address, but you need to install FreeBSD over network. I'm glad to see DHCP client included onto boot floppy in the future. -- Vallo Kallaste va...@matti.ee To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: 3.0 install woes
This sometimes can happen :( However, to avoid hungs - boot with -c option and in visual configure mode disable all devices which you doesn't have. Maxim Christoph Kukulies wrote: > I took a 3.0 kernel #3 floppy and tried to install 3.0 on two systems > and both failed: > > 1. System: > > PCB Motherboard , Amd 386/40, Cyrix FasMath (w/ or w/o) > 8 MB, IDE IBM DHEA 38451 (16384/16/63) > > The most I could achieve was booting up into blue install screen > mode but got hung during probing devices (only NE2000, VGA and IDE > controller present, nothing fancy). > > 2. System > > ASUS P55T2P4, same HD, but also SCSI disks and a Syquest removable > medium. P5/200, 128 MB, xl0 network device. > > Symptoms: > > at boot: prompt there is a long beep (for a second or so) > > finds xl0, SCSI disks but wdc0 and wdc1 are not found !. > (although the HD is there in the BIOS) > > Comes up into install mode, but when choosing custom->partition > there are No disks found. > ? > > -- > Chris Christoph P. U. Kukulies k...@gil.physik.rwth-aachen.de > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
Can we go onto a more interesting discussion? I'm a bit tired of debating the merits of DHCP or rc.conf.site.foo.bar and this discussion thread (and that one) have now moved to the "delete at first sight" stage. - Jordan > David O'Brien wrote: > > > These should be left has ports. > > > > Explain how I am to install FreeBSD at my campus when DHCP has been > > mandated. Many univ. are moving in this direction. > > > > Maybe, support WC by purchasing the cd-rom? > > Convince your University to get a large quantity of cd-roms > from WC and resell the disks to the students? > > -- > Steve > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
In article you write: >What impact will this have on the rc files? How will it affect >rc.conf, seeing as it overrides several values therein? PAO already has some support for this; it works, and is what I've been using. >What happens >if your lease expires and doesn't get renewed, or gets renewed with a >different IP address? That's always a problem -- I know some people at uSoft who have that happen (in Windows), and it kills their telnet sessions. It's not something we're going to be able to solve, and there really isn't one. >Having seen the complete mess that DHCP client support made of >Solaris' init files (and they were bad to start with!), I'm keen to >not see the same convolution made here. Fortunately, it shouldn't be that difficult. There's a freebsd shell script that comes with isc-dhcp that does the brunt of the work, and dhclient invokes that itself. So all the rc scripts have to do is notice that the IP address is being set by DHCP, and start dhclient, instead of running ifconfig. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cleanup of rc.conf ( -4.x )
On Mon, 8 Feb 1999, Matthew Dillon wrote:
> This does not make any operational change except to get rid
> of the $conf_dir junk from rc.conf, which I originally put
> in to try to bootstrap rc.diskless.
>
> A much better way to do rc.diskless was suggested to me,
> which I'm going to implement. It involves retargeting
> the /conf/ME softlink by mount_union'ing a small MFS
> filesystem onto /conf. Then one simply makes /etc/rc.conf.local
> a softlink to /conf/ME/rc.conf.local ( i.e. a sysop would do
> that as an extra, we wouldn't distribute the base system
> like that of course )
>
> In anycase, I've committed a new rc.conf that gets rid
> of $conf_dir, FYI, and am about to commit a new rc.diskless and
> new examples that uses the mount_union idea for retargeting
> during a diskless boot that will be much more straightward and
> obvious.
>
Hasn't mount_union been dead for ~forever (+/- a few years)?
> -Matt
> Matthew Dillon
>
>
>
>
> rc_conf_files="/etc/rc.conf.site /etc/rc.conf.local"
>
> ...
>
> ##
> ### Allow local configuration override at the very end here ##
> ##
> #
> #
>
> for i in ${rc_conf_files}; do
> if [ -f $i ]; then
> . $i
> fi
> done
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
RE: adding DHCP client to src/contrib/
> -Original Message- > From: David O'Brien [mailto:obr...@nuxi.com] > Sent: 09 February 1999 10:54 > To: Geoff Rehmet > Cc: curr...@freebsd.org > Subject: Re: adding DHCP client to src/contrib/ > > > > It may even be necessary to use bpf initially, but there > must be a more > > elegant way - having a quick look around - it would be a > good idea to > > look at the code which already exists in libstand > > (/usr/src/lib/libstand/bootp.c). > > There is. > > Date: Wed, 16 Sep 1998 15:20:45 -0400 (EDT) > From: Garrett Wollman > Message-Id: <199809161920.paa07...@khavrinen.lcs.mit.edu> > > ..snip.. > The problem is that the network code assumes, at a very > deep level, > that you can't have any IP traffic until you have an address > configured (and this is wrong, but requires work to fix). > > -GAWollman > > Unfortunately, I don't have the knowledge of the part of the > kernel that > needs changing. Hopefully, it will be possible to find the person who will be able to do that work - I also do not have the knowledge to do this. It is probably worth fixing, to get a more elegant way for DHCP to work, and I believe that DHCP should be committed with a view to changing the use of bpf. I realise this is not an easy proposition. Geoff. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: 3.0 install woes
On Tue, Feb 09, 1999 at 01:37:16PM +0200, Maxim Sobolev wrote: > This sometimes can happen :( However, to avoid hungs - boot with -c option > and in visual configure mode disable all devices which you doesn't have. I should have mentioned that I did that already. The installation disk lets you enter into this mode anyway, so there is no need for the -c option or am I wrong? > > Maxim > > Christoph Kukulies wrote: > > > I took a 3.0 kernel #3 floppy and tried to install 3.0 on two systems > > and both failed: > > > > 1. System: > > > > PCB Motherboard , Amd 386/40, Cyrix FasMath (w/ or w/o) > > 8 MB, IDE IBM DHEA 38451 (16384/16/63) > > > > The most I could achieve was booting up into blue install screen > > mode but got hung during probing devices (only NE2000, VGA and IDE > > controller present, nothing fancy). > > > > 2. System > > > > ASUS P55T2P4, same HD, but also SCSI disks and a Syquest removable > > medium. P5/200, 128 MB, xl0 network device. > > > > Symptoms: > > > > at boot: prompt there is a long beep (for a second or so) > > > > finds xl0, SCSI disks but wdc0 and wdc1 are not found !. > > (although the HD is there in the BIOS) > > > > Comes up into install mode, but when choosing custom->partition > > there are No disks found. > > > > > > -- > > Chris Christoph P. U. Kukulies k...@gil.physik.rwth-aachen.de > > > > To Unsubscribe: send mail to majord...@freebsd.org > > with "unsubscribe freebsd-current" in the body of the message -- --Chris Christoph P. U. Kukulies k...@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Lots of "panic: vrele: negative ref cnt"
> I've seen identical panics when using nmh's spost command to send > mail. Instant panic saying "negative ref cnt". This is using an NFS > mounted home directory (containing the draft mail to be sent). > Unfortunately, I didn't have time to investigate further, so I just > switched over to using SMTP instead. We think we've sorted out this problem. Trying to make a cross device link to an NFS filesystem decreases the reference count twice, so if you do this a few times you can panic a machine. I've submitted a gnats report (kern/9970). David. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Which DHCP client
Jordan, I object to the idea that the selection of which dhcp client is being made on the basis that David has commit privledges and I do not. Further, it is clear that David has not used a recent release of the isc client and is biasing his opinion with false assertions. It is my opinion that we should not use this criteria to decide which client will become a part of the base system. I have been "bmake"ing the isc client for almost a year. Requests to get assistance in comitting it went unanswered. I believe the isc client to be a better choice. If size is a real concern, perhaps we should treat this client as we do the shell in PicoBSD. I'm not convinced that the differences are that great. However, the flexability is :-) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
From: "Jordan K. Hubbard" Subject: Re: adding DHCP client to src/contrib/ Date: Mon, 08 Feb 1999 21:05:59 -0800 > > Make sysinstall be able to pkg_add? We do something similar to > > It can already pkg_add. However, I need dhcp in the crunched image > since I can't very well GET a package if I don't have any bloody IP > addresses to configure the network interface with and the user doesn't > know what they are either. :-) > > - Jordan > I wasn't clear about that (sorry - long day). I meant something like pkg_add for extending the sysinstall environment, not the one being installed. Cheers, Jerry Hicks wghi...@bellsouth.net To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
Steve Kargl wrote: > > Drop FreeBSD cd-rom into tray (or caddy). > mount_cd9660 /dev/cd0a /mnt > pkg_add dhcp > umount /mnt What about us without FreeBSD cd-roms? -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
Karl Pielorz wrote: > > Whilst the argument about removing the source tree / kernel source etc. has > always been pretty mute (what hackers not worth their salt don't come > prepared? :) - I don't like the idea of every root exploiter just being able > to 'instantly' sit there and run BPF! (Without even things like tripwire > having a chance of detecting a kernel change). Err... what about kld? Or you are basing your security on a hacker's lazyness? -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
Steve Kargl wrote: > > > > The plan is to make a boot floppy / boot CDROM with a DHCP client on it. > > Content-Type: text/BLOAT > > These should be left has ports. I disagree. It is very common nowadays to need to extract your IP address through DHCP. Not having a DHCP boot floppy/cd is a serious disadvantage. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
From: John Birrell > Or convince FreeBSD developers to simply add a DHCP client to the base > sources and build a boot/install floppy with that functionality. > No user cost. No user hassle. Why not?! Sigh. Agree that this should be done for now. Absolutely. In the long run, an extensible sysinstall will help with these matters. I haven't really examined them yet, but feel safe in assuming that there is a fair amount of unused space on the two floppy installation diskette set. It shouldn't be necessary to extract everything that might ship on these floppies for every user. I'm not certain what the minimum installation footprint is right now but would probably be safe in assuming that it is growing. I sincerely believe that getting the filesystem layering code into shape is a good first step toward a more flexible sysinstall. Cheers, Jerry Hicks wghi...@bellsouth.net > -- > John Birrell - j...@cimlogic.com.au; j...@freebsd.org > http://www.cimlogic.com.au/ > CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cleanup of rc.conf ( -4.x )
On Mon, Feb 08, 1999 at 08:14:55PM -0800, Matthew Dillon wrote: > This does not make any operational change except to get rid > of the $conf_dir junk from rc.conf, which I originally put > in to try to bootstrap rc.diskless. > > A much better way to do rc.diskless was suggested to me, > which I'm going to implement. It involves retargeting > the /conf/ME softlink by mount_union'ing a small MFS Union mounts do not work, and I believe they are some distance from working (unless you have better patches than I do, of course). Eivind. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
> I object to the idea that the selection of which dhcp client > is being made on the basis that David has commit privledges > and I do not. Further, it is clear that David has not used a > recent release of the isc client and is biasing his opinion > with false assertions. H. From where I'm sitting, it looked more to me like he was selecting it based on the fact that he liked the WIDE client a lot more. I personally am ambivalent about which client is chosen just so long as *a* client is chosen. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
< said: > The issue, as I understand it, is to get a reply from an unknown server > (who has an IP address), while you have no IP address. You also have to send a packet *from* 0.0.0.0 (since you have no IP address). I'm almost irritated enough to consider fixing this this week. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New boot blocks + serial hardware handshaking?
On Mon, Jan 18, 1999 at 07:39:06PM +0200, Robert Nordier wrote: > Josef Karthauser wrote: > > As the one who did the actual coding, I can confirm that the approach > adopted in both the new bootblocks and the boot loader is virtually > identical to that used in the older (biosboot) bootblocks. In all > cases, the simplest approach giving the smallest code sizes was > used, so there's very little difference between the three sets of > routines. > > The above applies to 3.0-current. In 3.0-release, the boot loader > was still using BIOS routines (with hardware handshaking), but this > was changed around late November 1998. I've now confirmed this. The problems that we saw in October have indeed been fixed. Thanks, Joe -- Josef KarthauserFreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [...@pavilion.net, j...@uk.freebsd.org, j...@tao.org.uk] To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
I do not dispute that he "likes" the WIDE client. However, his choice seems to be based on familarity rather than CURRENT technical evaluation. I have (recently) tried both clients. For the simple case, both work satisfactorily. The ISC client/server (pl10) builds right out of the box. I prefer it because of the additional flexability it provides for the non-trivial case. On Tue, 9 Feb 1999, Jordan K. Hubbard wrote: > I personally am ambivalent about which client is chosen just so > long as *a* client is chosen. I agree that this is the important issue. If someone will agree to commit the files, I'd be happy to supply the pieces for the ISC DHCP2 client to drop in. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
Sean Eric Fagan writes: > >There is NO config file which means its damn annoying for you to tweak how > >it works.. > > Would you please settle on a set of misinformation and stick with it? > > isc-dhcp's client *does* have a very extensive configuration file. Same > parser as the server. > > In 99.9% of cases, it needs to be a 0-length file. I agree that ISC is better software (in terms of design, configurability, etc). We use the ISC server (highly modified for our product) on the InterJet and it works fine. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
DHCP, install, security
How about putting bpf functionality into install-kernel, but not into the GENERIC kernel? If the install required the use of dhcp, sysinstall should yell about having to rebuild the kernel with bpf-device in. On the other hand, the security-concerned ISPs and others can rebuild their kernels to remove the bpf (they probably rebuild them anyway for other reasons, or should do that anyway). -mi To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DHCP, install, security
> How about putting bpf functionality into install-kernel, but not > into the GENERIC kernel? That's already going to happen since the dhcp client isn't going to be very useful otherwise. Since this affects only the installation kernel, it's nothing that anyone should take issue with. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Buildworld FAILS for 2 days!!!!
Hi folks, It seems to me that most of all people in the developer list carried away with DHCP issue and just ignore that buildworld fails continuously for 2 days in /usr/src/sys/i386/ibcs2/ibcs2_ipc.c. Please get rid of it!!! Sincerely, Maxim To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cleanup of rc.conf ( -4.x )
< said: >> A much better way to do rc.diskless was suggested to me, >> which I'm going to implement. It involves retargeting >> the /conf/ME softlink by mount_union'ing a small MFS > Union mounts do not work, and I believe they are some distance from > working (unless you have better patches than I do, of course). Last I checked, union mounts work just fine, thank you very much. unionfs (which should have been called `translucentfs') is what doesn't work. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
On 8 Feb, Jordan K. Hubbard wrote: >> These should be left has ports. > > Can't really get away with that anymore - too many people require > DHCP for very basic bootstrapping. To insert some reality into this discussion, a quick survey at the office shows: PlatformHas DHCP Irix 6.5Yes Solaris 2.5.1 No HP/UX 10.20 Yes Linux (RH 5.x) Yes AIX 4.2 Yes BSD/OS 4.0 Yes FreeBSD 2.X, 3.XNo A "yes" means "ships with the base OS." I'll also note that the ASUS motherboards I use in our servers have BOOTP in the BIOS to support net booting via the onboard Intel Pro/100 interfaces. It's time to get out of the stone age, folks. --lyndon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
"David O'Brien" wrote: > I was taking the "contribute code, not ideas with no one to act on them" > route. Hear, Hear! Please import this, it will certainly make may (and many of those I work with) lives a $#!tload easier. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
From: Charlie ROOT > Although it is somewhat larger, the ISC dhcp2 client has significantly > more flexability WRT options beyond the bare basics. > > I would recommend that the default client on HD based systems be the > ISC client because of that flexability. I have to agree here. The problem with ISC is the example configuration file in the manpage is much too complicated. It scares people off. 99% of the people don't need that. My config file is: send host-name "pdxlx103"; One line that's it. -Wayne To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
DHCP bpf alternatives
An alternative to dhclient and bpf would be to add an ioctl that would force an interface to initiate a DHCP configuration. This would allow for something like: ifconfig ep0 dhcp Of course, this means moving the entire DHCP state engine into the kernel ... --lyndon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> To insert some reality into this discussion, a quick survey at the > office shows: > > Platform Has DHCP > > Irix 6.5 Yes > Solaris 2.5.1 No ... and Solaris 2.6 has DHCP. > HP/UX 10.20 Yes > Linux (RH 5.x)Yes > AIX 4.2 Yes > BSD/OS 4.0Yes > FreeBSD 2.X, 3.X No > > A "yes" means "ships with the base OS." Yes, having a DHCP client as a standard part of the system wold be nice. Steinar Haug, Nethelp consulting, sth...@nethelp.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld FAILS for 2 days!!!!
Maxim Sobolev writes: > It seems to me that most of all people in the developer list carried > away with DHCP issue and just ignore that buildworld fails continuously > for 2 days in /usr/src/sys/i386/ibcs2/ibcs2_ipc.c. Please get rid of > it!!! If you followed the appropriate lists, you'd know the cause of this breakage, and why it wasn't fixed until three hours ago. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
On Mon, 8 Feb 1999, Steve Kargl wrote: > Daniel O'Connor wrote: > > > > On 09-Feb-99 Steve Kargl wrote: > > > > And just WHERE is the package?? Often on an NFS or FTP server, no?? > > > > And just HOW am I to communicate with that NFS or FTP server?? > > > Drop FreeBSD cd-rom into tray (or caddy). > > > mount_cd9660 /dev/cd0a /mnt > > > pkg_add dhcp > > > umount /mnt > > Excuse me sir.. I am but a poor student.. > > > > Or I'd like to play with FreeBSD, but I'd rather not fork out US$30 for > > something I > > haven't tested. > > > > Cheapbytes. Support the project and Walnut Creek CDROM. Alex To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cleanup of rc.conf ( -4.x )
:>> the /conf/ME softlink by mount_union'ing a small MFS : :> Union mounts do not work, and I believe they are some distance from :> working (unless you have better patches than I do, of course). : :Last I checked, union mounts work just fine, thank you very much. :unionfs (which should have been called `translucentfs') is what :doesn't work. : :-GAWollman union mounts are broken. I must have panic'd my test box 50 times trying to get them to work. null mounts are also broken -- mmap()ing NFS based files through a null mount doesn't work, amoung other things. Fortunately I found another way using the less sophisticated -o union type of mount ( verses the more sophisticated mount_union ). -Matt Matthew Dillon :-- :Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same :woll...@lcs.mit.edu | O Siem / The fires of freedom :Opinions not those of| Dance in the burning flame :MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
On Tue, Feb 09, 1999 at 09:59:52AM -0600, Charlie ROOT wrote: > If someone will agree to commit the files, I'd be happy to supply > the pieces for the ISC DHCP2 client to drop in. I already have a bmaked ISC v2 dhclient. I bmaked both so I would more informated about how easy either would be to add to the tree. I will spend some time today and reflect on which client I still prefer in import. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cleanup of rc.conf ( -4.x )
< said: > union mounts are broken. I must have panic'd my test box 50 times > trying to get them to work. > Fortunately I found another way using the less sophisticated > -o union type of mount That is a union mount. Which is it -- broken or not? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
On Tue, Feb 09, 1999 at 09:27:44AM -0700, Lyndon Nerenberg wrote: > > Platform Has DHCP > > Irix 6.5 Yes > Solaris 2.5.1 No Solaris 2.6 Yes You should have used a more modern Solaris. It helps your argment. :-) > It's time to get out of the stone age, folks. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cleanup of rc.conf ( -4.x )
Matthew Dillon writes:
> union mounts are broken. I must have panic'd my test box 50 times
> trying to get them to work.
Nonono. The union filesystem ('mount -t union') is broken. Union
mounts ('mount -o union') are not.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
On Tue, 9 Feb 1999, David O'Brien wrote: > On Tue, Feb 09, 1999 at 09:27:44AM -0700, Lyndon Nerenberg wrote: > > > > PlatformHas DHCP > > > > Irix 6.5Yes > > Solaris 2.5.1 No > Solaris 2.6 Yes > > You should have used a more modern Solaris. It helps your argment. :-) Digital Unix 4.0Yes -john To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cleanup of rc.conf ( -4.x )
:Matthew Dillon writes:
:> union mounts are broken. I must have panic'd my test box 50 times
:> trying to get them to work.
:
:Nonono. The union filesystem ('mount -t union') is broken. Union
:mounts ('mount -o union') are not.
:
:DES
:--
:Dag-Erling Smorgrav - d...@flood.ping.uio.no
Ack. We're just confusing terminology. We're both saying the same
thing.
-Matt
Matthew Dillon
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
In article <19990209003618.b19...@relay.nuxi.com>, David O'Brien wrote: > Maybe Gary isn't yelling loud enought, so let me try. > > I AM part of the FreeBSD Project. I'm contributing about as much as > I possibly can. David, please Just Do It. As is often the case, the loudest of the obstructionists are nowhere to be found in the commit logs or the FreeBSD contributors list. -- John Polstra j...@polstra.com John D. Polstra & Co., Inc.Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cleanup of rc.conf ( -4.x )
> Fortunately I found another way using the less sophisticated > -o union type of mount ( verses the more sophisticated mount_union ). Well, there are problems here too. I had /var/mail mounted with -o union from another host. My own, local, mailbox would get corrupted every once in a while -- lots of \0, some other strings. 16K in size. This is on 3.0-RELEASE, with NFSv3. The server is Solaris. -mi To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
In article , Richard Wackerbarth wrote: > I object to the idea that the selection of which dhcp client is > being made on the basis that David has commit privledges and I do > not. It's not. It's being made on the basis that David took the initiative and did the work, and you did not. -- John Polstra j...@polstra.com John D. Polstra & Co., Inc.Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cleanup of rc.conf ( -4.x )
On Tue, 9 Feb 1999, Mikhail Teterin wrote: > > Fortunately I found another way using the less sophisticated > > -o union type of mount ( verses the more sophisticated mount_union ). > > Well, there are problems here too. I had /var/mail mounted with -o union > from another host. My own, local, mailbox would get corrupted every once > in a while -- lots of \0, some other strings. 16K in size. > > This is on 3.0-RELEASE, with NFSv3. The server is Solaris. There were several NFS fixes put in after 3.0-RELEASE i do not know if they are applicable to your situation though. -Alfred To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DHCP bpf alternatives
Lyndon Nerenberg wrote: > > An alternative to dhclient and bpf would be to add an ioctl that would > force an interface to initiate a DHCP configuration. This would allow > for something like: > > ifconfig ep0 dhcp > > Of course, this means moving the entire DHCP state engine into the > kernel ... Erm, you forgot to include the patches to do this... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
At 9:25 AM -0800 2/9/99, David O'Brien wrote: > I already have a bmaked ISC v2 dhclient. I bmaked both so I would > more informated about how easy either would be to add to the tree. > > I will spend some time today and reflect on which client I still > prefer in import. Does anyone have a good feel for which dhcp client would be better from a security standpoint? (me, I don't have a clue, but maybe that's something to consider) I'd also note that I have no particular preference which DHCP client is used, but I do very much like the idea that some DHCP capability will be available at installation time for net-installs. --- Garance Alistair Drosehn = g...@eclipse.its.rpi.edu Senior Systems Programmer or dro...@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
> Wackerbarth wrote: > > > I object to the idea that the selection of which dhcp client is > > being made on the basis that David has commit privledges and I do > > not. > > It's not. It's being made on the basis that David took the initiative > and did the work, and you did not. I think, he did. But his requests to get the thing reviewed/committed went unanswered. This is getting ugly... -mi To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DHCP bpf alternatives
> Erm, you forgot to include the patches to do this... I'll leave that to the anti-bpf fanatics (who can also supply patches to eliminate /dev/[k]mem while they're at it). I'm quite happy seeing ISC dhclient move into /sbin. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> > What impact will this have on the rc files? How will it affect > > rc.conf, seeing as it overrides several values therein? > > Most basic, you would have ``network_interfaces="lo0 fxp0"'' as usual, > but no "ifconfig_fxp0="inet " line. Actually, I'm not sure I'd want to be that locked in. I'd have interfaces listed explicitly assume they had config data, and then specify a 'DHCP' token to have all non-listed interfaces do the DHCP thing, eg: network_interfaces="lo0 dhcp" > > What happens if your lease expires and doesn't get renewed, or gets > > renewed with a different IP address? > > You will get "no route to host" type messages. Yup. That's just the way it is - I can't imagine what alternative the original poster thought they could have, steal an address? Ignore your least? Get real. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
on Feb 9, David O'Brien wrote: > > What impact will this have on the rc files? How will it affect > > rc.conf, seeing as it overrides several values therein? > > Most basic, you would have ``network_interfaces="lo0 fxp0"'' as usual, > but no "ifconfig_fxp0="inet " line. > > Rather you would have a ``/etc/start_if.fxp0'' file with: > > /sbin/dhcpc fxp0 > sleep 10 this is one of the things ISC does better than WIDE, btw -- dhclient won't background itself until it has an ip address, so you don't have to guess how long it'll take to obtain a lease. no wasted time during boot if things are quick, no lost services if things are slow. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
Just wanted to mention something that I haven't seen mentioned here in all the flaming and whatnot. OpenBSD ships out-of-the-box with dhcp client support available as an install option. This turned out to be very nice when I was installing it on one of my friend's Sparcs. His network is on a DSL link and has to run with DHCP - he has no static IPs available at all. OpenBSD installed and runs just fine with his network. We also tried to get Solaris7 going on one of his other Sparcs but it was a royal pain to figure out how to turn on dhcp for it. It didn't switch it on during the install nor give any hints as to how do do so. All in all, OpenBSD made a far more favorable impression on my friend than Solaris. So from a practical point-of-view, I think adding dhcp client support to FreeBSD is a good thing. Also, the argument about which dhcp server/client is better than the other, if I may suggest looking at and perhaps importing the OpenBSD code? The CHANGES file lists a bunch of security and bug fixes. I can't tell where the code is derived from. -- Parag Patel To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
May I suggest looking at the OpenBSD dhcp client/server? I'm not sure which one they're derived from, but the CHANGES file lists a bunch of bug and security fixes. -- Parag Patel To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> Ok! So I'll stop passing on this information, I'll try it again. Last > time I used ISC-dhclient, it did infact REQUIRE a configuration file. > Now a zero length file might of done the trick.. but it bitched about a > non-existent file. and would not fetch an IP address for me when I ran > it. So maybe it is a documentation over-site. Maybe now it says > "configuration file not found, using built-in defaults". This is the same experience I had with ISC - it would never fetch an IP address. WIDE worked right off, so I've been sticking with that. - Mike To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> > Most basic, you would have ``network_interfaces="lo0 fxp0"'' as usual, > > but no "ifconfig_fxp0="inet " line. > > then specify a 'DHCP' token to have all non-listed interfaces do the > DHCP thing, eg: > > network_interfaces="lo0 dhcp" Hum... can you give a little more of the approach? I'm probably just not seeing the clean way of doing this. I've got a machine on the DHCP required network with two NICs. Currently I'm only using one of them and thus don't have it listed in ``network_interfaces''. So it just happily sits there. IMHO we shouldn't try to dhcp configure it. It will just fill up logs as it continues to try to get a lease which it can't. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cleanup of rc.conf ( -4.x )
:> Well, there are problems here too. I had /var/mail mounted with -o union :> from another host. My own, local, mailbox would get corrupted every once :> in a while -- lots of \0, some other strings. 16K in size. :> :> This is on 3.0-RELEASE, with NFSv3. The server is Solaris. : :There were several NFS fixes put in after 3.0-RELEASE i do not know if :they are applicable to your situation though. : :-Alfred The zero-corruption bug is fixed in both -stable and -current. -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
SVR4 module doesn't load
Is anyone having problems loading the SVR4 module? I have it loading up thru loader.rc, and I get: Preloaded elf kernel "kernel" at 0xf02a3000. Preloaded splash_image_data "/boot/splash.bmp" at 0xf02a309c. Preloaded elf module "splash_bmp.ko" at 0xf02a30ec. Preloaded elf module "cd9660.ko" at 0xf02a3190. Preloaded elf module "vesa.ko" at 0xf02a3230. Preloaded elf module "linux.ko" at 0xf02a32cc. Preloaded elf module "svr4.ko" at 0xf02a336c. link_elf: symbol msginfo undefined ^^^ When I try to load it using kldload, I get: [vs...@jabberwock] /sys/i386/conf# kldload /modules/svr4.ko kldload: can't load /modules/svr4.ko: Exec format error This is on a -current world as of 11:30am EST 02/09/99. [vs...@jabberwock] /sys/i386/conf# ls -la /modules/svr4.ko -r-xr-xr-x 1 root wheel 75194 Feb 9 13:40 /modules/svr4.ko [vs...@jabberwock] /sys/i386/conf# file /modules/svr4.ko /modules/svr4.ko: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped I do have "pseudo-device streams" in my kernel config. Is there anything else that I require? Thanks Viren -- Viren R. Shah "You are about as sharp as a sack of wet mice" -- Foghorn Leghorn To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
> May I suggest looking at the OpenBSD dhcp client/server? I'm not sure > which one they're derived from, but the CHANGES file lists a bunch of > bug and security fixes. It looks like they're using the ISC dhcp client (and server). Dan Eischen eisc...@vigrid.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> > > Most basic, you would have ``network_interfaces="lo0 fxp0"'' as usual, > > > but no "ifconfig_fxp0="inet " line. > > > > then specify a 'DHCP' token to have all non-listed interfaces do the > > DHCP thing, eg: > > > > network_interfaces="lo0 dhcp" > > Hum... can you give a little more of the approach? I'm probably just not > seeing the clean way of doing this. The ISC dhclient can (IRC) take a list of interfaces not to muck with. Just pass it all the interface names on the list, minus the 'dhcp'. If you find 'dhcp' in $network_interfaces, start dhclient. > I've got a machine on the DHCP required network with two NICs. Currently > I'm only using one of them and thus don't have it listed in > ``network_interfaces''. So it just happily sits there. IMHO we > shouldn't try to dhcp configure it. It will just fill up logs as it > continues to try to get a lease which it can't. In a situation like that, you would just tune the dhcp client not to ask for a lease on that interface. You know you've done something silly; there's a mechanism to stop it breaking things. What more could you ask for? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: SVR4 module doesn't load
On Tue, 9 Feb 1999, Viren R. Shah wrote: > I do have "pseudo-device streams" in my kernel config. Is there > anything else that I require? Yes, I needed to add "options KTRACE". Blaz Zupan, b...@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: gpib driver - does anybody use it?
On Mon, 08-Feb-1999 at 17:44:33 -0700, John Galbraith wrote: > Dag-Erling Smorgrav writes: > > Steve Kargl writes: > > > Dag-Erling Smorgrav wrote: > > > > I stumbled upon the (undocumented) gpib driver today [...] > > > Actually, John Galbraith has written > > > a better driver for the National Instrument GPIB cards. Search > > > the hardware mailing list for a URL to his latest driver. It > > > is reported to be superior to the driver in src/sys. > > > > Then why haven't we imported it yet? send-pr that baby and drop me a > > note, and I'll look into it. > > > > The last version I posted can be found at www.ece.arizona.edu:/~john. > I have been using it quite extensively for the last few months on a > 2.2.6 machine. Mostly it has been small transfers, so I haven't been > using it at heavy load. It appears to be quite stable under those > conditions. > > I have tested it on another 3.0 machine, but I haven't been using it > for real work. > > I made some extensive changes in order to support catching SRQ's using > the poll() mechanism. I almost have it, but there was one thing that > I couldn't get to work, so I haven't posted it yet. The version on > the web page is the one I am actually using, along with a bunch of > documentation. I would greatly appreciate to see this thing go into the tree. I still have to build a measurement system in our lab (you remeber, John :-)) and people there are talking about linux already :-(. Don't shoot me, but I would like to see it in 2.2.x if possible, since 3.x-STABLE still has some problems which makes it impossible for me to use it on production machines. Thanks a lot, -Andre To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
HEADS UP: Spontaneous reboots
Everybody who is experiencing spontaneous reboots under 3.0-STABLE or 4.0-CURRENT (and did not experience them with 2.2.8 or earlier) and cannot find any indication of what could be wrong (nothing on the console and nothing in syslog), please send me (in *private* mail) the output of "dmesg" on your machine and your kernel configuration file. Also send a list of all daemons that are running on a freshly booted system and any other information you think could be relevant. If you are a commiter or a networking guru, even better. :) Please send the above data, even if you have already responded to the "Spontaneous reboots" thread on this mailing list. I'm trying to compile a list of hardware and software configurations that experience the problem and see if there is something in common between them. If we want to fix the problem, we at least need a starting point. For now it looks like it is a problem with the networking code, so please send a description of what network activity is going on when you experience the reboots. I will summarize the responses I receive. Also if you have a good idea how we could attack the problem, please speak up. For now my idea is to find a common software and hardware configuration and then try to sistematically remove components that could cause the problem. I have separetely posted this message to both freebsd-current and freebsd-stable, as it seems to affect both branches. Please DO NOT respond to the mailing list. Thank you for your attention. Blaz Zupan, b...@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld FAILS for 2 days!!!!
-BEGIN PGP SIGNED MESSAGE- On Tue, 9 Feb 1999, Maxim Sobolev wrote: MS> It seems to me that most of all people in the developer list carried MS> away with DHCP issue and just ignore that buildworld fails continuously MS> for 2 days in /usr/src/sys/i386/ibcs2/ibcs2_ipc.c. Please get rid of MS> it!!! I'm a FreeBSD user. I can't code, so I don't "contribute" in the code sense to the project. However, your e-mail (and many of it's ilk) raises my hackles, and I'll tell you why : 1. If you have a problem, and you're running -current, and you are 100% sure that this is affecting everyone, format a nice e-mail with sufficient details, and mail it to the list (assuming you've read the list to ensure that the problem isn't specific to you, or hasn't already been fixed). Or ask someone else you know who is running -current if they're experiencing the same problem. Or check your commit mail to see what has changed in the file(s) that is affecting you. 2. This is a co-operative project; no-one is getting paid for this, and no-one appreciates getting moaned at for something they've done for (economically speaking) free. 3. You're running -current. This assumes that you're enough of a developer (and NOT a user) to fix problems. If you can't, run - -stable or -release. 4. The people in the developer list (note: DEVELOPer list) are discussing a relatively important question about something entering the source tree. Unlike other free OS projects, in this one, most things get a good airing and people can air their views. It's a kind of a democratic autocracy. I love FreeBSD; I like the support I've received, and the lack of support at times is frustrating, but it's taught me to look for information before banging on my keyboard to the nearest @freebsd.org mailing list. I suggest you realise that unless you're paying for support and development, you're not guarenteed access to or quality of either. I can recommend a fair, commercially supported NOS - NT; you'll pay for (and sometimes receive) support, but bear in mind you can't reach their developers. EXTREMELY satisfied 4.0-current and 2.2.6-release user. - --- Khetan Gajjar (!kg1779) * khe...@iafrica.com ; khe...@os.org.za http://www.os.org.za/~khetan * Talk/Finger khe...@chain.freebsd.os.org.za FreeBSD enthusiast* http://www2.za.freebsd.org/ Security-wise, NT is a OS with a "kick me" sign taped to it -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBNsCxCV0slw2AMOJdAQEq0wP/bYO1capvfoUugmFrxKiqui2k0V6M9vPB xeEmmUdbfnWanyvImKVoD1bB27gd8yXAnCkYd86UXCORQ+Kfvb36xKswK8MK88BY kFadnmCS636vvs5his6uOeVHmWKMwO5D+DiOghvlXJUvmluAL6lQ3FM0/Gq8mguw PgaZchYvdbE= =w674 -END PGP SIGNATURE- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: gpib driver - does anybody use it?
> > I would greatly appreciate to see this thing go into the tree. I > still have to build a measurement system in our lab (you remeber, > John :-)) and people there are talking about linux already :-(. > > Don't shoot me, but I would like to see it in 2.2.x if possible, > since 3.x-STABLE still has some problems which makes it impossible > for me to use it on production machines. What crippiling disability prevents you from adding the driver yourself? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Heads up! /etc/rc.conf.site is dead.
Rather that listen to people wail over the next few months, it was decided instead to go to a slight variation on the previous theme in hopes that more people will be happy with the compromise. In essence, what used to be everything in /etc/rc.conf has moved to /etc/defaults/rc.conf and this file takes care of including (optionally) /etc/rc.conf and /etc/rc.conf.local. This means that you can go back to editing /etc/rc.conf again and the expected things will happen, though those interested in the full set of tunables will still need to look at /etc/defaults/rc.conf (which, like all defaults to eventually live in that directory, will be freely upgradable by the system). Since that made rc.conf.site obsolete, it was taken out of the configuration. Please move it to rc.conf on your system, should you be one of those folks who installed from an earlier snapshot and are now updating your /etc from -current or -stable sources (not likely to be all that many people). This change will also be in 3.1. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
Mike Smith wrote: > >> I've got a machine on the DHCP required network with two NICs. Currently >> I'm only using one of them and thus don't have it listed in >> ``network_interfaces''. So it just happily sits there. IMHO we >> shouldn't try to dhcp configure it. It will just fill up logs as it >> continues to try to get a lease which it can't. > >In a situation like that, you would just tune the dhcp client not to >ask for a lease on that interface. You know you've done something >silly; there's a mechanism to stop it breaking things. What more could >you ask for? POLA. Currently, an interface that isn't mentioned isn't configured at all. Changing that isn't kind. Perhaps having a variable in rc.conf that lists the interfaces to be configured with DHCP would be better? (As opposed to the statically configured interfaces.) Tony. -- f.a.n.finch d...@dotat.at f...@demon.net To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
> Mike Smith wrote: > >In a situation like that, you would just tune the dhcp client not to > >ask for a lease on that interface. You know you've done something > >silly; there's a mechanism to stop it breaking things. What more could > >you ask for? > > POLA. Currently, an interface that isn't mentioned isn't configured at > all. Changing that isn't kind. Perhaps having a variable in rc.conf > that lists the interfaces to be configured with DHCP would be better? > (As opposed to the statically configured interfaces.) It depends on who's being astonished. DHCP expects to try to configure all your interfaces; that's what it's there for. On a system where a new and unexpected interface may suddenly arrive, it makes sense to have the dhcp client pick it up. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
>Date: Tue, 09 Feb 1999 14:21:09 -0800 >From: "Jordan K. Hubbard" >Since that made rc.conf.site obsolete, it was taken out of the >configuration. Please move it to rc.conf on your system, should you >be one of those folks who installed from an earlier snapshot and are >now updating your /etc from -current or -stable sources (not likely to >be all that many people). This change will also be in 3.1. OK; I gather that (by default) rc.conf will no longer be sourcing rc.conf.local either? Thanks, david (who is using a moderately recent SNAP for a growing number of machines) -- David Wolfskill UNIX System Administrator d...@whistle.comvoice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
:>configuration. Please move it to rc.conf on your system, should you :>be one of those folks who installed from an earlier snapshot and are :>now updating your /etc from -current or -stable sources (not likely to :>be all that many people). This change will also be in 3.1. : :OK; I gather that (by default) rc.conf will no longer be sourcing :rc.conf.local either? : :Thanks, :david (who is using a moderately recent SNAP for a growing number of machines) Sniff. I liked rc.conf where it was. /etc/rc, /etc/rc.conf. /etc/rc.local, /etc/rc.conf.local. Simple and obvious. Now we have /etc/defaults/rc.conf, /etc/rc.conf, and /etc/rc.conf.local. Considerably less simple and quite unobvious. -Matt :-- :David WolfskillUNIX System Administrator :d...@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 : :To Unsubscribe: send mail to majord...@freebsd.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
On Tue, 9 Feb 1999, Matthew Dillon wrote: > Sniff. I liked rc.conf where it was. /etc/rc, /etc/rc.conf. > /etc/rc.local, /etc/rc.conf.local. Simple and obvious. > > Now we have /etc/defaults/rc.conf, /etc/rc.conf, and /etc/rc.conf.local. > Considerably less simple and quite unobvious. Erm... I thought that the point of /etc/defaults/rc.conf was that one wouldn't touch it, and only work with rc.conf? (Haven't looked at the change myself, as my test machine is dead at the moment) mela...@yip.org - Shave A Tree Today! (TM) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
> Now we have /etc/defaults/rc.conf, /etc/rc.conf, and /etc/rc.conf.local. > Considerably less simple and quite unobvious. Until you have to upgrade to the latest set of "knobs"; that problem is something I think people are not focusing sufficiently on in commenting only on the downsides of this. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
:> Now we have /etc/defaults/rc.conf, /etc/rc.conf, and /etc/rc.conf.local. :> Considerably less simple and quite unobvious. : :Erm... I thought that the point of /etc/defaults/rc.conf was that one :wouldn't touch it, and only work with rc.conf? : :(Haven't looked at the change myself, as my test machine is dead at the :moment) : :mela...@yip.org - Shave A Tree Today! (TM) Yah... kinda like nobody is supposed to touch /etc/rc, eh? /etc/rc - no touchee /etc/rc.conf- no touchee /etc/rc.local - touchees /etc/rc.conf.local - touchees That seems pretty obvious to me. I'm still partial to my /etc/rc.conf.N idea, where /etc/rc.conf.0 is a no-touchee and /etc/rc.conf.9 is the 'user can do whatever he wants with this file' touchee. The site configurator would mess with /etc/rc.conf.2. A post-install gui configurator would mess with either /etc/rc.conf.2 or /etc/rc.conf.3. -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
:> Now we have /etc/defaults/rc.conf, /etc/rc.conf, and /etc/rc.conf.local. :> Considerably less simple and quite unobvious. : :Until you have to upgrade to the latest set of "knobs"; that problem :is something I think people are not focusing sufficiently on in :commenting only on the downsides of this. : :- Jordan /etc/rc.conf - no touchee /etc/rc.conf.local - touchees People are still stuck in the 'I want to edit /etc/rc.conf' mode of thinking. I say that if you intend to put the /etc/rc.* scripts in /etc, and make them read-only ( /etc/rc, /etc/rc.network, /etc/rc.firewall, etc... ) then /etc/rc.conf should stay where it is and also be read-only. If you want to put 'read only' junk into /etc/defaults, then why aren't you also sticking /etc/rc, /etc/rc.network, /etc/rc.firewall, etc etc etc into /etc/defaults ? It makes no sense to have an /etc/defaults/ directory if you are still mixing read-only and user-modifiable files in /etc. -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
Which rc.conf do you mean? :) The one in defaults/ will do everything the old one did save source rc.conf.site. - Jordan > >Date: Tue, 09 Feb 1999 14:21:09 -0800 > >From: "Jordan K. Hubbard" > > >Since that made rc.conf.site obsolete, it was taken out of the > >configuration. Please move it to rc.conf on your system, should you > >be one of those folks who installed from an earlier snapshot and are > >now updating your /etc from -current or -stable sources (not likely to > >be all that many people). This change will also be in 3.1. > > OK; I gather that (by default) rc.conf will no longer be sourcing > rc.conf.local either? > > Thanks, > david (who is using a moderately recent SNAP for a growing number of machines ) > -- > David Wolfskill UNIX System Administrator > d...@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
> If you want to put 'read only' junk into /etc/defaults, then why aren't > you also sticking /etc/rc, /etc/rc.network, /etc/rc.firewall, etc etc etc > into /etc/defaults ? It makes no sense to have an /etc/defaults/ > directory if you are still mixing read-only and user-modifiable files > in /etc. There is an eventual plan to put more things into /etc/defaults, yes. One has to, however, start somewhere. :) - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
FreeBSD Crippleware (was Re: adding DHCP client to src/contrib/)
On Mon, 08 Feb 1999 22:34:52 PST, Steve Kargl wrote: > > How can we make this any clearer to you? Its fine to say `I don't > > want to see DHCP in the base system' when you have the choice > > of getting a static IP. A lot of the emerging high-speed access > > providers aren't giving you that option. > > Then, *BUY* the cd-rom and support the FreeBSD project. It took me a while to figure out what I didn't like about your punt. After all, the project could use the money. But something grated me about it nonetheless. Anyway, 30 minutes later, I've figured it out. You're endorsing FreeBSD crippleware. I sincerely hope that your attitude is _not_ endorsed by the core team. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
Personally, I have to side with Matt. I like to have ALL of the files in one directory. That way I can "grep ntpd /etc/rc*" and find ALL the line that are likely to affect it. Moving some of the files into another directory just complicates things. I like the idea of having all the "default knobs" in one file. I recommend /etc/rc.conf.defaults On Tue, 9 Feb 1999, Jordan K. Hubbard wrote: > > If you want to put 'read only' junk into /etc/defaults, then why aren't > > you also sticking /etc/rc, /etc/rc.network, /etc/rc.firewall, etc etc > > etc > > into /etc/defaults ? It makes no sense to have an /etc/defaults/ > > directory if you are still mixing read-only and user-modifiable files > > in /etc. > > There is an eventual plan to put more things into /etc/defaults, yes. > One has to, however, start somewhere. :) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
> I like the idea of having all the "default knobs" in one file. > I recommend /etc/rc.conf.defaults The problem is that this doesn't scale. We (Mike and I) already debated this one back and forth for awhile and decided that quite a few files in /etc were due to be ".defaulted" and if this were kept flat, you'd very quickly wind up with far too much crap in /etc to keep track of. I think people will get used to /etc/defaults fairly quickly, especially as we move more things into there which currently get clobbered by the `make distribute' rule in /usr/src/etc. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
: :Personally, I have to side with Matt. :I like to have ALL of the files in one directory. :That way I can "grep ntpd /etc/rc*" and find ALL the line that are likely :to affect it. Moving some of the files into another directory just :complicates things. : :I like the idea of having all the "default knobs" in one file. :I recommend /etc/rc.conf.defaults I like this idea ( /etc/rc.conf.defaults ) better then /etc/defaults/rc.conf. Maybe /etc/rc.conf.distribution instead of /etc/rc.conf.defaults. Either is better then /etc/defaults/rc.conf. I don't think we should have an /etc/defaults/ directory, but if it is insisted on then *ALL* the read-only files should be moved into it, not just one of them. -Matt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: was: some woes about rc.conf.site
On Sun, Feb 07, 1999 at 03:14:22PM -0500, Christopher Masto wrote: > I haven't used it yet, but I definately think the idea is an > improvement. I hate trying to update /etc after an upgrade.. if it's > been a while, or it's between major versions, it can take a very > significant amount of time. Have you tried the mergemaster port for this? It greatly speeds the task. > Anything that moves local changes to a > seperate file is a blessing. True. -- Adrian Wontroba To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
> : > :Personally, I have to side with Matt. > :I like to have ALL of the files in one directory. > :That way I can "grep ntpd /etc/rc*" and find ALL the line that are likely > :to affect it. Moving some of the files into another directory just > :complicates things. > : > :I like the idea of having all the "default knobs" in one file. > :I recommend /etc/rc.conf.defaults > > I like this idea ( /etc/rc.conf.defaults ) better then > /etc/defaults/rc.conf. As Jordan pointed out, this gets very messy very quickly. > I don't think we should have an /etc/defaults/ directory, but if > it is insisted on then *ALL* the read-only files should be moved into > it, not just one of them. All of the files that currently mix read-only and read-write data will, ideally, be split so that the read-only content goes into /etc/defaults, and the "local changes" stay in /etc. The next big candidate for this is make.conf, but that will require careful testing first. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: gpib driver - does anybody use it?
Andre Albsmeier writes: > Don't shoot me, but I would like to see it in 2.2.x if possible, > since 3.x-STABLE still has some problems which makes it impossible > for me to use it on production machines. No, 2.2 is dead now exept for bug fixes. Anyway, you're a committer - who's stopping you? DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: was: some woes about rc.conf.site
On Tue, Feb 09, 1999 at 10:11:48PM +, Adrian Wontroba wrote: > On Sun, Feb 07, 1999 at 03:14:22PM -0500, Christopher Masto wrote: > > I haven't used it yet, but I definately think the idea is an > > improvement. I hate trying to update /etc after an upgrade.. if it's > > been a while, or it's between major versions, it can take a very > > significant amount of time. > > Have you tried the mergemaster port for this? It greatly speeds the > task. Yes, I have. It doesn't make much of a dent in the real problem, which is separating diffs like: - portmap_enable="YES"# Run the portmapper service (or NO) + portmap_enable="YES"# Run the portmapper service (or NO). from - portmap_enable="NO" # Run the portmapper service (or NO). + portmap_enable="YES"# Run the portmapper service (or NO). from portmap_enable="YES"# Run the portmapper service (or NO). + portmap_flags=""# Flags to portmap (if enabled). ad infinitum. The latest "compromise" is still good enough for me. I just don't want to go back to having to edit the same file that I have to upgrade. -- Christopher MastoDirector of Operations NetMonger Communications ch...@netmonger.neti...@netmonger.nethttp://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
:As Jordan pointed out, this gets very messy very quickly.
:
:> I don't think we should have an /etc/defaults/ directory, but if
:> it is insisted on then *ALL* the read-only files should be moved into
:> it, not just one of them.
:
:All of the files that currently mix read-only and read-write data
:will, ideally, be split so that the read-only content goes into
:/etc/defaults, and the "local changes" stay in /etc. The next big
:candidate for this is make.conf, but that will require careful testing
:first.
I think it's a *BAD* idea to change rc.conf operation for the 3.1
distribution. Bad Bad Bad.
If you guys want to fix the read-only / read-write mess, fix it
for 3.2 and 4.x and don't just go piecemeal -- fix 90% of it right
off the bat. Move rc, rc.network, rc.firewall, rc.diskless{1,2},
rc.atm, rc.devfs, rc.isdn, rc.pccard, rc.serial, and rc.shutdown
into your defaults directory.
defaults is a bad name. Why not make it /etc/dist/ ?? for
'distribution files'. Much more obviously a 'do not mess with me'
directory then /etc/defaults is.
Either way, I really think we have enough problems to deal with
that changing rc.conf operation in 3.2 would just be asking for it.
-Matt
Matthew Dillon
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: gpib driver - does anybody use it?
"Jordan K. Hubbard" writes: > > Andre Albsmeier writes: > > > Don't shoot me, but I would like to see it in 2.2.x if possible, > > > since 3.x-STABLE still has some problems which makes it impossible > > > for me to use it on production machines. > > No, 2.2 is dead now exept for bug fixes. > > Anyway, you're a committer - who's stopping you? > Actually, I would. I would prefer to see 2.2.x left to die > in peace. The vinum import to that branch already has me on > edge enough as it is. I meant "who's stopping you from committing the driver", not "who's stopping you from committing the driver to 2.2". I too think 2.2 should be left to die in peace. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: gpib driver - does anybody use it?
Actually, I would. I would prefer to see 2.2.x left to die in peace. The vinum import to that branch already has me on edge enough as it is. - Jordan > Andre Albsmeier writes: > > Don't shoot me, but I would like to see it in 2.2.x if possible, > > since 3.x-STABLE still has some problems which makes it impossible > > for me to use it on production machines. > > No, 2.2 is dead now exept for bug fixes. > > Anyway, you're a committer - who's stopping you? > > DES > -- > Dag-Erling Smorgrav - d...@flood.ping.uio.no > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: gpib driver - does anybody use it?
> I meant "who's stopping you from committing the driver", not "who's > stopping you from committing the driver to 2.2". I too think 2.2 > should be left to die in peace. Well, before it is committed I would like to see one of you FreeBSD wizards to check it over for a half hour first. My experience with FreeBSD is one of rock-solid performance. I would hate to upset that impression for somebody else with this particular chunk of code. I wrote this driver to the best of my abilities, and I think it is good, but I don't spend every weekend with the FreeBSD source code like some of you guys do. I can say with 100% certainty that my driver works much faster, more reliably, and with more features than the current gp driver distributed with FreeBSD for _me_. This will probably be true for most other people as well. However, that doesn't mean that this code is the end all and shouldn't be committed without being checked over by one of you FreeBSD-god types. Maybe this is just my own anxiety over my FreeBSD-contributer virgin status, but it seems wise. Should I send it in with this "send-pr" command myself, or should I let one of you guys do it? John -- John Galbraithemail: j...@ece.arizona.edu University of Arizona,home phone: (520) 327-6074 Los Alamos National Laboratorywork phone: (520) 626-6277 home page: www.ece.arizona.edu:/~john "As had been true historically, Gates' concern was not making great products, but keeping the world locked into using his products." --- Wendy Goldman Rohm, The Microsoft File To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
On Tue, 9 Feb 1999, Matthew Dillon wrote: > I think it's a *BAD* idea to change rc.conf operation for the 3.1 > distribution. Bad Bad Bad. I have to agree. Let's not forget that there are over 30 man pages with references to /etc/rc.conf. There is already enough confusion over wcd in /dev with everything else refering to it as acd, and no documentation about when to just ignore "tagged openings now ". Both of these issues are already popping up in questions and the news groups. -- Jack O'NeillSystems Administrator / Systems Analyst j...@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger j...@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
HEADS UP: devstat changes
I have just commited changes to devstat(9) that will require recompilation of the following things: libdevstat [ do this first! ] systat iostat vmstat rpc.rstatd You'll have to recompile those things in order to use them with the new kernel changes. You will probably also have to recompile any ports that depend on libdevstat. (I think there are 2 or 3 sysinfo type ports that depend on it.) A buildworld/installworld will of course do all the upgrades automatically, and that's the recommended course of action. For those who are interested: the changes implement different sorting priorities for different devices, so that, for instance, da devices now appear before fd devices, instead of after. i.e., "more interesting" devices appear before "less interesting" devices. Thanks for Bruce Evans and David O'Brien for suggestions, reviewing the code, etc. Ken -- Kenneth Merry k...@plutotech.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: gpib driver - does anybody use it?
> Should I send it in with this "send-pr" command myself, or should I Please, thanks! - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
FW: adding DHCP client to src/contrib/
In addition to Irix 6.5, you should also add Irix 6.3 and 6.4 to that list. It's been there since 6.3 first shipped on the O2s in '97. -steve From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of John Fieber Sent: Tuesday, February 09, 1999 12:41 PM To: obr...@freebsd.org Cc: curr...@freebsd.org Subject: Re: adding DHCP client to src/contrib/ On Tue, 9 Feb 1999, David O'Brien wrote: > On Tue, Feb 09, 1999 at 09:27:44AM -0700, Lyndon Nerenberg wrote: > > > > PlatformHas DHCP > > > > Irix 6.5Yes > > Solaris 2.5.1 No > Solaris 2.6 Yes > > You should have used a more modern Solaris. It helps your argment. :-) Digital Unix 4.0Yes -john To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
I understand the scaling issue. However, I like to keep related things in one place. Perhaps we need to move ALL the rc files into a common directory. As for the "read-only" argument, I recommend, for those who wish to separate them, symbolic links from the read only area to a writable area. When that is not important, keeping them together can have advantages. Please understand that I support the general direction of these changes. However, since it is just about the same effort to implement any of the proposals and the "status quo" has a big advantage, I think that it is important to discuss the implications of each of the stratagies before commiting to any of them. PS: The same applies to DHCP. Since some of the well respected "names" have also supported ISC-DHCP, I hope that we can reach a concensus before anyone is allowed to make their bias the "de-facto" answer. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
On Tue, 9 Feb 1999, jack wrote: > On Tue, 9 Feb 1999, Matthew Dillon wrote: > > > I think it's a *BAD* idea to change rc.conf operation for the 3.1 > > distribution. Bad Bad Bad. > > I have to agree. Let's not forget that there are over 30 man > pages with references to /etc/rc.conf. Lets not forget that with the latest round of changes, the rc.conf in 3.1 will behave exactly as it has in the past. Think about it. rc.conf was a "touchees" file in the past and it is a "touchees" file now. The only difference is the addition of a "no touchees" reference copy in /etc/defaults that gets sourced before rc.conf so any essential variables introduced in an upgrade will have a safety fallaback in case you don't properly upgrade your rc.conf. The detour with rc.conf.site *did* change the way rc.conf was used. That was Bad Bad Bad and has just been fixed. -john To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
>From: "Daniel C. Sobral" > >>Steve Kargl wrote: >> >> > > The plan is to make a boot floppy / boot CDROM with a DHCP client on it. >> >> Content-Type: text/BLOAT >> >> These should be left has ports. > >I disagree. It is very common nowadays to need to extract your IP >address through DHCP. Not having a DHCP boot floppy/cd is a serious >disadvantage. > Make a boot floppy with BPF and a DHCP client. When a user installs via the network, ensure a VERY PROMINENT splash screen indicates that the basic NO-BPF kernel has been installed (ie - the normal distribution kernel) and that NO DHCP CLIENT is installed on the hard drive and that the BPF will NOT be available upon reboot. Then offer the option to install either the WIDE or ISC client via the package mechanism and a BPF-enabled GENERIC kernel. This mechanism ensures that people in a DHCP environment can install via the network without causing the security- and bloat-minded people to have a brain hemmorage. If the installers using the DHCP boot disk don't follow the instructions and install a proper package or a BPF-enabled kernel, they are SOL for not having read the dialog boxes. --Jason j.b.georgeieee.org jbgmasterplan.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
