Re: some woes about rc.conf.site
On Sun, Feb 07, 1999 at 12:48:13PM -0800, Mike Smith wrote: > > I hate it unreservedly. If we need a source of seeded default values, > we should have rc.conf.default, uncommented, read-only. rc.conf is > where people expect to make their changes, and it is immensely bogus to > have sysinstall creating rc.conf.site which is quietly included *after* > everything in rc.conf (so that when someone changes rc.conf, the change > is overridden). I hate to be an AOL'er, but I would like to voice agreement with Mike. It seems we are coming very close to violating POLA and a web of stacking. On Sun, Feb 07, 1999, John Fieber wrote: > > As for for all the debate on the name, if it is supposed to be an > untouchable file, the name of rc.conf has GOT to change. IF things are too far along to break from the current path, John is very right that the name has to change. Remember, we changed the name from /etc/sysconfig to /etc/rc.conf due to overwhelming requests from sysadmins for us to be similarly named with other Unixes. People expect to edit /etc/rc.conf. -- -- 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
man page for syscons(4)
I wrote a draft man page for syscons(4). (It's not as comprehensive as it should be, though.) http://www.freebsd.org/~yokota/syscons.4 Please review the draft and give me some comments. We shall add it to RELENG_3 before 3.1 comes out, if possible. Kazu To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Floppy Tape Driver.....
On Sun, Feb 07, 1999 at 02:03:58PM -0800, Mike Holling wrote: > > Hmm.. I don't believe this can be true however. I do not program but > > I do run current on my workstation, it's just plain interesting thing > > to do. Just my opinion. > > If you're running -current, you should at least be able to apply kernel > patches... Certainly :) I agree completely with your statement, but... once is the first time to do it and you have to ask how to do it. Manual pages are sometimes so hard to understand for beginners, I haven't forgot my first steps yet. Well, I shut up now, it's wrong topic for -current. -- Vallo Kallaste va...@matti.ee To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Boot problems with -CURRENT and -STABLE tree
hello! I have some critical problems with fbsd. When I try to boot with fbsd install disk (boot.flp), my system is halt. I tried different versions of fbsd from 2.2.8R and 3.0-STABLE till 4.0-CURRENT. I have IBM server, model 8640ES0, with PPro 200, 128 MB RAM, SCSII-adapter AIC-7880 (it was "modified to better" :-/ by IBM's hands), SCSII CD-ROM IBM CDRM00203, 2 SCSII HDD - IBM DCAS-34330W and QUANTUM EMPIRE_1080S I think SCSII driver cannot correct work with my SCSII-adapter, becose system halted after kernel say "Waiting 15 seconds to settle SCSII devices" But some last snaps (by 4,5,6 january) halted my system after uncompressing kernel: it say "Uncompressing kernel" and freeze computer. I obligate to work with Linux on that server now, but I didn't prefer this OS. Can anybody comment this situation? (sorry for my english :) With best regards, -- Vladimir G. Drobyshevsky system administrator 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
> -Original Message- > From: Christopher Masto [mailto:ch...@netmonger.net] > Sent: 07 February 1999 20:14 > To: curr...@freebsd.org > Subject: Re: was: some woes about rc.conf.site > > > 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. Anything that moves local changes to a > seperate file is a blessing. > > Also, having had sysinstall destroy my /etc/rc.conf on more than one > occasion, I am grateful to not have it touched any more. I don't understand what rc.conf.site buys us, surely sysinstall is just an admin tool for maintaining site specific options in exactly the same way that vi /etc/rc.conf.local would be? I think it's getting overly engineered and we're just chasing our tails. Why can't there be a set of shipped defaults, set in /usr/share that is never touched by local sites and by definition will always be up to date and then have a single file /etc/rc.conf that provides local overrides. Whether you maintain it with sysinstall or vi shouldn't really matter. Paul. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: some woes about rc.conf.site
On Sun, 7 Feb 1999, Mike Smith wrote: > I hate it unreservedly. If we need a source of seeded default values, > we should have rc.conf.default, uncommented, read-only. rc.conf is Absolutely...agreed! _ Lauri Laupmaa ...speaking for myself only... To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: [Call for Review] new ioctl for src/sys/pccard/*
Thank you for your comment. Mike Smith wrote: > But this diagram worries me. Does this explicitly disallow physical > removal without a preceeding virtual removal? No. This is for card such as: o Some cards go unstable when it is removed from slot with power on. But turning off the power of that card with this ioctl, this may be going to remove safety. > Just to be clear, I have no objections to that approach, but it's > something that we would want to make very clear if we're going to make > this change. I don't think my sentence is clear explanation. Feel free to make more questions about it. I'll try to explain it. Thanks. -- Jun Kuriyama // kuriy...@sky.rim.or.jp // kuriy...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: [Call for Review] new ioctl for src/sys/pccard/*
Thank you for your comment.
Nate Williams wrote:
> The patch implementing these changes are adequate in the kernel, but are
> incomplete.
Yes, I should have attached patch for usr.sbin/pccard/* too.
> What about the changes to usr.sbin/pccard/*? With regard
> to the power-on modifications, it is necessary to see these changes for
> insertion/removal as well as suspend/resume, not to mention the
> documentation changes.
Hmmm, I'm planning to change pccardc like below. Only functional
additions. Could you point out where we should modify with these
changes?
> ps. I like the new 'beep' ioctl better than the original implementation
> in PAO.
Thanks. But I've changed only a little from PAO implementation. I like
PAO's melodious beep sound (that isn't included in this patch), what you
said is this?
# Of course, I think that is not "must needed" feature. :-)
--
Jun Kuriyama // kuriy...@sky.rim.or.jp
// kuriy...@freebsd.orgIndex: pccardc/Makefile
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardc/Makefile,v
retrieving revision 1.7
diff -u -r1.7 Makefile
--- Makefile1998/02/26 14:36:00 1.7
+++ Makefile1999/02/08 11:50:25
@@ -5,7 +5,7 @@
#
PROG= pccardc
NOMAN= noman
-SRCS= dumpcis.c enabler.c pccardc.c pccardmem.c printcis.c \
+SRCS= beep.c dumpcis.c enabler.c pccardc.c pccardmem.c power.c printcis.c \
rdattr.c rdmap.c rdreg.c readcis.c wrattr.c wrreg.c
CFLAGS+= -I${.CURDIR}/../pccardd
Index: pccardc/beep.c
===
RCS file: beep.c
diff -N beep.c
--- /dev/null Mon Feb 8 20:41:26 1999
+++ beep.c Mon Feb 8 20:49:00 1999
@@ -0,0 +1,77 @@
+/*
+ * Copyright (c) 1995 Andrew McRae. All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
+ *notice, this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright
+ *notice, this list of conditions and the following disclaimer in the
+ *documentation and/or other materials provided with the distribution.
+ * 3. The name of the author may not be used to endorse or promote products
+ *derived from this software without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+ * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+ * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+ * IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+ * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+ * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+ * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+ * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+
+/*
+ * Code cleanup, bug-fix and extension
+ * by Tatsumi Hosokawa
+ */
+
+#ifndef lint
+static const char rcsid[] =
+ "$Id$";
+#endif /* not lint */
+
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+
+#include
+
+int
+beep_main(argc, argv)
+ int argc;
+ char *argv[];
+{
+ int fd, newstat, valid = 1;
+ charname[64], *p;
+
+ if (argc != 2)
+ valid = 0;
+ if (valid) {
+ for (p = argv[1]; *p; p++) {
+ if (!isdigit(*p)) {
+ valid = 0;
+ break;
+ }
+ }
+ }
+ if (!valid)
+ errx(1, "Usage: %s beep newstat", argv[0]);
+
+ sscanf(argv[1], "%d", &newstat);
+ sprintf(name, CARD_DEVICE, 0);
+ fd = open(name, O_RDWR);
+ if (fd < 0)
+ err(1, "%s", name);
+ if (ioctl(fd, PIOCSBEEP, &newstat) < 0)
+ err(1, "ioctl (PIOCSBEEP)");
+ return 0;
+}
Index: pccardc/pccardc.c
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardc/pccardc.c,v
retrieving revision 1.7
diff -u -r1.7 pccardc.c
--- pccardc.c 1998/02/26 14:36:01 1.7
+++ pccardc.c 1999/02/08 11:51:17
@@ -36,10 +36,12 @@
typedef int (*main_t)(int, char **);
#define DECL(foo) int foo(int, char**);
+DECL(beep_main);
DECL(dumpcis_main);
DECL(enabler_main);
DECL(help_main);
DECL(pccardmem_main);
+DECL(power_main);
DECL(rdattr_main);
DECL(rdmap_main);
DECL(rdreg_main);
@@ -51,10 +53,12 @@
main_t func;
char *help;
} subcommands[] = {
+ { "beep", beep_main, "Beep type
Identd problems
'lo all - On Friday, I did a make world from that day's sources. The previous build had been in early December I think. Anyway, once I got the new sources down and compiled I started seeing funny problems with identd (2.8.2) - telnetting to the identd port would work fine, but IRC servers wouldn't allow me to connect - they complained they couldn't talk to identd. I installed 2.8.5 today, and with the -l option in inetd.conf, I saw these messages when trying to connect to an IRC server: Feb 8 10:16:43 orthanc identd[9960]: getbuf: bad address (01c2 not in f0117580-0xFFC0) - pfd Anyone have any insight? Thanks, Peter -- - Peter Cox - Systems Administrator, Phone: (847) 467 1842 Kellogg Graduate School of Management, Fax: (847) 467 3500 Northwestern University.Email: p-...@nwu.edu - "Protozoa are small, and bacteria are small, but viruses are smaller than the both put together." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: [Call for Review] new ioctl for src/sys/pccard/*
> Nate Williams wrote: > > The patch implementing these changes are adequate in the kernel, but are > > incomplete. > > Yes, I should have attached patch for usr.sbin/pccard/* too. The changes to pccardd to support the new 'inactive' flag are still missing. We can power the slot on/off, but pccardd is unaware of these changes. Doesn't it need to be aware of the new 'power' state? Nate > > ps. I like the new 'beep' ioctl better than the original implementation > > in PAO. > > Thanks. But I've changed only a little from PAO implementation. I like > PAO's melodious beep sound (that isn't included in this patch), what you > said is this? Right. Last I looked at PAO the pccard code had modifications all over the kernel. Nate To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: some woes about rc.conf.site
On Sun, Feb 07, 1999 at 04:33:00PM -0800, Parag Patel wrote: > > Because rc.conf contains configuration variables, whereas rc contains > > commands to execute at boot time. > > Then I would suggest renaming rc.conf to be rc.vars or rc.config-vars > or something more appropriate than rc.conf, which like all the other > *.conf files is intended for local editing and maintainence. > > I do like the local overriding feature though. Yesterday I took out > all my local rc.conf mods into rc.conf.local and copied in the default > /usr/src/etc/rc.conf to /etc. The local mods are much smaller and much > more obvious as to what is different from the default setup. I think rc.conf and nothing else wasn't that bad. rc.conf was a _reference_ for all possible settings and easy manageable. And mergemaster is an excellent tool, to update it on demand. -- Andreas Klemmhttp://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: imgact_shell.c ENOEXEC
Tony Kimball writes: > : Imagine this: > : > : $ file /tmp/test.sh > : /tmp/test.sh: a /tmp/test.sh script text > : $ /tmp/test.sh > > Won't this just fail when the recursion level is such that > the command length exceeds stringspace? > > Ah, I see the difference: > /* >* Copy to end of token. No need to watch stringspace >* because this is at the front of the string > buffer >* and the maximum shell command length is tiny. >*/ > > Very bogus. So file a PR, preferably with patches.. :-) Seriously, it's good to take note of little things like this.. -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
Re: some woes about rc.conf.site
> Hopefully that is now fixed. It is. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
HEADS UP: CVSup "SetAttrs" messages
Replies to curr...@freebsd.org only, please. I am doing some final beta testing before releasing a new version of CVSup. When you run your next CVSup update from a FreeBSD mirror site, you may find that it spews out a whole bunch of "SetAttrs" messages. Or, maybe not. :-) It depends on a lot of things. Anyway, don't be alarmed. The new version is stricter about the way it preserves file permissions. The first time you update from a server using the new version, it may do a lot of SetAttrs to correct the information in its "checkouts" files. You won't see it again on subsequent updates. Replies to curr...@freebsd.org only, please. John --- 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: SKIP on 3.0 ? lkm vs kld = SOL ?
Mike Tancsa writes: > OK, looking back at some of the threads, it seems I am hosed since the ELF > cannot load klds ? Is that correct ? > > Are there any other options for VPN on the 3.0 branch ? SKIP wasnt/isnt > the greatest, but I had decent luck with it on the 2.2 branch of things... I hope to get the SKIP port converted from a LKM to a KLD soon.. but it will be a couple of weeks at best. In the meantime I'd suggest staying with 2.2.x for now.. -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
Tracking a Fatal Double Fault
Can someone please give me a short guide on how to track down a fatal double fault? System is 3.0-19990205-STABLE, and I've written down the fault info. Thanks, -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
adding DHCP client to src/contrib/
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. -- -- 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 02:28:20PM -0800, David O'Brien wrote: > 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. Content-Type: text/applause Yaay! 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/
Hi, On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote: > I am planning on adding the Wide-DHCP client to src/contrib/ and > src/sbin/ in a few days. speaking about DHCP-things (clients and servers) I would like to hear from some 'export' on choosing a the 'right' dhcp-software for FreeBSD. I'm mostly interested in choosing the server part. In the past I deployed only the wide-dhcp server from the ports collection; but only because I somehow decided to test the wide-dhcp before the isc one. A few days ago I had a look (triggered by a piece of samba documentation) at isc-dhcp and found the configuration syntax somewhat more user friendly. Are there any really hard facts on how to decide? > The plan is to make a boot floppy / boot CDROM with a DHCP client on it. fine. Kind regards, Andreas -- : TSE TeleService GmbH : Gsf: Arne Reuter: : : Hovestrasse 14: Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP: :: : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : 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/
Joe Abley wrote: > On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote: > > 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. > > Content-Type: text/applause > Content-Type: text/BLOAT These should be left has ports. -- Steve finger ka...@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html 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/
> speaking about DHCP-things (clients and servers) I would like to > hear from some 'export' on choosing a the 'right' dhcp-software > for FreeBSD. > I'm mostly interested in choosing the server part. In the past I > deployed only the wide-dhcp server from the ports collection; but > only because I somehow decided to test the wide-dhcp before the isc one. > > A few days ago I had a look (triggered by a piece of samba documentation) > at isc-dhcp and found the configuration syntax somewhat more user friendly. > > Are there any really hard facts on how to decide? FWIW, I've integrated both the WIDE DHCP client and server pieces into a PicoBSD image. I started out trying with ISC, but WIDE ended up being much easier to deal with. The ISC server does have a nicer configuration syntax, but the WIDE client is easier to get going with. - 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/
> 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. I tried both, and I must say that ISC was easier to use and configure. It also seems to work better, at least as a server. I couldn't get Wide-DHCP to work, but it's been a while since I tried though... I don't know why you think the termcap-type configuration is easier to understand than ISCs configuration :-) Dan Eischen eisc...@vigrid.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Tracking a Fatal Double Fault
> Can someone please give me a short guide > on how to track down a fatal double fault? > System is 3.0-19990205-STABLE, and I've written > down the fault info. Ack. It's actually pretty difficult. You can start by trying to locate the PC for the fault in the kernel image, but the typical cause of a double fault is running out of kernel stack. Are you running any custom kernel code? -- \\ 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
gpib driver - does anybody use it?
I stumbled upon the (undocumented) gpib driver today - apparently for the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to LINT. Apart from staticization sweeps, -Wall fixes and the like, nobody's touched it since 1995. Does anybody have an AT-GPIB board, or even know what it is? Does the driver actually work? Is there a good reason (or any reason at all) why we shouldn't just bobbit it? 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: Tracking a Fatal Double Fault
The machine is running a custom kernel, but nothing very unusual. My instinct is that it may be related to something with the 3c905B 3COM cards that I reported earlier, I'm trying with Intel EtherExpresses right now and getting no fault problems. The double-fault does not occur consistently, unfortunately, and typically only occurs during my rc.local stuff (loading a bunch (100+) of chrooted daemons) on boot-up. Would the eip/esp/ebp values be worth sending? -Troy Cobb Circle Net, Inc. http://www.circle.net > -Original Message- > From: Mike Smith [mailto:m...@smith.net.au] > Sent: Monday, February 08, 1999 6:55 PM > To: tc...@staff.circle.net > Cc: curr...@freebsd.org > Subject: Re: Tracking a Fatal Double Fault > > > > Can someone please give me a short guide > > on how to track down a fatal double fault? > > System is 3.0-19990205-STABLE, and I've written > > down the fault info. > > Ack. It's actually pretty difficult. You can start by trying to > locate the PC for the fault in the kernel image, but the > typical cause > of a double fault is running out of kernel stack. > > Are you running any custom kernel code? > > -- > \\ 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?
> I stumbled upon the (undocumented) gpib driver today - apparently for > the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to > LINT. Apart from staticization sweeps, -Wall fixes and the like, > nobody's touched it since 1995. Does anybody have an AT-GPIB board, or > even know what it is? Does the driver actually work? Is there a good > reason (or any reason at all) why we shouldn't just bobbit it? Yes, Yes, Yes, not yet, as the replacement's not ready. John Galbraith was working on a replacement; I haven't heard from him for a while now, but I know he had some very happy beta-testers in the field. -- \\ 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?
>I stumbled upon the (undocumented) gpib driver today - apparently for >the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to >LINT. Apart from staticization sweeps, -Wall fixes and the like, >nobody's touched it since 1995. Does anybody have an AT-GPIB board, or >even know what it is? I don't have one, but I know what these are. It's an interface for talking to lab equipment like voltmeters, scanners, all sort of stuff. All this "stuff" of course has to have a GPIB interface as well, but it gets used a lot by those types of people. If I worked in a lab, I'd almost assuredly be using the driver. No idea if it works. >Is there a good reason (or any reason at all) why we shouldn't just >bobbit it? It kills me to watch this go, but the surest way to bring a maintainer out of the woodwork is to kill it. :-) If I still used this stuff, I think this would be a *great* project to call my own. Deep sigh. But it's all in the CVS tree, so if someone pops up, hey the stuff is still there for the resurrection. Brian 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 writes: > > On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote: > > > I am planning on adding the Wide-DHCP client to src/contrib/ and > > > src/sbin/ in a few days. > [...] > These should be left has ports. 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. 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: Tracking a Fatal Double Fault
> The machine is running a custom kernel, but nothing > very unusual. My instinct is that it may be related to > something with the 3c905B 3COM cards that I reported > earlier, I'm trying with Intel EtherExpresses right now > and getting no fault problems. > > The double-fault does not occur consistently, unfortunately, > and typically only occurs during my rc.local stuff (loading > a bunch (100+) of chrooted daemons) on boot-up. > > Would the eip/esp/ebp values be worth sending? They're meaningless without your kernel, but even then all you're going to be able to tell is where in the fault handler things died; you won't know the address of the original fault. There's nothing immediately obvious in the xl driver that would suggest that it uses excessive kernel stack either. 8( Maybe someone has some clues on measuring stack usage (or simply on how to increase the kernel stack allocation...). -- \\ 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?
Dag-Erling Smorgrav wrote: > I stumbled upon the (undocumented) gpib driver today - apparently for > the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to > LINT. Apart from staticization sweeps, -Wall fixes and the like, > nobody's touched it since 1995. Does anybody have an AT-GPIB board, or > even know what it is? Does the driver actually work? Is there a good > reason (or any reason at all) why we shouldn't just bobbit it? > 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. -- Steve finger ka...@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html 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?
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. 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/
Dag-Erling Smorgrav wrote: > Steve Kargl writes: > > > On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote: > > > > I am planning on adding the Wide-DHCP client to src/contrib/ and > > > > src/sbin/ in a few days. > > [...] > > These should be left has ports. > > 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. -- Steve finger ka...@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html 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?
Judging by the traffic on it over the last year it's in use widely. On Mon, 8 Feb 1999, Brian Handy wrote: > >I stumbled upon the (undocumented) gpib driver today - apparently for > >the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to > >LINT. Apart from staticization sweeps, -Wall fixes and the like, > >nobody's touched it since 1995. Does anybody have an AT-GPIB board, or > >even know what it is? > > I don't have one, but I know what these are. It's an interface for > talking to lab equipment like voltmeters, scanners, all sort of stuff. > All this "stuff" of course has to have a GPIB interface as well, but it > gets used a lot by those types of people. If I worked in a lab, I'd > almost assuredly be using the driver. No idea if it works. > > >Is there a good reason (or any reason at all) why we shouldn't just > >bobbit it? > > It kills me to watch this go, but the surest way to bring a maintainer out > of the woodwork is to kill it. :-) If I still used this stuff, I think > this would be a *great* project to call my own. Deep sigh. But it's all > in the CVS tree, so if someone pops up, hey the stuff is still there for > the resurrection. > > > Brian > > > 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
buildworld failure in /usr/src/sys/i386/ibcs2/ibcs2_ipc.c
4.0 -current touch opt_spx_hack.h cc -O -pipe -DCOMPAT_IBCS2 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/ibcs2 -I/usr/obj/usr/src/sys/modules/ibcs2/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_errno.c cc -O -pipe -DCOMPAT_IBCS2 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/ibcs2 -I/usr/obj/usr/src/sys/modules/ibcs2/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: warning: `struct ibcs2_ipc_perm' declared inside parameter list /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: warning: its scope is only this definition or declaration, /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: warning: which is probably not what you want. /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:59: warning: `struct ibcs2_ipc_perm' declared inside parameter list /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_msqid2imsqid': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:71: warning: passing arg 2 of `cvt_perm2iperm' from incompatible pointer type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_imsqid2msqid': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:90: warning: passing arg 1 of `cvt_iperm2perm' from incompatible pointer type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_iperm2perm': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:185: argument `ipp' doesn't match prototype /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:59: prototype declaration /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:186: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:187: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:188: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:189: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:190: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:191: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:192: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_perm2iperm': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:199: argument `ipp' doesn't match prototype /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: prototype declaration /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:200: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:201: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:202: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:203: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:204: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:205: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:206: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_semid2isemid': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:214: warning: passing arg 2 of `cvt_perm2iperm' from incompatible pointer type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_isemid2semid': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:227: warning: passing arg 1 of `cvt_iperm2perm' from incompatible pointer type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_shmid2ishmid': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:318: warning: passing arg 2 of `cvt_perm2iperm' from incompatible pointer type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_ishmid2shmid': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:335: warning: passing arg 1 of `cvt_iperm2perm' from incompatible pointer type *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. 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?
Dag-Erling Smorgrav wrote: > 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. > I may have been one of the few people testing for John of -current (pre 3.0-RELEASE), but the machine I was using has developed CPU, memory, and disk problems. I have not had a chance to (stress) the driver, yet. -- Steve finger ka...@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html 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?
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. 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: Tracking a Fatal Double Fault
On Mon, 8 Feb 1999, Mike Smith wrote: > > The machine is running a custom kernel, but nothing > > very unusual. My instinct is that it may be related to > > something with the 3c905B 3COM cards that I reported > > earlier, I'm trying with Intel EtherExpresses right now > > and getting no fault problems. > > > > The double-fault does not occur consistently, unfortunately, > > and typically only occurs during my rc.local stuff (loading > > a bunch (100+) of chrooted daemons) on boot-up. > > > > Would the eip/esp/ebp values be worth sending? > > They're meaningless without your kernel, but even then all you're going > to be able to tell is where in the fault handler things died; you won't > know the address of the original fault. > > There's nothing immediately obvious in the xl driver that would suggest > that it uses excessive kernel stack either. 8( Maybe someone has some > clues on measuring stack usage (or simply on how to increase the kernel > stack allocation...). While you guys are on this subject, I'd like to sneak in a question on a subject that's close by. A while back, I had a kernel problem, and went about finding out how to use kgdb and kernel dumps. Unfortunately, by the time I was completely ready to do it, the problem (you guys remember the GPL_MATH_EMULATE thing?) went away. Just for grins, I'd like to force a kernel dump, so I can go the rest of the way in making sure my test setup works, and I can get more used to it. What's the safest way to force a kernel dump (hopefully without screwing filesystems)? +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
RE: Tracking a Fatal Double Fault
So a double-fault is always a kernel stack problem? I find it suspicious that this same machine also had trouble with the 3c905B flaking out -- dropping packets during an ifconfig alias, and sometimes never reactivating the interface according to what tcpdump shows. The 3c905B problem repeates itself on EVERY machine that I've them installed into (7 or so), the double-faults are infrequent on some of the busier machines, and almost always during the initial boot process. -Troy Cobb Circle Net, Inc. http://www.circle.net > -Original Message- > From: Mike Smith [mailto:m...@smith.net.au] > There's nothing immediately obvious in the xl driver that > would suggest > that it uses excessive kernel stack either. 8( Maybe > someone has some > clues on measuring stack usage (or simply on how to > increase the kernel > stack allocation...). > > > -- > \\ 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/
Steve Kargl writes: > Dag-Erling Smorgrav 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. None of these are necessary on an average workstation. DHCP is becoming more and more common. 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: some woes about rc.conf.site
>Date: Sun, 07 Feb 1999 12:48:13 -0800 >From: Mike Smith >> What do you think ? Or what are your experiences ? >I hate it unreservedly. If we need a source of seeded default values, >we should have rc.conf.default, uncommented, read-only. rc.conf is >where people expect to make their changes, and it is immensely bogus to >have sysinstall creating rc.conf.site which is quietly included *after* >everything in rc.conf (so that when someone changes rc.conf, the change >is overridden). I confess that I experienced what sure felt like a POLA violation when I set up a system with a recent 3.0-SNAP (from about 01 February or so): Since it was on a scratch box, I did a fresh install. But I wanted to see what it would take to make the box "play nice" on our internal Engineering network. So immediately after sysinstall finished, and I told the system to boot single-user (since sysinstall doesn't seem to provide a way to specify the NIS domain name), and: fsck -p mount -a cd vi .cshrc [change EDITOR from "ee" to "vi"] csh cd /etc mkdir /RCS ci -u sendmail.cf rc.conf fstab printcap group inetd.conf [hand-enter descriptions of each file] co -l !:3* vi !:2* [hand-enter the NIS domain. Also change the amd_map_program & amd_flags; those are easier to change w/ a normal editor. Do reality check on everything else in rc.conf.] [Add MFS-mounted /tmp.] [Add a couple of networked printers.] [Add the NIS "magic cookie" to /etc/group.] [Add the amanda client-side entry.] ci -u !* [hand-enter brief descriptions of the above] vipw [Add NIS "magic cookie" to passwd.] reboot intending to come up multi-user. (Note that I had deliberately not changed sendmail.cf yet; that comes later.) Machine comes up... amd says "no work to do--quitting". Huh? I try logging in (as "dhw"); no go. ??!? Login as root; works fine. "ls -F ~dhw/" -- no such user. Foo. "domainname"... null. :-( "grep nis /etc/rc.conf" -- yeah; the domain name is set. ??!??! *Then* my manager points out rc.conf.site. :-( So I check *that* file in & out, edit it, check it back in, come up multi-user, and things are *much* happier. So then I'm able to cd /etc cp -p /usr/local/share/sendmail/cf-8.9.2/cf/dhw.cf sendmail.cf ci -u !$ kill `head -1 /var/run/sendmail.pid` && tail -f /var/log/maillog OK so far (Then all I needed to do was un-tar a bunch of the a.out libraries (as well as /usr/libexec/ld.so) where they can be found.) *Then* I was able to login Later, on another machine (on an engineer's desk), I've upgraded the box to that SNAP. And now he's re-booted, and can't login. I login as root, and we happen to look at the results of rcsdiff -u /etc/rc.conf.site ??!? All kinds of changes Then he says he was doing some things with sysinstall. :-( Fine; "co /etc/rc.conf.site" restores it back again. Re-boot, and he can login again Seems that whatever he did completely trashed thinsg like the NIS domain name OK; this note is way too long already But it does seem to me that there's a bit of a POLA violation, if nothing else, in the naming. You see, when I got here, I inherited a network where /usr/local was NFS-exported from a box (that is now running 2.2.6-R). And this seems to be rather at odds with the expectation of the "ports" system. Now, since this has been my first experience with FreeBSD, I didn't know any better... and I had no idea how much hassle this usage of /usr/local would be in an environment where such a "ports" system is used. Further, having /usr/local be "site-local" vs. "machine-local" isn't all that unusual in the environments I've used and administered before (mostly Suns). But if /usr/local is expected to be machine-specific, it seems to me that what sysinstall messes with should also be machine-specific, and the names should be of a similar pattern. At the same time, there is value in having a site-specific configuration file (just as there is value in having some site-wide files, some of which may well be executables). I would expect, moreover, that the machine-specific information would override the site-specific information. I hope that was of *some* use (or interest, at least), david -- 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: adding DHCP client to src/contrib/
> > 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. Here are the regular (dynamically linked) versions of the ISC client and server: phluffy% ls -l =dhclient =dhcpd -rwxr-xr-x 1 root wheel 86016 Nov 20 20:47 /usr/local/sbin/dhclient -rwxr-xr-x 1 root wheel 90112 Nov 20 20:47 /usr/local/sbin/dhcpd I built a static version of the WIDE client and server, both were only around 140K. What's the problem? It's not like putting emacs in the base install or anything. I still run FreeBSD on a 386/40 with a 40M MFM main drive, and even so I'm not worried about the "bloat" of adding DHCP. Lots of people have been asking about DHCP on the lists and the newsgroups, probably because DSL/cablemodems are becoming more readily available (at least in the US). Windows comes with DHCP. Heck, even my old Mac IIci running System 7.5.5 comes with DHCP. It's small and increasingly useful, why not make it part of the base distribution? Or would you rather have FreeBSD be like RedHat, where you have to install an RPM for just about everything? Personally, I'd like to see DHCP in /usr/src because that makes it easier to integrate with PicoBSD. - 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/
On 09-Feb-99 Steve Kargl wrote: > So, we'll import a pop server, apache, g77, ad nauseam > to increase the credibility of FreeBSD as a workstation OS. Yes, of course, I need a pop server to install freesbsd.. NOT. Lots of places use DHCP and in some cases you can't actually use the network without a DHCP client (cable modems, some campuses etc) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum 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 agree. having a DHCP client can make the difference between being able to get ont he net at all and not being able to get on the net. On 9 Feb 1999, Dag-Erling Smorgrav wrote: > Steve Kargl writes: > > Dag-Erling Smorgrav 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. > > None of these are necessary on an average workstation. DHCP is > becoming more and more common. > > 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: adding DHCP client to src/contrib/
Hi, ...sorry, I just didn't get it ... On Mon, Feb 08, 1999 at 04:32:39PM -0800, Steve Kargl wrote: > > > > > I am planning on adding the Wide-DHCP client to src/contrib/ and ^^ ^^^ ! client ! > > > > > src/sbin/ in a few days. > > > [...] > > 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. Read his statement again; the (IMHO very valuable) itention is to be able to build a "sysinstall boot floppy" for network-installations without having the installing person go through the hassle of setting up a _static_ ip configuration. (Especially if the workstation should be a dhcp client later on.) Furthermore I know more than one network where 'dhcp' is the only mean to get a valid ip-configuration. Scenario: User-A wants to setup his brand new FreeBSD-workstation: [without dhcp-client on boot-disk] - boot the bootdisk ;) - choose distribution media 'ftp' or 'nfs' - get to the network-configuration screen - don't find a knob named 'use dhcp' - yell after the net-admin "Hey, ... I need a static IP, which one should I use?" [ - The ever-friendly net-admin is not available - wait several days ... ;) ] - install / configure the machine for the static ip - cd /usr/ports/net/dhcp*; make && make install; - change the machine's configuration (/etc/rc.conf etc.) to make use of the dhcp-client - tell the net-admin that the static ip could now be 'recycled' [with dhcp-client on boot-disk] - boot the bootdisk ;) - choose distribution media 'ftp' or 'nfs' - get to the network-configuration screen - select 'use dhcp' - install - be happy Including a dhcp-client for the boot-disk is something very, very different from including various 'convenience' software in the base system. Regards, Andreas -- : TSE TeleService GmbH : Gsf: Arne Reuter: : : Hovestrasse 14: Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP: :: : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
ibcs2_ipc.c compile failure
Hi, I beleive version 1.14 of ibcs2_ipc.c is bad. I've been receiving the following error(s) when trying to comile it: Thanks! John cc -nostdinc -O -pipe -DCOMPAT_IBCS2 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/ibcs2 -I/usr/obj/usr/src/sys/modules/ibcs2/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: warning: `struct ibcs2_ipc_perm' declared inside parameter list /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: warning: its scope is only this definition or declaration, /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: warning: which is probably not what you want. /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:59: warning: `struct ibcs2_ipc_perm' declared inside parameter list /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_msqid2imsqid': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:71: warning: passing arg 2 of `cvt_perm2iperm' from incompatible pointer type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_imsqid2msqid': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:90: warning: passing arg 1 of `cvt_iperm2perm' from incompatible pointer type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function `cvt_iperm2perm': /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:185: argument `ipp' doesn't match prototype /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:59: prototype declaration /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:186: dereferencing pointer to incomplete type /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:187: dereferencing pointer to incomplete type 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 Holling 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. This would be really nifty for a lot of people. I've installed Windows NT about a zillion times due to its instability and tendencies to eat itself, but I always liked being able to say at the installation phase that I needed to use DHCP to get my IP address. } I built a static version of the WIDE client and server, both were only } around 140K. What's the problem? It's not like putting emacs in the base } install or anything. I still run FreeBSD on a 386/40 with a 40M MFM main } drive, and even so I'm not worried about the "bloat" of adding DHCP. Lots } of people have been asking about DHCP on the lists and the newsgroups, } probably because DSL/cablemodems are becoming more readily available (at } least in the US). People repeatedly ask me if FreeBSD comes with a DHCP client when I suggest it as an alternative to Linux. I always tell them "You can build the port or install a precompiled package," and as easy as that is for people who are familiar with FreeBSD's wonderful ports and package systems, it still causes some people to shy away. } Windows comes with DHCP. Heck, even my old Mac IIci running System 7.5.5 } comes with DHCP. It's small and increasingly useful, why not make it part } of the base distribution? Or would you rather have FreeBSD be like } RedHat, where you have to install an RPM for just about everything? When someone can simply click a radio button or mark a check box in their network configuration in these operating systems, they seem to assume that having to do anything more than that will be too hard. I think that having this small client (which I have installed as a port) in the base operating system will get people to warm up to the idea of trying out FreeBSD. It's one less thing that inexperiencied people have to worry about. These new people may find it semi-frightening to have to remember all those numbers and have to type them in, possibly more than once if something goes wrong. -Patrick Patrick L. Hartling | Research Assistant, ICEMT myst...@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ 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 Holling 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. > > Here are the regular (dynamically linked) versions of the ISC client and > server: > > phluffy% ls -l =dhclient =dhcpd > -rwxr-xr-x 1 root wheel 86016 Nov 20 20:47 /usr/local/sbin/dhclient > -rwxr-xr-x 1 root wheel 90112 Nov 20 20:47 /usr/local/sbin/dhcpd It will probably go into /sbin, /bin, or /stand. These are statically linked exacutables. > I built a static version of the WIDE client and server, both were only > around 140K. What's the problem? It's not like putting emacs in the base > install or anything. I still run FreeBSD on a 386/40 with a 40M MFM main > drive, and even so I'm not worried about the "bloat" of adding DHCP. Lots Bloat by any other name is still bloat. > Windows comes with DHCP. Heck, even my old Mac IIci running System 7.5.5 > comes with DHCP. It's small and increasingly useful, why not make it part > of the base distribution? Or would you rather have FreeBSD be like > RedHat, where you have to install an RPM for just about everything? Where do you draw the line on the base system? Security is important so add tcp_wrappers? More and more documentation is released in html, so add apache? Once something is added to the base distribution, it seldomly gets removed? -- Steve To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: emacs directories in BSD.local.dist
* Just curious as to why share/emacs and share/emacs/site-lisp are created by * BSD.local.dist instead of by the emacs ports which might want to use them? * It's not a big deal, but it seems to me that these aren't useful for the * general case of someone not wanting to install an emacs port (strange as that * may sound [1]). I suspect it's for historical reasons, but it doesnt mean it * can't be removed if sufficient time is deemed to have passed. Actually it's the other way around. It's created by BSD.local.dist so that people who don't need emacs don't have to install them. :) The problem is that many ports, some of which only install .el files as a "by the way, you can use this from emacs too", fall over if this directory is not around. One solution is to add RUN_DEPENDS to emacs, which causes a whole lot of unhappiness, of course. So it's either those ports create the directory themselves or let BSD.local.dist do it. The latter was infinitely easier. :) Satoshi 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 Holling wrote: : :It will probably go into /sbin, /bin, or /stand. These are statically :linked exacutables. : :> I built a static version of the WIDE client and server, both were only :> around 140K. What's the problem? It's not like putting emacs in the base :> install or anything. I still run FreeBSD on a 386/40 with a 40M MFM main :> drive, and even so I'm not worried about the "bloat" of adding DHCP. Lots : :Bloat by any other name is still bloat. : :> Windows comes with DHCP. Heck, even my old Mac IIci running System 7.5.5 :> comes with DHCP. It's small and increasingly useful, why not make it part :> of the base distribution? Or would you rather have FreeBSD be like :> RedHat, where you have to install an RPM for just about everything? : :Where do you draw the line on the base system? Security is :important so add tcp_wrappers? More and more documentation is released :in html, so add apache? : :Once something is added to the base distribution, it seldomly :gets removed? : :-- :Steve I think what goes into the base distribution depends on where we think TheRestOfTheWorld is heading. dhcpd use has exploded in recent years and it is unlikely to go away for a long, long time. dhcpd also supports traditional bootp protocols such as those used by BOOTP kernels. I think it would be an excellent addition to our base system. However, someone needs to do a serious security check on it. I did a quick once-over of the code a few months ago and its security is extremely poor. For example, I had to commit some fairly serious bounds checking to dhcpd's ( I forget which version ) DNS resolution routines. Without a security audit, enabling the thing by default is just asking to get hacked. -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
new freebsd news site
http://www.roms.cx - new freebsd news website, updated daily. 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: > So, we'll import a pop server, apache, g77, ad nauseam > to increase the credibility of FreeBSD as a workstation OS. None of those things are required to get a machine onto the network. DHCP is, in a large and growing number of places. -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
new default options for the Qlogic ISP host adapter...
this causes the generation of opt_isp.h, and so you'll need to reconfig To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: emacs directories in BSD.local.dist
On Mon, 8 Feb 1999, Satoshi Asami wrote: > * Just curious as to why share/emacs and share/emacs/site-lisp are created by > * BSD.local.dist instead of by the emacs ports which might want to use them? > * It's not a big deal, but it seems to me that these aren't useful for the > * general case of someone not wanting to install an emacs port (strange as > that > * may sound [1]). I suspect it's for historical reasons, but it doesnt mean > it > * can't be removed if sufficient time is deemed to have passed. > > Actually it's the other way around. It's created by BSD.local.dist so > that people who don't need emacs don't have to install them. :) > > The problem is that many ports, some of which only install .el files > as a "by the way, you can use this from emacs too", fall over if this > directory is not around. One solution is to add RUN_DEPENDS to emacs, > which causes a whole lot of unhappiness, of course. Ahh, that makes sense. Thanks for the explanation. Kris - (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. 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 mostly interested in choosing the server part. I am NOT importing the server. Only the client and that is because it is required to get booted enought to install FreeBSD and to install packages. -- -- 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/
> 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. -- -- 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/
> So, we'll import a pop server, apache, g77, ad nauseam > to increase the credibility of FreeBSD as a workstation OS. NO. Again, the problem is boot strapping. If you lived in a DHCP world (and not in control of it) you would understand. -- -- 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/
> Or would you rather have FreeBSD be like RedHat, where you have to > install an RPM for just about everything? Actually RedHat's boot floopy has a BOOTP client and thus the Linux weenies on campus don't have the bootstrapping problem the FreeBSD users do. -- -- 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/
: :> Or would you rather have FreeBSD be like RedHat, where you have to :> install an RPM for just about everything? : :Actually RedHat's boot floopy has a BOOTP client and thus the Linux :weenies on campus don't have the bootstrapping problem the FreeBSD users :do. : :-- :-- David(obr...@nuxi.com -or- obr...@freebsd.org) I'm not sure I follow this. FreeBSD's kernel can be compiled up as a BOOTP client too. I use it all the time for my diskless ( well, floppy-only ) workstations. -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/
> :Actually RedHat's boot floopy has a BOOTP client and thus the Linux > :weenies on campus don't have the bootstrapping problem the FreeBSD users > :do. > > I'm not sure I follow this. FreeBSD's kernel can be compiled up as > a BOOTP client too. Sorry, add to that, and their "sysinstall" offers it as an option. Some people on campus have said they have been able to install RH Linux using the BOOTP option on the Linux boot floppy. Others have said it didn't work for them. -- -- 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/
From: "David O'Brien" Subject: Re: adding DHCP client to src/contrib/ Date: Mon, 8 Feb 1999 18:27:57 -0800 > > 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. Make sysinstall be able to pkg_add? We do something similar to that here with PicoBSD by creating the MFS to have slack space and extracting a supplemental archive into it. Cheers, Jerry Hicks wghi...@bellsouth.net > > -- > -- 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 > 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/
> Make sysinstall be able to pkg_add? We do something similar to that 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?? -- -- 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
cleanup of rc.conf ( -4.x )
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.
-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
Re: adding DHCP client to src/contrib/
At 6:02 PM -0800 2/8/99, Steve Kargl wrote: >Mike Holling wrote: >> ... What's the problem? It's not like putting emacs in the base >> install or anything. I still run FreeBSD on a 386/40 with a 40M MFM >> main drive, and even so I'm not worried about the "bloat" of adding >> DHCP. > > Bloat by any other name is still bloat. I think it is a very good idea to have DHCP client support in the base system. Note that I am on a campus which is heading for DHCP for pretty much all student-owned computers, and many campus-owned computers too. >> Windows comes with DHCP. Heck, even my old Mac IIci running >> System 7.5.5 comes with DHCP. It's small and increasingly useful, >> why not make it part of the base distribution? > > Where do you draw the line on the base system? How about "things you need before you can send a single packet over the network"? Particularly for those thinking of doing a network install of an operating system, this might be a good starting point. Every fall we have about 1100 students show up, and many of those students will want to have their computer up and running before they have their alarm clock plugged in. Realistically, the only way for us (the computer center) to deal with this logistical nightmare is thru DHCP. I do not see that changing anytime soon. > Security is important so add tcp_wrappers? More and more > documentation is released in html, so add apache? You don't need either of these to send a packet over our network. You do need DHCP (or you need to wait a week or two before you'll get a fixed IP address so you can use your machine on our network). > Once something is added to the base distribution, it seldomly > gets removed? >From my environment, the chances that DHCP is going to go away anytime soon is zero. Not "close to zero", but absolute zero. Given a situation where: 1) a user wants to do a network install (to get the latest version of everything) and 2) the user will not be able to use the network without DHCP support then what does that user have to do if a DHCP client is not part of the base system? At the same time, I do agree with Matthew Dillion's comment that it would be a very prudent idea if someone could do a code review of whatever DHCP client is chosen, so we have some confidence WRT security issues. --- 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: adding DHCP client to src/contrib/
From: "David O'Brien" > > Make sysinstall be able to pkg_add? We do something similar to that > > 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?? Sorry. It's got to go somewhere offline. If not in the crunched /stand I'd guess it could live on the mfsroot floppy as an archive. I agree that DHCP is very important to have *somewhere* easy to use for both pre- and post- install purposes. We've produced a deviant PicoBSD that uses a different scheme for and uses shared libraries for greater flexibility. Of course, the price you pay is the static memory footprint required. As Jordan has mentioned, what we really need is a new dynamically sizable memory filesystem. I see that Eivind is doing something with getting NULLFS fixed. This is probably a very good step toward a more flexible setup environment. Cheers, Jerry Hicks wghi...@bellsouth.net > > -- > -- 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/
> These should be left has ports. Can't really get away with that anymore - too many people require DHCP for very basic bootstrapping. - 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/
> 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 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 writes : > > Content-Type: text/BLOAT > > These should be left has ports. > I can understand the people who need DHCP to get their systems up. OTOH, where does one draw the line. Is DHCP core functionality? Another issue to be taken into account: there is already a bootp daemon in the tree. Anyone putting any DHCP functionality in should look very seriously at any possibilities of combining the functionality, rather than creating what amounts to a degree of redundancy. (I haven't looked at DHCP-WIDE, and consequently, I don't know if it also supports bootp functionality.) I personally would prefer to see DHCP left a port. But, OTOH, more and more people are using dynamic IP address assignment on their networks. (Not an easy one.) Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 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 <19990209074440.15845.qmail.kithrup.freebsd.curr...@rucus.ru.ac.za> you write: >Is DHCP core functionality? As much as an editor and PPP are, yes -- without it, some people simply *cannot* get on the net. >Anyone putting any DHCP functionality in should look >very seriously at any possibilities of combining the functionality, >rather than creating what amounts to a degree of redundancy. I think isc-dhcp can do both; however, it may only be the server that has that functionality. >I personally would prefer to see DHCP left a port. How would someone on a network and without a CD-ROM install it? (I recently had the joy of doing this, incidently... I ended up unplugging one of the other computers and using is IP address until the installation was complete.) That, I believe, is the reason that it's time to consider putting it in. (I've only used the ISC code, and, for several reasons, am biased in its favour, but I don't think it really matters.) 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: > > Make sysinstall be able to pkg_add? We do something similar to that > > 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 -- Steve 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: > > So, we'll import a pop server, apache, g77, ad nauseam > > to increase the credibility of FreeBSD as a workstation OS. > > NO. Again, the problem is boot strapping. If you lived in a DHCP world > (and not in control of it) you would understand. > I do live in a dhcp world, but our net admins appreciate the fact my machines are up 7/24 and serve my research group, so they have given me a fixed ip. -- Steve 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 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. etc.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum 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: > > 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
Re: adding DHCP client to src/contrib/
Steve Kargl wrote in message ID <199902090600.waa65...@troutmask.apl.washington.edu>: > Drop FreeBSD cd-rom into tray (or caddy). > mount_cd9660 /dev/cd0a /mnt > pkg_add dhcp > umount /mnt So you are suggesting we no longer supporting FTP installs? Do you realise what impact that would have? I guess you haven't seen the dramatic increase in cablemodem and ADSL/SDSL/HDSL/IDSL installations which don't offer static IP's and require running DHCP clients? Let alone all the M$ infested corporate environments? Heck, I even recommend running DHCP to people! Why? It makes roaming between work and home with a laptop 10 times easier! IMHO, requiring a CD to install in a DHCP environment is like requiring a GPS before getting a driving license. Something that a case could be made for, but it'd hold water about as well as a wire mesh fence. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info 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: > > > 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? If the user had the CD, they wouldn't need DHCP to install the OS. Obviously the reason to put DHCP on the boot floppy is so that people can netinstall FreeBSD from an environment where IPs are handed out via DHCP, like a cablemodem/DSL setup. - 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/
Steve Kargl wrote in message ID <199902090603.waa65...@troutmask.apl.washington.edu>: > I do live in a dhcp world, but our net admins appreciate > the fact my machines are up 7/24 and serve my research group, > so they have given me a fixed ip. That argument won't work with Media-One, Roadrunner, RCN, etc who just simply *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' 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. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info 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: > 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? 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. -- 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
Re: adding DHCP client to src/contrib/
Wrong! The dhcp client is ESSENTIAL to boot floppies for modern use. As for "bloat", one man's bloat is another's essential material :-( On Mon, 8 Feb 1999, Steve Kargl wrote: > Joe Abley wrote: > > On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote: > > > I am planning on adding the Wide-DHCP client to src/contrib/ > > Content-Type: text/BLOAT > > These should be left has ports. > 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/
Remember that the client, relay, and server are all independent items. Each MUST meet the same RFC specification. On Tue, 9 Feb 1999, Andreas Braukmann wrote: > On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote: > > I am planning on adding the Wide-DHCP client to src/contrib/ and > I'm mostly interested in choosing the server part. In the past I > deployed only the wide-dhcp server from the ports collection; but > only because I somehow decided to test the wide-dhcp before the isc one. > > A few days ago I had a look (triggered by a piece of samba documentation) > at isc-dhcp and found the configuration syntax somewhat more user friendly. 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 am glad to see some SOME version of the dhcp client included in base floppies. However, I must take exception to David's choice for any purpose other than single floppy situations. 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. Further, the assertion that it is easier to configure the WIDE client is WRONG. The ISC CLIENT requires NO configuration. I don't see how anything can be simpler. :-) Unfortunately, David persists in spreading this mis-information. On, 8 Feb 1999, David O'Brien wrote: > 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. 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 09-Feb-99 Charlie ROOT wrote: > Further, the assertion that it is easier to configure the WIDE client is > WRONG. The ISC CLIENT requires NO configuration. I don't see how anything > can be simpler. :-) Hmmm.. This annoyed me actually.. There is NO config file which means its damn annoying for you to tweak how it works.. Almost like a windows app really :) The WIDE client's default config file is usually quite OK. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum 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/
Gary Palmer wrote: > Steve Kargl wrote in message ID > <199902090600.waa65...@troutmask.apl.washington.edu>: > > Drop FreeBSD cd-rom into tray (or caddy). > > mount_cd9660 /dev/cd0a /mnt > > pkg_add dhcp > > umount /mnt > [watch the long lines] > So you are suggesting we no longer supporting FTP installs? Do you > realise what impact that would have? I guess you haven't seen the > dramatic increase in cablemodem and ADSL/SDSL/HDSL/IDSL installations > which don't offer static IP's and require running DHCP clients? > Let alone all the M$ infested corporate environments? Heck, I even > recommend running DHCP to people! Why? It makes > roaming between work and home with a laptop 10 times easier! No. Yes. Yes. Yes. Why? Paraphasing David's original email: david> I have DHCP-WIDE bmake'd. I going to commit if no one objects. It would have been helpful if he would have given some justification. Without critical discussion of each candidate for inclusion in the base distribution, the system will grow without bounds. Trying to remove something from the base is somewhat difficult. Search mailing list for a recent discussion about removing f2c. I have a f2c port and more robust f77(1) sitting here waiting. Inertia. -- Steve 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 : > In article > <19990209074440.15845.qmail.kithrup.freebsd.curr...@rucus.ru.ac.za> you write: > >Is DHCP core functionality? > > As much as an editor and PPP are, yes -- without it, some people simply > *cannot* get on the net. Your point is valid. Before it goes in, there are some points to look at though: - Integration with bootp functionality (if possible) - 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. Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 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/
John Birrell wrote: > Steve Kargl wrote: > > 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? > > 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. > David's original email said he was going to commit without giving a justification. I call it bloat, then the justifications pour in. I'm now convinced it may be a good thing with a security audit. However, if every committer starting to push his (pet) software as candidate for the base distribution, then the base will grow without bounds. How long did it take to kill tcl from the base distribution, and how long will it take to kill f2c? -- Steve 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/
Gary Palmer wrote: > Steve Kargl wrote in message ID > <199902090603.waa65...@troutmask.apl.washington.edu>: > > I do live in a dhcp world, but our net admins appreciate > > the fact my machines are up 7/24 and serve my research group, > > so they have given me a fixed ip. > > That argument won't work with Media-One, Roadrunner, RCN, etc who just simply > *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' > 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. -- Steve 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: > David's original email said he was going to commit without giving > a justification. I call it bloat, then the justifications pour in. > I'm now convinced it may be a good thing with a security audit. > > However, if every committer starting to push his (pet) software > as candidate for the base distribution, then the base will > grow without bounds. How long did it take to kill tcl from > the base distribution, and how long will it take to kill f2c? IMHO, "Just Do It". Ask David. 8-) -- 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
Re: adding DHCP client to src/contrib/
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. -- Steve 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: >Hmmm.. This annoyed me actually.. >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. In some other cases, it needs to be configured. Due to a bug in the version of isc-dhcpd at work, for example, I needed to have a /etc/dhclient.conf file that looked like: send dhcp-client-identifier "sef-laptop"; There are a bunch of things I could specify. Interestingly enough, they're documented in dhclient.conf(5), which comes with the isc-dhcp package. So: not only does isc-dhcp have extensive configuration options, but, in the common case, it's not needed at all. 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 09-Feb-99 Steve Kargl wrote: > > Or I'd like to play with FreeBSD, but I'd rather not fork out US$30 for > > something I > > haven't tested. > Cheapbytes. Argument still holds.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum 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 <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
Re: adding DHCP client to src/contrib/
On 09-Feb-99 Sean Eric Fagan wrote: > >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? Argh! Damn I got WIDE and ISC confused.. AGAIN.. My aplogies.. OK, lets do ISC instead of WIDE :) The WIDE client is the one I tried first a while ago and got very annoyed cause there was no config file.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum 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 in message ID <199902090634.waa65...@troutmask.apl.washington.edu>: > Then, *BUY* the cd-rom and support the FreeBSD project. All that would happen would be that ppl will see `oh, no DHCP support on install. Better go with that linux dist which supports it' and we lose support. *shrug* Keeping people happy is the name of the game. I think you fail to understand that concept. If people need DHCP to install, then that becomes a requirement. Its not a cost issue. Its a `oh, I want to do this tonite, I have time. What? I need to wait for a CD to be shipped?!?!? that, I'll go install something which *SUPPORTS* *MY* *NEEDS*' Please, unless you have something constructive to contribute to this discussion, I suggest you drop it before you look like you are irritated because fortran is still in the base tree and you now have a bee in your bonnet. Instead of being an obstruction to progress, I suggest you find ways to contribute to the furthering of your goals. e.g. working with the people developing the new integrated packaging system which would make the distinction between `distribution' and `package' blurred. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info 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/
> > That argument won't work with Media-One, Roadrunner, RCN, etc who > > just simply *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' 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. That's not the point. Of course, everyone is encouraged to buy CDs and support the project. However, if netinstalls weren't desired, then they wouldn't be available in the first place. Since they are, they should be made to work for as many cases as possible. It seems silly to allow for esoteric netinstall methods like PLIP, but leave out something as common as environments requiring DHCP. And yes, I've used PLIP to install before, on a notebook that didn't have an ethernet card at the time. - 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/
On Tue, 9 Feb 1999, Daniel O'Connor wrote: > > On 09-Feb-99 Charlie ROOT wrote: > > Further, the assertion that it is easier to configure the WIDE client is > > WRONG. The ISC CLIENT requires NO configuration. I don't see how anything > > can be simpler. :-) > Hmmm.. This annoyed me actually.. > There is NO config file which means its damn annoying for you to tweak how it > works.. > Almost like a windows app really :) This also is incorrect. You MAY have a configuration file to override the defaults. In most cases, the defaults are just fine and the configuration file may be omitted. However, all the knobs are there for those who need them. > The WIDE client's default config file is usually quite OK. As I said, the ISC clients (non-existant) file is equally acceptable. 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'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. Bootpd doesn't require bpf in order to work. Incoming requests all have the IP number 0.0.0.0. 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. I would still be very reticent to see BPF in a generic kernel because of the security implications. Remember that the DHCP client is listening for a datagram which has its own layer 2 address as the destination address. - No need for promiscuous mode. The only problem is that the client doesn't know its own IP number. I would really not like DHCP to require FreeBSD being shipped with bpf enabled. Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 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 09-Feb-99 Charlie ROOT wrote: > > Further, the assertion that it is easier to configure the WIDE client is > > WRONG. The ISC CLIENT requires NO configuration. I don't see how anything > > can be simpler. :-) > Hmmm.. This annoyed me actually.. > There is NO config file which means its damn annoying for you to tweak how it > works.. > Almost like a windows app really :) > > The WIDE client's default config file is usually quite OK. Actually, the ISC client supports a configuration file, but its defaults are usually fine. There are any number of reasons for going with the ISC client, including an involved ISC developer that's keen to help it happen. -- \\ 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/
> - 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. That's not "VERY BAD". Bpf imposes a slight performance, hit, but that's about all. Don't start whining about the "security issues"; they're so trivial to be beyond worry. -- \\ 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/
> 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. Buying the Cheapbytes disc doesn't support the project, and there's a pretty good chance that the DHCP client won't be on the first disk. Steve; face it, DHCP client functionality is needed by other people. It won't kill you. Live with it. -- \\ 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/
In article <19990209091330.18608.qmail.kithrup.freebsd.curr...@rucus.ru.ac.za> you write: >I would still >be very reticent to see BPF in a generic kernel because of the security >implications. I'm sorry, but that's a complete non-issue: 1. /dev/bpf0 is mode 400, root.wheel -- to read it, you need to break root. 2. If you can break root, you can rebuild a kernel with BPF *anyway*. 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/
According to Steve Kargl: > So, we'll import a pop server, apache, g77, ad nauseam > to increase the credibility of FreeBSD as a workstation OS. No but if you want to install from a cable modem (they're becoming quite common these days, even in France), you _need_ it. Period. I'm as much anti-bloat as the next guy but I'll welcome this addition. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in /usr/src/sys/i386/ibcs2/ibcs2_ipc.c
I also have this problem Randy Bush wrote: > 4.0 -current > > touch?? opt_spx_hack.h > cc -O -pipe -DCOMPAT_IBCS2? -DKERNEL -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes? -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual? -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-? > -I/usr/obj/usr/src/sys/modules/ibcs2 -I/usr/obj/usr/src/sys/modules/ibcs2/@ > -I/usr/obj/usr/src/tmp/usr/include -c > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_errno.c > cc -O -pipe -DCOMPAT_IBCS2? -DKERNEL -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes? -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual? -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-? > -I/usr/obj/usr/src/sys/modules/ibcs2 -I/usr/obj/usr/src/sys/modules/ibcs2/@ > -I/usr/obj/usr/src/tmp/usr/include -c > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: warning: `struct > ibcs2_ipc_perm' declared inside parameter list > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: warning: its > scope is only this definition or declaration, > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: warning: which is > probably not what you want. > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:59: warning: `struct > ibcs2_ipc_perm' declared inside parameter list > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function > `cvt_msqid2imsqid': > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:71: warning: passing > arg 2 of `cvt_perm2iperm' from incompatible pointer type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function > `cvt_imsqid2msqid': > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:90: warning: passing > arg 1 of `cvt_iperm2perm' from incompatible pointer type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function > `cvt_iperm2perm': > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:185: argument `ipp' > doesn't match prototype > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:59: prototype > declaration > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:186: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:187: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:188: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:189: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:190: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:191: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:192: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function > `cvt_perm2iperm': > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:199: argument `ipp' > doesn't match prototype > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:58: prototype > declaration > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:200: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:201: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:202: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:203: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:204: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:205: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:206: dereferencing > pointer to incomplete type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function > `cvt_semid2isemid': > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:214: warning: passing > arg 2 of `cvt_perm2iperm' from incompatible pointer type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function > `cvt_isemid2semid': > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:227: warning: passing > arg 1 of `cvt_iperm2perm' from incompatible pointer type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function > `cvt_shmid2ishmid': > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:318: warning: passing > arg 2 of `cvt_perm2iperm' from incompatible pointer type > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c: In function > `cvt_ishmid2shmid': > /usr/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:335: warning: passing > arg 1 of `cvt_iperm2perm' from incompatible pointer type > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > ***
