Re: Error in libstdc++ buildworld
On Sun, Nov 19, 2000 at 12:45:11PM -0600, Mark R Grant wrote: > 1. I cleaned up the source directories using "cd /usr ; make cleandir" > 2. I cleaned up the object directories using "cd /usr/obj ; chflags -R > noschg * ; rm -rf *" These two steps should be reversed. The `make cleandir' in #1 will clean out the /usr/obj/<...dir> shadow tree if it exists, else the dir w/in /usr/src/ ``make cleandir && make cleandir'' is the way to ensure that /usr/src is truely clean (or do your step #2 above first). > 4. I decided that since I am too much of a novice at this, I should use the > buildworld and installworld seperately. I ran "cd /usr/src ; make -j2 > buildworld" With -jX (X > 1), you cannot trust any error output. You would be better off not using -j until you know you can build the world. From the output you provide I'm not sure why the /usr/obj/usr/src/i386/mk directory doesn't exist. But please try your step #2, followed by our step #1 and see if this goes away. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Error in libstdc++ buildworld
On Sun, Nov 19, 2000 at 10:44:09AM -0600, Mark R Grant wrote: > David O'Brien wrote: Respect my "Reply-To: [EMAIL PROTECTED]" or I won't respond to queries for help in the future. > Following my interpretation of the instructions in the make.conf file, the > CFLAGS line is commented out. > I am running version 4.1.1-RELEASE, trying to upgrade to -CURRENT using the > 'RELENG_4' tag. Last cvsup was Nov 18, 2300 GMT One cannot "upgrade"[*] to -CURRENT using he "RELENG_4" tag. The "RELENG_4" is the 4.x code base. To get -CURRENT source one would use no tag. RELENG_4 is very buildable right now, so something is weird on your end. You'll [again] need to give more _details_. Example: 1. I checked out the source using ``cd /usr ; cvs co src'' 2. I then made sure the /usr/obj/ directory existed. 3. I then did ``cd /usr/src ; make world''. [*] "upgrading" to -CURRENT really doesn't mean anything as it isn't a release and for your use it may easily be a "downgrade". You should examine your reasons for wanting to run -CURRENT. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Error in libstdc++ buildworld
On Sun, Nov 19, 2000 at 09:54:58AM -0600, Mark R Grant wrote: > FreeBSD user since 2.x, but never attempted to make/build/install world. > While doing 'make -j2 buildworld': It would help us immensely if you would give some details of the environment in which you are having this problem. What CLFAGS are you using? What version of FreeBSD are you running? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RQ review: [was: Re: "make modules" kicks the first module d
On Fri, Nov 17, 2000 at 02:06:44PM -0800, John Baldwin wrote: > > I committed something simular. BTW, you made ``make depend'' a > > requirement, which we did not have agreement on. > > Erm: > > config -g LAPTOP > Don't forget to do a ``make depend'' > Kernel build directory is ../../compile/LAPTOP > > make depend is already a requirement. "Erm", that is a recommendation. It is not a requirement. The posted patch made it so you were forced to. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RQ review: [was: Re: "make modules" kicks the first module directory twice]
On Fri, Nov 17, 2000 at 10:55:32PM +0900, Makoto MATSUSHITA wrote: > Attached below is a patch which I've made before. If nothing is going > wrong, please commit this change I committed something simular. BTW, you made ``make depend'' a requirement, which we did not have agreement on. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to build world
On Wed, Nov 15, 2000 at 09:20:06PM +, Joel Lindau wrote: > When i try to build my -current world cvsupped today ( 15 nov ) i get the > following errors: When was the last time up built world? I'd like to know if this has anything to do with the Binutils upgrade, or if is something you would have experienced if you had tried to build world yesterday To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: binutils commit breaks kernel builds?
On Wed, Nov 15, 2000 at 04:15:55PM +0100, Harti Brandt wrote: > with fresh sources from today 6:00 MET kernel builds fail. The victim is I'm done with the upgrade - you may have easily CVSuped during the upgrade process. Can you wait an hour or so, CVSup again and see if you still see the problem? Is anyone else experience[31~ing this? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make modules" kicks the first module directory twice
[stable dropped, this should have only been in a single list to start with!!] On Tue, Nov 14, 2000 at 01:27:32PM -0700, Warner Losh wrote: > : I'd rather take a major compile time hit and be deterministic than not. > > I'd rather not. We don't do an implicit make obj in the rest of the > tree. It is in `make world' if /usr/obj exists. Otherwise how does all the .o's get in /usr/obj/ ? > If I go build the world, and then someone adds a new program to > the tree, you are in the same boat. Nope, `make world' will DTRT. > If you cd to that program and type make it will wind up in . rather > than /usr/obj. Yes, and how many times do we have to tell people to run ``make cleandir && make cleandir'' or ``rm -rf /usr/obj/* ; cd /usr/src ; make cleandir '' > Completely deterministic, the same thing will happen every time you do > the scenario. Ok, completely deterministic given enough detail -- detail which 99% of the time will not be provided in email to the lists saying this and that is broken. > But before making major changes to this, let's see Peter Wemm's new > all singing all dancing config work does for us. I'd rather see what > he's come up with than argue further on this. Earlier today, I too I was wondering if his plan makes all this OBE. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RQ review: [was: Re: "make modules" kicks the first module directory twice]
On Mon, Nov 13, 2000 at 08:02:47PM -0800, Marcel Moolenaar wrote:
> Any objections?
Yes.
> (patches follow for your convenience)
[its easier to read patches when they aren't quoted in their entirety ;-)]
> > modules-depend:
> > @mkdir -p ${.OBJDIR}/modules
> > ! cd $S/modules; env ${MKMODULESENV} ${MAKE} obj
> > ! env ${MKMODULESENV} ${MAKE} depend
This is broken for non -j case.
--
-- David ([EMAIL PROTECTED])
GNU is Not Unix / Linux Is Not UniX
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: "make modules" kicks the first module directory twice
On Mon, Nov 13, 2000 at 09:17:54PM -0700, Warner Losh wrote: > The implications are that make obj isn't done unless you've run make > depend first. If a new directory is added and a make depend isn't > run, then the modules won't get built into the obj tree, but instead > will be built into $S/modules. Having modules wind up in two trees is not acceptable IMHO. I'd rather take a major compile time hit and be deterministic than not. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make modules" kicks the first module directory twice
On Mon, Nov 13, 2000 at 12:23:08PM -0700, Warner Losh wrote: > : > I think that make has no business doing an implicit make obj for the > : > all target. > : Someone has to run `make obj' for the modules tree. How are you doing it > : locally? > > Right now we do it twice. Once in make dpeend and again in make > all. My patch removes it from make all. ..snip.. > I'm not sure what you're criteria for a robust world is here. If the > directory doesn't exist, it will warn the user. It doesn't warn the user, it errors out (possibly a suttle distinction I'm making). Also in the past a `make depend' for the kernel was not required. Just highly suggested. Are we really prepared to make it a requirement now? To tell the truth, IMHO the modules should just build in the current directory (and thus could share some .o's with the kernel build). -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make modules" kicks the first module directory twice
On Mon, Nov 13, 2000 at 01:19:38PM -0500, Marcel Moolenaar wrote: > I'll commit a fix with just semi-colons today for all architectures if > someone hasn't done that already by that time. Can you post a patch first. There seems to be some subtleties here that might make a review useful. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make modules" kicks the first module directory twice
On Mon, Nov 13, 2000 at 07:51:11PM +0900, Makoto MATSUSHITA wrote:
> ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj all
> --- 310,322
> ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj
> ! cd $S/modules && env ${MKMODULESENV} ${MAKE} all
I can certainly commit this type of fix. The combined make invocation
was an optimization someone recommended.
--
-- David ([EMAIL PROTECTED])
GNU is Not Unix / Linux Is Not UniX
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: "make modules" kicks the first module directory twice
On Sun, Nov 12, 2000 at 11:58:39PM -0700, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Makoto MATSUSHITA writes: > : It does not fix this problem. However, if we separate the execution of > : "make obj" and "make all", we can avoid (again, not *fix*) the problem. > : Maybe this change is reasonable; there is few meaning doing "make > : kernel-depend" in "doMODULES" target. > > I think that make has no business doing an implicit make obj for the > all target. Someone has to run `make obj' for the modules tree. How are you doing it locally? > I have been running with patches in my tree that doesn't do the obj > target if .depend exists. can you post them for review. > Of course, you have to be more careful about running make depend in > that case Now *that* sounds scarry to me. We'll have people all over the lists who forget to and would now get rather bitten. From the sounds of it, your patch doesn't create as robust a world, but maybe it does. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: I broke world with the ligcc_pic for shared object commit
On Fri, Nov 10, 2000 at 12:02:52PM -0800, David O'Brien wrote: > I break world. The world is believed to be fixed now. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
I broke world with the ligcc_pic for shared object commit
Oh just shoot me. I drop my "don't commit a single bit to the compiler" w/o a full `make buildworld' for a single commit and look what happens -- I break world. *sigh* -- the compiler did build along with everything in /src/gnu/lib with it... but that wasn't good enough testing. A fix is in the works. -- David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: We cannot use 'make -j' option to build the world, period.
On Sat, Nov 04, 2000 at 05:19:44PM +0900, Makoto MATSUSHITA wrote: > > matusita> I've found that current src/sys/modules/linux for RELENG_4 > matusita> is not 'make -j' safe. It maybe causes a problem if you want > matusita> to make a module. > > Long time has past and, but problem is still there. > > OK, we all FreeBSD users should forget the fact that there is an > option '-j' in make(1) and it's helpful for building FreeBSD. I dunno AFAIK, we've never really supported -j for kernel building (which the linux module is part of). -j makes for world should certainly still work. Or you could help debug the problem and submit at Makefile patch. :-) -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make DESTDIR=foo failing in installkernel ?
On Thu, Nov 02, 2000 at 10:20:36AM +0100, Adrian Chadd wrote: > On Mon, Oct 30, 2000, David O'Brien wrote: > > On Mon, Oct 30, 2000 at 09:15:00AM +0100, Adrian Chadd wrote: > > > cd /crash/usr/src/sys/modules && env > > > MAKEOBJDIRPREFIX=/usr/obj/crash/usr/src/sys/GENERIC/modules > > > KMODDIR=/crash/boot/kernel make install > > > > Don't explicitly add DESTDIR to KMODDIR. > > Thats all fine and good, but I don't want to touch the makefile magic. I mean when you set KMODDIR, only use "/boot/kernel", as the bsd.*.mk Makefiles will add DESTDIR for you. > Can someone else proficient in Makefile h0h0magick do it if it hasn't > been done already? :) Not sure what Makefile hackery is needed as I'm not sure what you're wanting to do. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ABI is broken??
On Wed, Nov 01, 2000 at 03:19:36PM -0500, Garrett Wollman wrote: > If you want to bump libc_r's version, we should do it to libc as well, > and in that case there are a large number of ABI fixes that I have > queued up which should be done at the same time. Any reason to not get them in -current now and make the bump? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: compile failure in current
On Tue, Oct 31, 2000 at 07:49:08AM -0800, Charlie Root wrote: > cc -Os -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I. -DIN_GCC >-finhibit-size-directive -fno-inline-functions -fno-exceptions >-fno-omit-frame-pointer -I/usr/obj/usr/src/i386/usr/include -g0 -DCRT_END -c -o >crtend.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c >/usr/src/gnu/lib/csu/crtend.c > cc: cannot specify -o with -c or -S and multiple compilations > *** Error code 1 What is the contents of your /usr/src/gnu/lib/csu ? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: `make cleandir' doesn't seem to be cleaning as well as before
On Mon, Oct 30, 2000 at 06:13:28PM -0800, David O'Brien wrote: > > Are others seing a situation where > > ``cd /usr/src/foo && make obj && make cleandir && make cleandir'' isn't > > deleting /usr/obj/usr/src/foo/ ? It used to and it needs to in order > > that the second ``make cleandir'' will clean /usr/src/foo/ itself. > > I tracked this down to rev 1.33 of bsd.obj.mk. I'm wrong, it is the rev 1.3[12]. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: `make cleandir' doesn't seem to be cleaning as well as before
> Are others seing a situation where > ``cd /usr/src/foo && make obj && make cleandir && make cleandir'' isn't > deleting /usr/obj/usr/src/foo/ ? It used to and it needs to in order > that the second ``make cleandir'' will clean /usr/src/foo/ itself. I tracked this down to rev 1.33 of bsd.obj.mk. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
`make cleandir' doesn't seem to be cleaning as well as before
Are others seing a situation where ``cd /usr/src/foo && make obj && make cleandir && make cleandir'' isn't deleting /usr/obj/usr/src/foo/ ? It used to and it needs to in order that the second ``make cleandir'' will clean /usr/src/foo/ itself. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make DESTDIR=foo failing in installkernel ?
On Mon, Oct 30, 2000 at 09:15:00AM +0100, Adrian Chadd wrote: > cd /crash/usr/src/sys/modules && env > MAKEOBJDIRPREFIX=/usr/obj/crash/usr/src/sys/GENERIC/modules > KMODDIR=/crash/boot/kernel make install Don't explicitly add DESTDIR to KMODDIR. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /stand/sysinstall fdisk won't work
On Sun, Oct 29, 2000 at 12:20:31PM -0700, [EMAIL PROTECTED] wrote: > After installing the latest version of the current source, > /stand/sysinstall's fdisk will not find any devices. Can anybody tell me > what I forgot to do? I did do the /dev/MAKEDEV all. cd /usr/src/release/sysinstall make obj && make all install In otherwords rebuild and install a new sysinstall. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** changes to /usr/lib/crt*.o
On Sun, Oct 29, 2000 at 02:50:26PM +0600, Alexey Dokuchaev wrote:
> What caused such a change? I mean, what the purpose of it, what set of
> problems should it (probably?) solve?
>From the commit message (which you should be following if you're running
-current :-) )
Log:
* Bring back the guts of crt{i,n}.S. This allows C++ exceptions to work
when using the egcs and gcc-devel ports, along with GCC built from stock
public FSF sources. With out this change, FreeBSD will be removed from
the list of systems GCC 3.0 must be evaluated on before release. With
the effort some of us put into getting FreeBSD on this list, we should
not turn this effort into a waste, else we might not be worth fighting
for in the future. (note that Alpha and IA-64 versions of crt{i,n}.S
are needed)
* Switch from our own crt{begin,in} to those created from GCC's crtstuff.c.
This will allow us to switch to DWARF2 exceptions in the future, along with
staying in sync with any future GCC requirements.
* Break out our ELF branding bits into a seperate file. Currently this
is now included by our crt1.c files (since this functionality was part of
our native crtbegin.c). Later crtbrand.o will be merged in the creation
of crti.o.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make release failure - ipfilter(osreldate.h)
On Sat, Oct 28, 2000 at 01:54:52PM -0700, John W. De Boskey wrote: > /usr/src/sys/modules/ipfilter/../../netinet/mlfk_ipl.c:44: > @/netinet/ip_compat.h:268: osreldate.h: No such file or directory > *** Error code 1 This was fixed (two different ways) 2 days ago. What rev of /sys/modules/Makefile and ip_compat.h do you have? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
** HEADS UP ** changes to /usr/lib/crt*.o
I am switching us from using or native crt{begin,end}.c to GCC's
crtstuff.c in the building of /usr/lib/crt{begin,end}.o.
Testing a new world with this change not show any problems.
HOWEVER, I have only done cursory testing with already installed ports
(shared binaries and libs) and our current set of Packages. (especially
since ``pkg_add -r'' is broken and no one will take responsibility for
it)
If you find any problems, I'd like to know ASAP as I hope to MFC this for
4.2-RELEASE.
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: AMD broken in -current?
On Fri, Oct 27, 2000 at 09:34:07AM -0700, Jordan Hubbard wrote: > > On Thu, Oct 26, 2000 at 09:04:45PM -0700, Jordan Hubbard wrote: > > > It use to work in early October, but now I get the following using > > > the stock (/etc/defaults/rc.conf) amd flags: > > > > It works on my Oct 22nd world. > > OK, so maybe it broke even later. What does it do on your > Oct 27th world? :) On a 4.5hr old world (I need more sleep), it also works fine. -- David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel build problem
On Fri, Oct 27, 2000 at 10:46:24PM +1100, Darren Reed wrote: > I'm generally compiling/developing on -STABLE (in this case, the > imported code was compiling cleanly on 4.1-RELEASE) and generally don't > think that it'll be _that_ different. In all seriousness, the farther down the 4.x branch we get, the divergence between -STABLE and -CURRENT gets *quite* different. This is unfortunate, but until we do major paid release engineering, many things are MFC'ed that really could/should be to reduce the differences. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel build problem
On Fri, Oct 27, 2000 at 11:43:04AM +0200, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Darren Reed writes > : > >What failed ? Do you have the make error output ? > Did you try to compile LINT before you committed ? Hell, forget LINT, just try GENERIC. Darren, you really, really have a major problem importing new ipfilter bits. I cannot think of a single time you have not broken world. What can we do to help you prevent this in the future? Do you compile a GENERIC and/or LINT kernel before your change(s)? Do you ``cvsup'' and then test what actually got committed in a virgin src tree? -- -- David ([EMAIL PROTECTED]) P.S. ===> ipfilter rm -f .depend mkdep -f .depend -a -nostdinc -DIPFILTER=1 -DIPFILTER_LKM -DIPFILTER_LOG -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include /usr/src/sys/modules/ipfilter/../../netinet/mlfk_ipl.c /usr/src/sys/modules/ipfilter/../../netinet/ip_nat.c /usr/src/sys/modules/ipfilter/../../netinet/ip_frag.c /usr/src/sys/modules/ipfilter/../../netinet/ip_state.c /usr/src/sys/modules/ipfilter/../../netinet/ip_proxy.c /usr/src/sys/modules/ipfilter/../../netinet/ip_auth.c /usr/src/sys/modules/ipfilter/../../netinet/ip_log.c /usr/src/sys/modules/ipfilter/../../netinet/ip_fil.c /usr/src/sys/modules/ipfilter/../../netinet/fil.c In file included from /usr/src/sys/modules/ipfilter/../../netinet/mlfk_ipl.c:44: @/netinet/ip_compat.h:268: osreldate.h: No such file or directory ..snip.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pkg_add -r broken
Are others seeing that ``pkg_add -r foo'' is broken? Core was generated by `pkg_add'. Program terminated with signal 11, Segmentation fault. (gdb) where #0 0x280e2866 in strchr () from /usr/lib/libc.so.4 #1 0x28074d74 in fetchRestartCalls () from /usr/lib/libfetch.so.2 #2 0x280720d6 in fetchXGet () from /usr/lib/libfetch.so.2 #3 0x2807236c in fetchXGetURL () from /usr/lib/libfetch.so.2 #4 0x280723ab in fetchGetURL () from /usr/lib/libfetch.so.2 #5 0x804d050 in free () #6 0x8049a45 in free () #7 0x8049913 in free () #8 0x80497fe in free () #9 0x80493e1 in free () To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AMD broken in -current?
On Thu, Oct 26, 2000 at 09:04:45PM -0700, Jordan Hubbard wrote: > It use to work in early October, but now I get the following using > the stock (/etc/defaults/rc.conf) amd flags: It works on my Oct 22nd world. -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfw question.
On Thu, Oct 26, 2000 at 08:47:35PM -0700, Jordan Hubbard wrote: > > G. Hot button. :) Quite sorry, didn't mean to push any buttons. But once again I just got hit by having a anchient /stand/sysinstall not be able to find any devices when I wanted to use it's Fdisk editor. Way back when I wanted to hook both sysinstall and the instalation of its manpage into `make world', you said not to bother because it was going to be OBE'ed soon. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfw question.
On Thu, Oct 26, 2000 at 03:18:55PM -0700, John Baldwin wrote: > Ugh, no. Peter's forthcoming config(8) changes will allow you to > specify kernel options to use when building modules (actually, it > builds modules in the same environment as the kernel) to properly > handle this. Just be patient until we have the right solution > finished and in the tree. I disagree. Vaporware (example Son of Sysinstall) has kept us from improving things until the fabled newstuff arrives. Unless you have a strong commitment from Peter on a time frame, we need to offer an easy way to control the functionality of the ipfw module. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
On Thu, Oct 26, 2000 at 02:25:58PM -0700, Matt Dillon wrote: > /etc/rc already assumes that /var is writable. I recommend that you make > that assumption by default... have the default entropy file be something > like "/var/db/entropy_seed" and allow the administrator to override it > with an RC variable. You could allow the administrator to select a > different entropy file and you could have another RC variable which allows > the administrator to set a command which, when executed, returns an > arbitrary sequence of bytes on its stdout to initialize entropy with. This is sweet! Seems it would give us the full benefits of Mark's randomdev, and fit nicely with our normal configuration framework and gives good flexibility. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfw question.
On Thu, Oct 26, 2000 at 04:31:57PM -0400, Bill Fumerola wrote:
> #If you want it verbose
> #CFLAGS+= -DIPFIREWALL_VERBOSE
> #CFLAGS+= -DIPFIREWALL_VERBOSE_LIMIT=100
> #
> #If you want it to pass all packets by default
> #CFLAGS+= -DIPFIREWALL_DEFAULT_TO_ACCEPT
So one doesn't have to change the source, would you be willing to add
WANT_foo logic so one could just set it in /etc/make.conf? Or add
${IPFIREWALL_OPTS} to CFLAGS and then IPFIREWALL_OPTS could be set in
/etc/make.conf?
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
On Thu, Oct 26, 2000 at 09:25:05AM -0400, John W. De Boskey wrote: > If this was happening in -stable I'd be in total agreement. > However, we're talking -current, and is not -current the > integration area for new technologies, whether they be > rough or round edged? Yes, -CURRENT is for new technologies and integration, even with rough edges. However, such integration should not cause major pain for more than 3-4 days. Anything more than 3 days or so, can really impact other's work. devrandom has taken a little longer than this. Over the past 3 weeks (or so), I've I've lost a day to this, and others piped up saying they've lost a lot of time too. This does not make me happy when writing my status reports to my boss, or others who really hoped to spend their Sunday afternoon developing their favorite new feature and instead couldn't. -- -- David ([EMAIL PROTECTED]) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
On Wed, Oct 25, 2000 at 09:28:31PM -0700, Doug Barton wrote: > > How exactly are you rebooting? If you're using the 'reboot' command, That is my standard rebooting method. ``reboot'' really has to be tolerated and something useful happen (ie, the next booting up doesn't hang (or delay for a long time) waiting for entropy, etc) -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Wed, Oct 25, 2000 at 04:04:13PM -0400, Garrett Wollman wrote: > Hmmm. We already have a program (called `tsort') which does this > (i.e., a topological sort). Does `rcorder' call `tsort' or does it > reinvent the wheel? UTSL lynx ftp://ftp.netbsd.org/pub/NetBSD-current/src/sbin/rcorder/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Wed, Oct 25, 2000 at 09:42:23AM +0200, Andrea Campi wrote: > Maybe we could have a script to do the dependency check and "compile" > everything in a single big file? Luke already has this support in NetBSD 1.5 for those who demand it, but its a secret. ;-) -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 02:58:08PM -0700, Jordan Hubbard wrote: > With the NetBSD stuff, this is not immediately obvious though I guess > one could have a top level rc file with an explicit ordering similar to > our various subdir Makefiles, Nope. All the /etc/rc.d/ files are scanned by `rcorder'. `rcorder' then creates a dependacy graph from information in each /etc/rc.d/ file. A walk of the graph is done to output the list of scripts in the order they should run in. To quote what you once wrote about `pib', the NetBSD implimentation is "slicker than two eels screwing in a bucket of snot!" :-) -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Wed, Oct 25, 2000 at 08:14:01PM +0200, Gerhard Sittig wrote: > but I don't see FreeBSD having this level of "rc lib" as NetBSD > has in rc.subr We would import the NetBSD rc.subr. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 02:56:07PM -0700, Jordan Hubbard wrote: > So, who wants to do a proof-of-concept implementation for -current > which integrates with our existing rc.conf mechanism? I was going to if no one else did. Who ever does it should coordinate with Luke M @ NetBSD. He is willing to make tweaks such that we could use as much of the NetBSD bits as possible. He really hopes we [BSD] can standardize on this interface. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make release" breakage - dokern.sh patch 2
On Tue, Oct 24, 2000 at 04:49:41PM -0400, John W. De Boskey wrote: > > IMO NFS needs to stay. It is *very* useful to many (including me). > > I haven't removed it. But it is an option. I was a very heavy > user of NFS, but it didn't matter to jkh when he removed it last > time. The switch to ftp isn't hard. Ultimately that is a call for JKH. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 12:31:57PM -0600, Warner Losh wrote: > The scripts themselves have the ordering dependencies. The startup > system runs them in the proper order. I don't know if this is > pre-computed or redone each boot. Redone on each boot up (and shutdown). -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 04:23:40PM +0700, Alexey Dokuchaev wrote: > Why can't I simply write kill -1 `cat /var/run/sendmail.pid`? What about deamons that don't understand `kill -HUP'? Sendmail didn't until very reciently. ``/etc/rc.d/some-deamon restart'' does the right thing reguardless how involved that might be. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Mon, Oct 23, 2000 at 08:21:39PM -0400, Matthew N. Dodd wrote: > There isn't any reason why rc.conf shouldn't continue to be useful in > either case. /etc/rc.conf and /etc/defaults/rc.conf are still used in the NetBSD 1.5 world. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 04:49:40AM +0700, Alexey Dokuchaev wrote: > Having dozens of small files instead of pair of big ones always > frustrates me when I have to work with linux. Maybe, but the greatly increased functionality makes it worth it. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 05:05:49AM +0700, Alexey Dokuchaev wrote: > Still, it would be better if I could choose between "classical" and "new" > startup layout, say, somewhere at the installation stage. Supporting two very different schemes is a support nightmare. And giveing good test coverage with our current resources would also be a problem. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: > 2. Make sure your kernel includes: > > devicerandom # Entropy device Are you implying the random.ko module is broken? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make release" breakage - dokern.sh patch 2
Before removing NFS, I'd remove the new `ncv', `nsp', and `stg' drivers. Not to mention the `vpo' Parellel port Zip drive device. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make release" breakage on today's -current
On Tue, Oct 24, 2000 at 09:42:54PM +0200, Rogier R. Mulhuijzen wrote: > >We used to, but we were trying to remove `apm0' from GENERIC. I've fixed > >to just `apm'. > > Might it be a good idea to make a INSTALL kernel config and a GENERIC > config? Nope, the two would be quickly out of sync. What make you think the person that forgot to change `apm0' to `apm' in dokern.sh would have remembered to have made the change in an INSTALL kernel config? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make release" breakage - dokern.sh patch 2
On Wed, Oct 25, 2000 at 04:48:14AM +0900, Motomichi Matsuzaki wrote: > > > Other candidates I've been pointed to include the removal of > > > /boot/boot[12] and NFS > > IMO NFS needs to stay. It is *very* useful to many (including me). > > I vote for 'remove NFS away'. > > Yes, there are many people using NFS install, but it is site-specific. And INET6 isn't site specific. It certainly is everywhere but maybe .jp. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make release" breakage - dokern.sh patch 2
On Tue, Oct 24, 2000 at 02:36:44PM -0400, John W. De Boskey wrote: > > the 'le' driver does not work. Can someone provide additional > information about why it's in GENERIC? Get confirmation that it does not work (one user isn't suffient in my book as there could be many issues which could make it ``not work'' for one person). > Other candidates I've been pointed to include the removal of > /boot/boot[12] and NFS IMO NFS needs to stay. It is *very* useful to many (including me). P.S. PLEASE trim the CC line. It has gotten redictulously long. To the point some might consider not sending a single message on this thread, else they'll get their mailbox flooded from then on. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make release" breakage on today's -current
On Tue, Oct 24, 2000 at 12:43:16PM -0600, Warner Losh wrote: > > apm is a good one to remove. We used to, but we were trying to remove `apm0' from GENERIC. I've fixed to just `apm'. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make release" breakage on today's -current
On Tue, Oct 24, 2000 at 10:44:31PM +0900, Makoto MATSUSHITA wrote: > How about removing /boot/boot[12] from floppies ? Committed! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make release" breakage on today's -current
On Tue, Oct 24, 2000 at 03:32:16PM +0200, John Hay wrote: > Why not remove NFS? That is what I do here when the snap floppy gets > too big. How many people install using NFS? (And can't easily change to > ftp.) Many. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make release" breakage on today's -current
On Tue, Oct 24, 2000 at 08:15:12AM -0500, Will Andrews wrote: > > I'm sure there are better things to disable, like MFS, SYSV*, P1003_P1B > and friends, and ICMP_BANDLIM. Only SYSVMSG is removed for the i386 case. SYS* for the Alpha. I'm assuming the SYS* left compiled in on the i386 is for X? Does P1003_P1B and ICMP_BANDLIM actually add code, or just set defaults, etc? If someone beats me to it, please compile GENERIC and GENERIC w/o ICMP_BANDLIM (and then again without P1003_P1B) and let us know how much space savings they would provide. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make release" breakage on today's -current
On Tue, Oct 24, 2000 at 03:59:20PM +0900, Makoto MATSUSHITA wrote: > Maybe kernel image for kern.flp is a little bit larger than a 1.44MB floppy. I just diked out more bits. Lets see if that will give us enough space on tonights snapshot build. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Mon, Oct 23, 2000 at 05:07:42PM -0400, Brandon D. Valentine wrote: > Hmm I don't have any NetBSD machines running the later 1.5 revisions > yet, so I've not seen the new scripts, lynx ftp://ftp.netbsd.org/pub/NetBSD-current/src/etc/rc.d/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Sun, Oct 22, 2000 at 09:41:51PM -0400, Bill Vermillion wrote:
> One of the reasons for the numbers in the SysVR4 arena is to
> set the order of execution so programs which other depend upon
> are executed first. How does the NetBSD solve this problem.
Very coolly. The main rc script runs a script named `rcorder' to
generate the proper order. rc.shutdown also uses `rcorder' but reverses
the ordering. Two examples are included below to show what `rcorder'
uses to generate the list. These NetBSD rc files also provide "start",
"stop", "restart", "status", etc. commands to assist the sysadmin.
Again, *very* slick and still quite BSD-like.
=== /etc/rc.d/ypbind ===
#!/bin/sh
#
# $NetBSD: ypbind,v 1.3 2000/05/13 08:45:10 lukem Exp $
#
# PROVIDE: ypbind
# REQUIRE: ypserv
. /etc/rc.subr
name="ypbind"
rcvar=$name
command="/usr/sbin/${name}"
start_precmd="ypbind_precmd"
ypbind_precmd()
{
_domain=`domainname`
if [ -z "$_domain" ]; then
warn "domainname(1) is not set."
return 1
fi
}
load_rc_config $name
run_rc_command "$1"
=== /etc/rc.d/ypserv ===
#!/bin/sh
#
# $NetBSD: ypserv,v 1.4 2000/06/02 22:54:13 fvdl Exp $
#
# PROVIDE: ypserv
# REQUIRE: rpcbind
. /etc/rc.subr
name="ypserv"
rcvar=$name
command="/usr/sbin/${name}"
required_vars="rpcbind"
start_precmd="ypserv_precmd"
ypserv_precmd()
{
_domain=`domainname`
if [ -z "$_domain" ]; then
warn "domainname(1) is not set."
return 1
fi
if [ ! -d /var/yp/$_domain/. ]; then
warn "/var/yp/$_domain is not a directory."
return 1
fi
}
load_rc_config $name
run_rc_command "$1"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: m4 not in build tools for make world
On Sun, Oct 22, 2000 at 01:01:57AM +0200, Rogier R. Mulhuijzen wrote: > > I don't know if m4 should be in the build tools that are made during make > world, but it isn't. No it shouldn't. > And because I had the GNU m4 installed as m4 and not gm4 the building > of the boot blocks went belly up (bootblocks crashed on boot). Then DON'T DO THAT. There is a reason the GNU M4 port installs it as `gm4'. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote: > with the mfs enable, it hangs there right after FILESYSTEM > checking, and with random_load set to YES, it hangs at ldconfig. mount_mfs is blocking on "rndblk". Our /dev/*random is fubar'ed *again*. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Sat, Oct 21, 2000 at 11:05:37AM -0700, Jordan Hubbard wrote: > > I wish to update rc.network6 and introduce rc.firewall6. > > H. I must confess that I see /etc as getting rather cluttered > these days. Is there no way to perhaps collapse some of the most > related functionality into single files and start passing arguments > or something? Just a comment.. At BSDcon Luke M showed me what the NetBSD 1.5 rc files look like. They've moved them all to /etc/rc.d/ and made them very granular (as SVR4, but w/o leading numbers in the filenames). The NetBSD implementation also solved all the issues people have brought up in the past -- dependacies, etc... We should just move to using their rc code. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
On Sun, Oct 22, 2000 at 12:14:03PM +0800, Donny Lee wrote: > /dev/da0s1e: FILESYSTEM CLEAN, SKIPPING CHECK > /dev/da0s1e: clean, 92565 free (125 frags, 11555 blocks, > 0.1%fragmentation) > > then no more, Next time hit control-T to find out what is hanging and why. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Which GCC in CURRENT? [Was: Re: Wine update]
On Mon, Oct 16, 2000 at 01:21:33PM +0200, Gerald Pfeifer wrote: > On Mon, 16 Oct 2000, Szilveszter Adam wrote: > > Also, since 2.96 has not even been released yet, I assume the > > maintainer (bruce, AFAIK) just makes sure that it builds and compiles > > stuff OK and so by the time 5.0 will be released and hopefully 2.96 > > too, we just have to push the button and it will be there. > > I can assert, with utmost authority ;-), that GCC 2.96 will never be > released by the GCC team. Correct, and FreeBSD 5.0 will ship with 5.0+ release. The import and use of GCC 2.96(7) in FreeBSD-CURRENT is to support development of the IA-64, x86-64, and PPC ports. Since FreeBSD-CURRENT is not a release and is a tool to use in getting to 5.0, we didn't mind importing a non-released version of GCC. Note that FreeBSD's warning of don't expect stability in -CURRENT will also be very true of the this compiler. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc and FreeBSD [was: Re: Which GCC in CURRENT? [Was: Re: Wine update]]
On Tue, Oct 17, 2000 at 04:40:53PM -0400, Marcel Moolenaar wrote:
> > Should any of you have some time to spend, those two PRs I mentioned above
> > are really critical.
I have issues with one of them -- IMHO FSF/GCC should not assume the
existence of crt{i,n}.o since they supply their own crt{begin,end}.o
(thru crtstuff.c). There is obivious assumpitons by crtstuff.c on what
crt{i,n}.o supplies, and thus seems logical GCC come with its own
crt{i,n}.s. This is not to say I am unbending on this (and it also
carries over into JDP's teritory), but I do want to rasie this issue on
the [EMAIL PROTECTED] (after BSDcon) mailing list to see what they say.
> David: Can you take a look at it, or shall I try to free some time for
> this. It sounds important enough from what I understand from Gerald.
I am tied up at BSDcon for the week. So I'll reply to this thread better
later.
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: /boot partition?
On Fri, Oct 13, 2000 at 07:18:05PM +0300, Maxim Sobolev wrote: > Nope, the loader can load stuff from other partitions, even from some strange > ones like msdos ;), so theoretically it should be possible to have /boot, or > even /boot/kernel, on another partition (it may require to tweak loader config > files, though), but I really do not see any reasons behind such weird setup. Our IA-64 offering may end up having /boot as a native partition (ie, vfat32) as their firmware understands it. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
Mike Smith points out that removing `vpo' kills parallel port Zip drives. Is this something we can live w/o for installs? > Index: dokern.sh > === > RCS file: /home/ncvs/src/release/scripts/dokern.sh,v > retrieving revision 1.35 > diff -u -r1.35 dokern.sh > --- dokern.sh 2000/09/29 03:24:03 1.35 > +++ dokern.sh 2000/10/14 22:55:45 > @@ -72,7 +72,15 @@ > -e '/SOFTUPDATES/d' \ > -e '/MFS/d' \ > -e '/NFS_ROOT/d' \ > + -e '/ncr/d' \ > -e '/atapist/d' \ > + -e '/lpt/d' \ > + -e '/ppi/d' \ > + -e '/vpo/d' \ > + -e '/ugen/d' \ > + -e '/uhid/d' \ > + -e '/ulpt/d' \ > + -e '/urio/d' \ > -e '/maxusers/d' \ > -e 's/ident.*GENERIC/ident BOOTMFS/g' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: removing global from tree
On Sat, Oct 14, 2000 at 10:32:11PM +0200, Gerhard Sittig wrote: > Backing out an rm'ed file should be as difficult as doing the sequence > I just tested to make sure: > > F=toberemoved.txt Coming up with the "F" list can be more than just ``ls -R /home/ncvs/src/contrib/global'' as older versions of global might have had files that weren't part of the the last version. Thus I'd have had to keep the commit message (or go find it in the archive, which would be some effort), to get the real list of files to revive. > F=toberemoved.txt # the name is misleading now :) > cvs log $F > REV=1.2 # the one before removal > cvs up -p -r$REV $F > $F > cvs add $F > cvs ci -m "revived file $F" > # and everything could be like before ... As you've just shown, this can be a real PITA. > But I feel that David wants to know this, too. Huh? Do what?? I fully understand how to remove, add, and revive files in the repo. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
> On Sat, Oct 14, 2000 at 01:54:39PM -0700, Jordan Hubbard wrote: > We've blown out the kern.flp image. Time for me to chop something > out again, unless there are any other suggestions. :| Mind if I commit this patch? Index: dokern.sh === RCS file: /home/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.35 diff -u -r1.35 dokern.sh --- dokern.sh 2000/09/29 03:24:03 1.35 +++ dokern.sh 2000/10/14 22:55:45 @@ -72,7 +72,15 @@ -e '/SOFTUPDATES/d' \ -e '/MFS/d' \ -e '/NFS_ROOT/d' \ + -e '/ncr/d' \ -e '/atapist/d' \ + -e '/lpt/d' \ + -e '/ppi/d' \ + -e '/vpo/d' \ + -e '/ugen/d' \ + -e '/uhid/d' \ + -e '/ulpt/d' \ + -e '/urio/d' \ -e '/maxusers/d' \ -e 's/ident.*GENERIC/ident BOOTMFS/g' @@ -115,6 +123,7 @@ -e '/ulpt/d' \ -e '/umass/d' \ -e '/ums/d' \ + -e '/urio/d' \ -e '/aue/d' \ -e '/cue/d' \ -e '/kue/d' \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
On Sat, Oct 14, 2000 at 01:54:39PM -0700, Jordan Hubbard wrote: > We've blown out the kern.flp image. Time for me to chop something > out again, unless there are any other suggestions. :| Things the Alpha has already diked out: ncr SYS* (not just SYSVMSG) lpt \ ppi / should not be needed for PLIP installs vpo (should it get turned on again) ugen uhid ulpt urio To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: removing global from tree
On Fri, Oct 13, 2000 at 10:01:59AM -0700, Steve Kargl wrote: > In revision 1.148 of src/usr.bin/Makefile, the hook for building > global was removed. This was 3.5 month ago. Is it time to move > src/contrib/global and src/usr.bin/global into the attic? Wow, that is still there. I forgot about it. I'll take care of this weekend. On Sat, Oct 14, 2000 at 03:03:57AM -0700, [EMAIL PROTECTED] wrote: > Yes, it should have been done at the time it was removed from the > Makefile. I didn't put it in the Attic when I disconnected it from the build in case someone came forward screaming about removing it. I figured it was much easier to back out a Makefile commit than get things from the Attic back to being alive. I had actually forgotten about it as no one did come forward. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make installkernel broken by recent manpage changes
> ===> joy > install -C -c -o root -g wheel -m 555 joy.ko /boot/kernel > install -C -c -o root -g wheel -m 444 joy.8.gz /usr/share/man/man8 > install: joy.8.gz: No such file or directory > *** Error code 71 Since the manpages are being moved elsewhere, I went ahead and removed them from the Makefile's since they were causing problems. -- -- David ([EMAIL PROTECTED]) Gnu is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make installkernel broken by recent manpage changes
On Fri, Oct 06, 2000 at 01:27:08PM -0700, Steve Kargl wrote: > ===> joy > install -C -c -o root -g wheel -m 555 joy.ko /boot/kernel > install -C -c -o root -g wheel -m 444 joy.8.gz /usr/share/man/man8 > install: joy.8.gz: No such file or directory > *** Error code 71 I'll check it out. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: downgrade to stable?
On Sat, Oct 07, 2000 at 12:04:15PM -0600, Warner Losh wrote: > and then looking for libraries that are too new. Would one not want to keep the libraries that are too new for things in /usr/local that would need them. Since the shlib symlink will be for the "older" lib, there really isn't any problem having too new ones present. -- -- David ([EMAIL PROTECTED]) Gnu is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs servers load
On Sat, Oct 07, 2000 at 10:19:32AM -0700, [EMAIL PROTECTED] wrote: > of the time. Given where you live, you might want to try cvsup7, Hey! That's the one I use -- don't tell anyone about it. :-))) Where is cvsup8? I get the fastest ping times to it. A traceroute implies it is also in Seatle, WA. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic in ufs_extattr_uepm_destroy()
On Fri, Oct 06, 2000 at 09:41:29AM -0400, Robert Watson wrote:
> Index: ffs_vfsops.c
> ===
> RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_vfsops.c,v
> retrieving revision 1.129
> diff -u -r1.129 ffs_vfsops.c
> --- ffs_vfsops.c 2000/10/04 04:44:51 1.129
> +++ ffs_vfsops.c 2000/10/06 13:40:57
> @@ -772,7 +772,7 @@
> int mntflags;
> struct proc *p;
> {
> - register struct ufsmount *ump;
> + register struct ufsmount *ump = VFSTOUFS(mp);
> register struct fs *fs;
> int error, flags;
This has a KNF style problem. The line you remove should stay and
"ump = VFSTOUFS(mp);" added.
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Today -current broken on build
On Mon, Oct 02, 2000 at 02:24:12PM -0700, Mike Smith wrote: > > The build was silently broken by AMD including previously. > It wasn't exposed until recently. The correct fix was still to not > include anywhere in AMD (or anywhere else in userland for > that matter). Yes I know. I was trying to figure out and explain why it was just now exposed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Today -current broken on build
On Sun, Oct 01, 2000 at 12:14:25PM -0700, Mike Smith wrote: > Er, this is probably the wrong fix. It sounds like the kernel 'callout' > structure is ending up visible in userland, which it shouldn't. The build was broken by the inclusion of in sys/sys/mbuf.h rev 1.56. includes sys/sys/proc.h as of rev 1.7. sys/sys/proc.h includes sys/sys/callout.h and that's were it comes from. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Today -current broken on build
On Sun, Oct 01, 2000 at 12:14:25PM -0700, Mike Smith wrote: > > > I hate to spoil the moment ... but does anyone have an idea what the > > > fix is? Nothing in the amd directory seems to have changed in the > > > past couple of weeks, so it must be somewhere else, and I'm not bright > > > enough to figure out where. > > > > Yeah, somebody forgot that typedefs and structure names can't > > conflict. :) I've just committed the fix. > > Er, this is probably the wrong fix. It sounds like the kernel 'callout' > structure is ending up visible in userland, which it shouldn't. This commit also took a file off the vendor branch and the maintainer of src/contrib was not consulted. The committer that committed something w/o testing `make world' should have backed out their commit and then discussed that they wanted a change made in Amd or taken a different approach in their commit. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /modules vs. /boot/kernel
On Tue, Sep 26, 2000 at 10:04:34PM -0400, John DeBoskey wrote: >Question, is /modules still valid? Yes. It should be used for 3rd party modules only. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel builds to wrong location?
On Sat, Sep 16, 2000 at 10:54:22PM -0500, Mike Meyer wrote: > I cvsupped and rebuilt earlier to today, only to find that the kernel > was installed as /boot/kernel/kernel instead of > /boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of > a surprise. > > Is this a bug, or did I happen to catch the world in a state of change It is not a bug. I was beaten to death to change "kernel.ko" back to "kernel". -- -- David ([EMAIL PROTECTED]) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: .indent.pro for KNF?
On Sun, Sep 24, 2000 at 08:24:44PM +0200, Blaz Zupan wrote:
> Does anybody have a .indent.pro file for indent(1) that enforces KNF style as
> specified in style(9)?
>From Bruce Evans, this is " a wrapper around indent(1) to print the
percentage changes that indent with the best (least bad) approximation to
KNF parameters that I know of would do."
---
#!/bin/sh
TMP=`mktemp /tmp/_knfom.XX`
TMPBAK=`mktemp /tmp/_knfom.XX`
trap 'rm -f $TMP $TMPBAK; exit 1' 1 2 3 13 15
trap 'rm -f $TMP $TMPBAK' 0
for i
do
cp "$i" $TMP
# XXX the typedef list hasn't been updated since 1993, except for the last
# two entries.
indent -npro \
-TBitSetTmp \
-TDBM \
-TDIR \
-TFix16_peh \
-TFix24_peh \
-TFix32_peh \
-TFix48_peh \
-TFix_peh \
-TGPT \
-TIntTmp \
-TLLattrib \
-TLLtoken \
-TPix \
-TProtoHook \
-TRatTmp \
-TSGTTY \
-TSeqNum \
-TStrTmp \
-TXCHAR \
-T_Fix \
-T__sFILE \
-T__sighandler_4_3_t \
-T__sighandler_t \
-T_code \
-T_dirdesc \
-T_ftsent \
-T_physadr \
-T_quad \
-T_uquad \
-T_vsIoAddr \
-T_vsStats \
-T_vs_box \
-T_vs_cursor \
-T_vs_event \
-Tbitstr_t \
-Tboolean_t \
-Tcaddr_t \
-Tcbool \
-Tcc_t \
-Tclock_t \
-Tclockframe \
-Tcomp_t \
-Tcomplex \
-Tdaddr_t \
-Tdb \
-Tdb_addr_t \
-Tdb_expr_t \
-Tdb_regs_t \
-Tdes_block \
-Tdev_pager_t \
-Tdev_t \
-Tfd_mask \
-Tfd_set \
-Tfhandle_t \
-Tfixpt_t \
-Tfpos_t \
-Tfsid_t \
-Tgid_t \
-Tino_t \
-Tint16 \
-Tint32 \
-Tjmp_buf \
-Tkey_t \
-Tlabel_t \
-Tllinsert \
-Tlock_data_t \
-Tlock_t \
-Tmode_t \
-Tn_long \
-Tn_short \
-Tn_time \
-Tnetobj \
-Tnew_handler_t \
-Tnfstype \
-Tnfsv2fh_t \
-Tnlink_t \
-Toff_t \
-Tone_arg_error_handler_t \
-Tpd_entry_t \
-Tpid_t \
-Tpmap_statistics_t \
-Tpmap_t \
-Tpt_entry_t \
-Tptrdiff_t \
-Tpv_entry \
-Tqaddr_t \
-Tqhdr \
-Tqueue_chain_t \
-Tqueue_entry_t \
-Tqueue_head_t \
-Tqueue_t \
-Tregexp \
-Tsegsz_t \
-TRefNum \
-Tsig_t \
-Tsigjmp_buf \
-Tsigset_t \
-Tsimple_lock_data_t \
-Tsimple_lock_t \
-Tsize_t \
-Tspeed_t \
-Tssize_t \
-Tsw_blk_t \
-Tsw_bm_t \
-Tsw_pager_t \
-Tswblk_t \
-Ttcflag_t \
-Ttcp_seq \
-Ttime_t \
-Ttimeout_func_t \
-Ttpr_t \
-Ttwo_arg_error_handler_t \
-Tu_char \
-Tu_int \
-Tu_int32 \
-Tu_long \
-Tu_short \
-Tuid_t \
-Tuint16 \
-Tuint32 \
-Tushort \
-Tva_list \
-Tvm_inherit_t \
-Tvm_map_entry_t \
-Tvm_map_object_t \
-Tvm_map_t \
-Tvm_object_hash_entry_t \
-Tvm_object_t \
-Tvm_offset_t \
-Tvm_page_t \
-Tvm_pager_t \
-Tvm_prot_t \
-Tvm_size_t \
-Tvm_statistics_data_t \
-Tvm_statistics_t \
-Tvn_pager_t \
-TvsIoAddrAddr \
-Twchar_t \
-Txdrproc_t \
-Tsy_call_t \
-Tvop_t \
-bad -bap -nbbb -nbc -br -nbs -c33 -cd33 -cdb -ce -ci4 -cli0 -d0 -di0 -ndj \
-ei -nfc1 -nfcb -i8 -ip -l79 -lc77 -nlp -npcs -psl -sc -nsob -nv \
$TMP $TMPBAK
(wc -l "$i" | tr '\012' ' '; diff $TMPBAK $TMP | grep -cv '^[1-9]') |
awk '{printf("%7.3f%% %s\n", 100 - 100 * $3 / 2 / ($1 + .1), $2)}'
done
---
-di0 is wrong for global declarations but right for local declarations.
indent -di8 would get the tabs for global declarations wrong anyway.
-nfcb is an extension to prevent formatting of big comments - otherwise
there is too much comment reformatting compared with code reformatting
(there still is).
These diffs implement -[n]fcb and attempt to implement no-space=after-sizeof
(not optional) and no-space-after 'struct foo *' (not optional). Without
these, indent unKNFizes even more perfectly KNF code.
The most serious bugs in indent are that it doesn't understand ANSI
function headers, and -lp doesn't actually work. I think these are
both fixed in gnu indent.
diff -c2 args.c~ args.c
*** args.c~ Sun Aug 29 11:15:27 1999
--- args.c Sun Aug 29 11:15:32 1999
***
*** 111,114
--- 111,115
"fb", PRO_FONT, 0, 0, (int *) &bodyf,
"fc1", PRO_BOOL, true, ON, &format_col1_comments,
+ "fcb", PRO_BOOL, true, ON, &format_block_comments,
"fc", PRO_FONT, 0, 0, (int *) &scomf,
"fk", PRO_FONT, 0, 0, (int *) &keywordf,
***
*** 132,135
--- 133,137
"nei", PRO_BOOL, true, OFF, &ps.else_if,
"nfc1", PRO_BOOL, true, OFF, &format_col1_comments,
+ "nfcb", PRO_BOOL, true, OFF, &format_block_comments,
"nip", PRO_BOOL, true, OFF, &ps.indent_parameters,
"nlp", PRO_BOOL, true, OFF, &lineup_to_parens,
diff -c2 indent.1~ indent.1
*** indent.1~ Sun Aug 29 11:45:30 1999
--- indent.1Sun Aug 29 11:46:03 1999
***
*** 64,67
--- 64,68
.Bk -words
.Op Fl fc1 | Fl nfc1
+ .Op Fl fcb | Fl nfcb
.Ek
.Op Fl i Ns Ar n
***
*** 249,252
--- 250,262
used. The default is
.Fl fc1 .
+ .It Fl fcb , nfcb
+ Enables (disables) the formatting of block comments (ones that begin
+ with `/*\\n'). Often, block comments have been not so carefully hand
+ formatted by the programmer, but reformatting that would just change
+ the line breaks is not wanted. In such cases,
+ .Fl nfcb
+ should be used. Block comments are then handled like box comments.
+ The default is
+ .Fl fcb .
.It Fl i Ns Ar n
The
Re: Latest kernel/module restructuring
On Tue, Sep 12, 2000 at 06:11:20PM +0200, Niels Chr. Bank-Pedersen wrote: > Hmm, how about those of us doing buildworlds/buildkernels on > one (nfs)server for subsequent installworlds/installkernels > on multiple other machines? Use the `make reinstall' target with KERNEL_KO set to the name of the kernel core filename you want. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please consider some cosmetic changes in boot messages
On Tue, Sep 12, 2000 at 06:28:05PM -0700, Kris Kennaway wrote: > > I'm also not sure where the rumors about a FreeBSD 4.1.5 got started > > since I'd certainly never planned on such a thing, that, I think, 4.1.1 rather than 4.1.5 please. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: SMP code commit iminent
On Tue, Sep 05, 2000 at 09:57:05PM -0700, Matthew Jacob wrote: > Jason- I think we'd all appreciate a UTC timestamp suitable for -D that we can > all use to checkout stuff prior to the big change. There will be a TAG for that to make life easier. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: SMP code commit iminent
On Tue, Sep 05, 2000 at 05:58:32PM -0700, Jason Evans wrote: > this email is a minimum 24 hour notice that SMP code will be committed > to -current. What is the status of the Alpha bits? Will we have a working kernel after the commit, or should we site tight for a week while the Alpha bits are tweaked into working status? -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
** HEADS UP ** kernel changed to /boot/kernel/kernel.ko
I just committed a change to the loader and kernel Makefiles such that the kernel is now named "kernel.ko" and it the modules live in ``/boot/kernel'' (and ``/boot/kernel.old''). After your next world build, the loader will not load ``/kernel'' by default, so you want to make sure you build and install a kernel using sources matching the loader source. Third party modules (ie, those not part of the base FreeBSD) should be placed in ``/boot/modules'' (or ``/modules'') and the FreeBSD build system will not disturb them. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: streams module no longer compiles
On Thu, Aug 31, 2000 at 10:24:46PM -0700, George W. Dinolt wrote: > If I read things correctly you relocated the svr4 pieces from sys to > sys/compat in todays -CURRENT. It appears that the streams module > depends on several include files which you moved. As a result, the > streams module no longer compiles. Fixed. Thanks!! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld errors....
On Thu, Aug 31, 2000 at 02:02:57PM -0400, Donn Miller wrote: > See the attached "errors". > ===> librsausa > sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 librsaUSA.a >/usr/obj/usr/src/i386/usr/lib > sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 444 librsaUSA.so.1 >/usr/obj/usr/src/i386/usr/lib > ln -sf librsaUSA.so.1 /usr/obj/usr/src/i386/usr/lib/librsaUSA.so As expected. > ===> libssh > cd /usr/src/gnu/lib/libgcc; make depend; make all; make install Huh?? `libssh' goes into src/gnu/lib/libgcc? Are you sure your /usr/src is clean? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How do i activate /boot/device.hints in loader.conf?
On Wed, Aug 30, 2000 at 11:49:25AM +, Justin Ovens [[EMAIL PROTECTED]] wrote: > I have a little Q: when i compile my kernel for 5.0-CURRENT > > [root@calloc:/usr/src/sys/compile/CALLOC]# make install > You must activate /boot/device.hints in loader.conf. > *** Error code 1 > > How do i activate it? See /usr/src/UPDATING. If you don't find the answer there, update your 'UPDATING'. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: hints static wiring
On Mon, Aug 28, 2000 at 06:29:21PM -0700, Brooks Davis wrote: > On Tue, Aug 29, 2000 at 10:25:26AM +0930, Greg Lehey wrote: > > At the very least, there appears to be confusion about how to use the > > hints. I can see two conflicting views here: > > > > 1. You must have a /boot/device.hints file, but it may be empty. > > This is minimally correct. I.e. that's what the build system requires. > This works if you build static hints into your kernel. Please stop saying FUD. The *INSTALL* system requires /boot/device.hints. The *BUILD* process does not. > > 2. You must have a /boot/device.hints file, and it must contain at > > least some entries. > > This is more correct. The new world order says that hints are not in the > kernel, instead they are loaded by the loader at boot time. I would quite to so far. I know many that will continue to compile static hints into their kernels until that ability is removed. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: hints static wiring
On Mon, Aug 28, 2000 at 08:24:50AM -0500, Mike Meyer wrote: > Well, yeah, I'd expect that. I'm still trying to figure out what > *good* failing to compile unless there's an empty /boot/device.hints The kernel does not fail to *BUILD*. ``make install'' is what fails. I agree that the requirement is somewhat anonying. But, it is better to have this slight anonyance than for many to to install and boot a kernel that would be broken. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
On Wed, Aug 23, 2000 at 01:36:56PM +0100, Konstantin Chuguev wrote: > Do you use /usr/local for anything? Yes, local stuff. IMHO, the Ports Collection using /usr/local was the biggest mistake of it. The ports collection should have used /usr/pkg/ as NetBSD does. I have to create /usr/truely-local on my FreeBSD machines. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
On Sun, Aug 13, 2000 at 01:14:09AM -0600, Warner Losh wrote: > : Won't the 'cvs diff' command tell you about such things? If not, > : that's yet another argument for ditching cvs in favor of something > : without so many flaws (like Perforce). > > Not when the files are in multiple different directories and you have > mutliple patches cooking in your tree. I committed files in > sys/pccard, but they depended on one in sys/dev/pccard which I > honestly thought I'd checked in with an earlier newcard fix. I'd been > running the patches long enough that I basically forgot. Which is why I keep a virgin src checkout and I CVSup (with "-i") right after large commit and try building the code again in the virgin tree. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Loss of fetch(1) functionality with libfetch
On Thu, Aug 03, 2000 at 01:26:01PM +0200, Dag-Erling Smorgrav wrote: > Peter Jeremy <[EMAIL PROTECTED]> writes: > > Whilst the environment is somewhat safer than the command line, I'd > > still prefer not to have passwords embedded in environment variables. > > Since ps(1) no longer allows users to view other users' processes' > environment, I don't think it's a very big issue anymore. POLA says you should not have changed what fetch(1) expects from the environmental var. > > Has this feature been deliberately left out, or is it just one of the > > bits that you haven't gotten around to implementing yet? Would you > > be interested in patches to implement it? > > Sure. The only clean way of doing this (that I can think of) would be > to add an interface to libfetch for registering password-prompting > callbacks. Then it should have been added -- especially before being MFC'ed. -- -- David ([EMAIL PROTECTED]) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world breakage
On Fri, Aug 04, 2000 at 08:38:17PM +0200, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, "David O'Brien" writes: > >Quite sorry, my contrib/gdb/ activities were suppose to be shielded from > >users. > And vice-versa I presume :-) G. I should go back to bed -- that's what I meant in the first place. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world breakage
On Fri, Aug 04, 2000 at 08:24:30PM +0300, Ruslan Ermilov wrote:
> On Fri, Aug 04, 2000 at 10:16:32AM -0700, Scott Flatman wrote:
> > In file included from
> > /u1/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/mdebugread.c:2774:
> > mkdep: compile failed
> > *** Error code 1
> 99 conflicts from the today's gdb import were not resolved yet...
Gr gnu/usr.bin/binutils/gdb/Makefile was still grabbing sources from
contrib/gdb rather than contrib/gdb.291. I goofed when I switched over
to that source by only getting gdb{replay,server} pointed to it.
I've committed an untested fix to gnu/usr.bin/binutils/gdb/Makefile to
hopefully get people going again. I've started a buildworld to make
sure.
Quite sorry, my contrib/gdb/ activities were suppose to be sheilded from
users.
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
