> On Dec 19, 2016, at 12:27 PM, Adrian Chadd wrote:
>
> So although I like the sentiment, I don't think using dtrace for
> program logging is the right answer. I like what apple did to wrap
> the program logging stuff so people didn't just write their own
> libraries (hi!) and so there's a unif
> On Nov 3, 2016, at 1:56 PM, David Chisnall wrote:
>
> Is the depressing thing here that even something as recent as 386BSD 0.1
> assumed that ASCII was enough for the whole world?
“Recent??” :-D
___
freebsd-current@freebsd.org mailing list
https:/
> On May 1, 2016, at 5:49 PM, Warren Block wrote:
>
> The first quarter of 2016 showed that FreeBSD retains a strong sense of
> ipseity. Improvements were pervasive, lending credence to the concept
> of meliorism. [ … ]
I, for one, learned at least 4 new words in that announcement, 3 of w
> On Jul 27, 2015, at 7:32 AM, Willem Jan Withagen wrote:
>
> You have any idea what is/was actual the hardware that was in the box?
>
> If I remember correctly we gave Jordan a check for like 5000 guilders.
> Which I guess would be 2500 us$ at that time. Which was not an enormous
> amount of m
On Apr 1, 2014, at 10:11 PM, Matt Olander wrote:
> This is like trying to predict automobile technology and dominant
> car-makers by 1905. There's always room for competition. Take a look
> at what's happening right now in the auto-industry. Tesla came out of
> nowhere 125 years after the invent
On Apr 1, 2014, at 9:33 PM, Person, Roderick wrote:
> Why aren't all the nerds and small businesses out there a market?
Too few of you to justify the capital outlay. Now, if we were talking about a
$1500 watch that was very nerdy and appealed to the inner James Bond in lots of
non-nerds, t
On Apr 1, 2014, at 9:12 PM, Jim Thompson wrote:
> I have Macs at work (typing on one now), and a mac at home. I like them.
> [ … ]
> It’s just like being back in the 80s, when Unix had a desktop market, only
> much, much faster.
Worry not, there’s a product just for you now!
http://www.macs
On Apr 1, 2014, at 10:46 AM, Eitan Adler wrote:
> That is why on this date I propose that we cease competing on the
> desktop market. FreeBSD should declare 2014 to be "year of the Linux
> desktop" and start to rip out the pieces of the OS not needed for
> server or embedded use.
>
> Some of y
On Oct 28, 2013, at 2:28 AM, Slawa Olhovchenkov wrote:
> As I see ZFS cretate seperate thread for earch txg writing.
> Also for writing to L2ARC.
> As result -- up to several thousands threads created and destoyed per
> second. And hundreds thousands page allocations, zeroing, maping
> unmaping
No, the NFS server it depends on is down. Still working on getting it
back up.
>
> I am trying to install one of the -current snapshots, but
> current.freebsd.org doesn't seem to want to let me log in as anonymous
> (some problem saying it cannot set guest access). Has the procedure
> changed
This is a different problem. The stable.freebsd.org machine, on which
all the really big NFS storage lives, failed to come back up from a
reboot last night and I'm trying to get it restarted now. The terminal
server also appears to be sick or I'd be able to intervene remotely. :(
- Jordan
>
>
No, the NFS server it depends on is down. Still working on getting it
back up.
>
> I am trying to install one of the -current snapshots, but
> current.freebsd.org doesn't seem to want to let me log in as anonymous
> (some problem saying it cannot set guest access). Has the procedure
> changed
This is a different problem. The stable.freebsd.org machine, on which
all the really big NFS storage lives, failed to come back up from a
reboot last night and I'm trying to get it restarted now. The terminal
server also appears to be sick or I'd be able to intervene remotely. :(
- Jordan
>
>
My, is it April 1st already? How quickly time flies! December feels
like it was just yesterday!
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> BTW, how dou you think my other patch (use 'devfs' while mounting
> filesystems, use fsck_ffs instead of fsck) for sysinstall, which was
> posted about a week before to [EMAIL PROTECTED]? You can fetch from:
>
> http://people.freebsd.org/~matusita/5.0-CURRENT-20011121-JPSNAP_usedevfs
/patch>
Looks good to me, I'd say commit it!
- Jordan
> dsyphers> DEBUG: kget: error buffer sizing
> matusita> This is because sysinstall still want to get userconfig data
> matusita> and put the result to /boot/kernel.conf.
>
> Userconfig was gone in 5-current, so we can safely remove kget() from
> sy
> I don't know -current. what is the feature which replace kget ?
There is none.
> does boot -c (or whatever) still exists ? is it possible to
> edit .hints at boot time ?
No.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> If you mean what I mean, that guy was Polish, and that stuff still sits in
> the tree:
Yeah, that was it, sorry - I'm always getting Germany and Poland mixed
up! No, not really, please don't hit! ;)
That's cool - I should look at this. A perfect excuse to pick up
forth again, I think.
- Jor
that stuff?
- Jordan
>
> On 13-Sep-2001 Jordan Hubbard wrote:
> > Cool, can I see it?
>
> Sure..
> http://www.gsoft.com.au/~doconnor/sysinstall-kld.diff
>
> Mmm dynamic libdialog menus :)
>
> ---
> Daniel O'Connor software and network engineer
> for Genesi
drwxr-xr-x 20 root wheel 1024 Oct 11 22:17 5.0-20011011-CURRENT
Come 'n get it. No warrantees stated or implied as to how far these
bits get you after you transfer them, of course. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of t
Amusement? Excitement you mean! :-)
That's REALLY a significant milestone and the IA-64 is by no means a
simple architecture to come to grips with. My hat is off (yet again)
to Doug! I think that makes two 64 bit architecture ports he's now
had a lot to do with. :)
- Jordan
To Unsubscribe: s
install failure
Date: Wed, 3 Oct 2001 16:12:21 -0500
> > > * Jordan Hubbard <[EMAIL PROTECTED]> [011003 15:33] wrote:
> > > > As you've already noticed, sysinstall basically tries to create the
> > > > device nodes it needs under the old assumption th
sysinstall, by design, knows very little about devices. It uses
libdisk(3) as the abstraction for dealing with all disks in
particular.
> * Jordan Hubbard <[EMAIL PROTECTED]> [011003 15:33] wrote:
> > As you've already noticed, sysinstall basically tries to create the
>
Sure, I just don't have time to work on this right now.
- jordan
>
> D'ya think it might be time for a 3rd floppy?
>
>
> On Wed, 3 Oct 2001, Jordan Hubbard wrote:
>
> > sh -e /usr/src/release/scripts/doFS.sh /R/stage/floppies/kern.flp /R/stage /mnt
>1
As you've already noticed, sysinstall basically tries to create the
device nodes it needs under the old assumption that /dev will be
mostly empty. Now that devfs is the default, phk needs to update
libdisk so that it doesn't attempt to make the device nodes in this
way. Fortunately, the person w
sh -e /usr/src/release/scripts/doFS.sh /R/stage/floppies/kern.flp /R/stage /mnt 1440
/R/stage/image.kern 8 fd1440
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 6.
Warning: 1216 sector(s) in last cylinder unallocated
/dev/
> Maybe I keep pushing on this issue because there have been times in
> the past where FreeBSD has been prepared to pay programmers to write
> critical project progressing pieces of code.
Well if that's your rationale then you can stop pushing because I can
state categorically that "FreeBSD" does
Progress in these types of situations nearly always comes from people
with enough self-interest in the problem area to actually commit to
working on it. Rather than asking for people who have written an
autofsd to step forward, why not instead start working on this project
yourselves and ask for
The bug doesn't exist in 4.4 either. It was fixed prior to release.
Doesn't anyone read commit mail anymore?! :-(
- Jordan
> Thus spake Andrey A. Chernov ([EMAIL PROTECTED]):
>
> > Please, read me carefully. This bug not exist in -current, where it is
> > disabled by mistake via commit I compl
> Hm. Isn't this a strong sign that something fundamental must be done
> about the boot floppy process? Alpha has been suffering from this longer
> already due to the bigger binaries.
Hey, be my guest, just so long as we can install from whatever you
come up with. :-) Seriously, the fact that it
I don't know what the KSE commit added (or if it was even anything
more than bad timing), but we've hit the limit on the kernel floppy
again (x86):
Setting up /boot directory for kern floppy
/R/stage/image.kern/kernel: 53.9% -- replaced with /R/stage/image.kern/kern
el.gz
sh -e /usr/src/rele
First we had hardware problems, then NFS was broken on the cluster for
awhile, preventing current.freebsd.org from getting at the CVS
repository. It's fixed now and I see that a snapshot is building
as we speak.
- Jordan
From: Alexey Zelkin
<[EMAIL PROTECTED]> Subject: current.freebsd.org Date:
Are you guys on crack? Scheme is just a dialect of LISP, where "LISP"
could also just as easily be any one of MacLisp, InterLisp, Franz
Lisp, Common Lisp or one of many other possibilities. The very
acronym lacks specific meaning without an additional qualifier.
Scheme can also dynamically build
From: "Daniel C. Sobral" <[EMAIL PROTECTED]>
Subject: Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Date: Wed, 05 Sep 2001 15:55:16 -0300
> I myself questioned the wisdom of using Forth at the time, and Jordan
> simply replied I was free to find a more popular language with a freely
If you think that's an acceptable work-around then by all means
commit it. Thanks!
- Jordan
From: Bruce Evans <[EMAIL PROTECTED]>
Subject: Re: Build problem in -current
Date: Mon, 3 Sep 2001 21:36:46 +1000 (EST)
> On Sun, 2 Sep 2001, Jordan Hubbard wrote:
>
> > cd /u
cd /usr/src/usr.bin/xinstall; make _EXTRADEPEND
echo xinstall: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend
cc -O -pipe-I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/xinstall
/xinstall.c
cc -O -pipe-I/usr/obj/usr/src/i386/usr/include -static -o xinstall xinstal
l.o
xinstall
This project has always been more than just its core developers,
whomever they might be at any one time (and if history has shown us
anything, it's that it's a constantly changing cast). This means that
anyone is free to chime in with their opinion on any project decision,
just as the people doin
From: Jim Bryant <[EMAIL PROTECTED]>
Subject: Re: Why is csh tcsh? This can be a bad thing...
Date: Thu, 23 Aug 2001 22:23:01 -0500
> Because of certain differences, it cannot be used wholesale as a
> replacement for csh.
Then please enumerate them so that they can be given due attention.
This
From: "David O'Brien" <[EMAIL PROTECTED]>
Subject: Re: iso target in release/Makefile
Date: Mon, 20 Aug 2001 14:06:34 -0700
> It is part of a patch set I sent you for review.
And that patch looks good - please commit it and then merge the
resulting changes into RELENG_4 if you get the chance. T
From: "David O'Brien" <[EMAIL PROTECTED]>
Subject: Re: iso target in release/Makefile
Date: Mon, 20 Aug 2001 11:43:16 -0700
> You didn't MFC the iso.1 target. We are all building releases on
> RELENG_4 right now :-) (-current releases have been broken for quite a
> while). Thus my patch was dev
H. I'm not sure why this reinvents a lot of the "wheel" in the
already existing iso.1 target. Could you explain its purpose a little
better as well as why you didn't simply conditionalize the iso.1
target in some way if it didn't currently suit? As it is, we have
two targets now and that do
No, the machine is dead and we haven't managed to get a replacement
going yet. Hopefully in late August, as soon as everyone involved is
back from vacation.
- Jordan
From: Wolfram Schneider <[EMAIL PROTECTED]>
Subject: no new snapshot on ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/
Dat
From: Peter Wemm <[EMAIL PROTECTED]>
Subject: Re: No more snapshots of -CURRENT?
Date: Thu, 12 Jul 2001 05:49:59 -0700
> Actually, I think we just need to pester jkh nicely to get somebody to
> copy over the stable build script, s/stable/current/, s/-rRELENG_4/-A/
> and fire it up.
I'm willing
No, it simply means that the machine has been too ill to make
snapshots for awhile. We're in the process of replacing it, but
everyone involved has been really busy. :(
- Jordan
From: John Indra <[EMAIL PROTECTED]>
Subject: No more snapshots of -CURRENT?
Date: Thu, 12 Jul 2001 13:50:34 +0700
>
Kennaway <[EMAIL PROTECTED]>
Subject: Re: chgrp broken on alpha systems
Date: Thu, 5 Jul 2001 16:22:27 -0700
> On Thu, Jul 05, 2001 at 04:12:22PM -0700, Jordan Hubbard wrote:
> > Since David's busy, I'm working on it now. Just some build issues to
> > be worked out
Since David's busy, I'm working on it now. Just some build issues to
be worked out since warnings were made fatal recently.
- Jordan
From: Matthew Jacob <[EMAIL PROTECTED]>
Subject: Re: chgrp broken on alpha systems
Date: Thu, 5 Jul 2001 14:17:51 -0700 (PDT)
>
> David claimed he would upgrade
Thanks, this is my fault too given that I tried to fix it myself
and didn't raise it with you earlier. :(
From: "Mark M. Lutgen" <[EMAIL PROTECTED]>
Subject: [[EMAIL PROTECTED]: Re: current.freebsd.org down?] (fwd)
Date: Mon, 25 Jun 2001 13:20:55 -0500 (CDT)
> I was just told about this and shou
Yes, it is. I'm trying to get it back online but it needs a hard reset
since it's wedged beyond the point where I can do anything useful
from the serial console.
- Jordan
From: John Doe <[EMAIL PROTECTED]>
Subject: current.freebsd.org down?
Date: Mon, 25 Jun 2001 09:33:52 -0700 (PDT)
> is curr
It seems your argument to disallow null symlinks got somehow taken
as an argument to disallow all "invalid" symlinks then.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
From: Matt Dillon <[EMAIL PROTECTED]>
Subject: Re: symlink(2) [Was: Re: tcsh.cat]
Date: Fri, 15 Jun 2001 22:01:47 -0700 (PDT)
> Symlinks do not have to contain paths. People use them for all sorts
> of things so it would be totally inappropriate to put any sort of
True. It would break
Not to my knowledge, though anyone is free to create one.
- Jordan
From: [EMAIL PROTECTED] (Stefan Carstens)
Subject: Mirror ?
Date: Sun, 10 Jun 2001 16:03:47 +0200
> Are there mirrors of current.freebsd.org available ?
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebs
From: Kenneth Wayne Culver <[EMAIL PROTECTED]>
Subject: dual athlons
Date: Thu, 7 Jun 2001 16:18:13 -0400 (EDT)
> Just curious, but are there plans to support the EV6 bus that the dual
> athlon motherboards use? I'm not going to buy that kind of system unless
> FreeBSD 5 will support it.
Both Fr
> Could you please be more specific on what you mean by "disuse"? I.e. what
> was the problem with that stuff and what goes wrong? Do you against its
> resurrection by what reasons?
E.g. we went and translated a bunch of the *.TXT files into various
languages (among them Russian) and then gave sy
Look through the cvs history for sysinstall - you'll see that it
already had much of that already, back around 2.0.5 I think. It
was eventually removed again due to disuse.
- Jordan
From: "Andrey A. Chernov" <[EMAIL PROTECTED]>
Subject: sysinstall and wrong /etc/ttys types
Date: Fri, 11 May 200
> You'll see a detailed analysis soon, patches will come only
> after we've agreed on a way to fix the problem.
You've already had some folks respond to this, though I think the
argument has been mischaracterized as a "BSD vs Linux" thing. It's
not.
What people are (IMHO) really trying to argue
From: Terry Lambert <[EMAIL PROTECTED]>
Subject: PATCH: partial fix for broken "make release"...
Date: Wed, 2 May 2001 22:00:37 + (GMT)
> The "make release" stuff is broken, at least in 4.3, and possibly
> before that.
>
> There are several obviously broken things:
>
> o The libssh stuf
> Say, FreeBSD is usually pretty safe, even in CURRENT.
> Has something near this magnitude of Really Bad Stuffage snuck into the
> codebase before?
No, it's not common, and it generally takes a Dane swinging something
sharp to inflict quite this much damage on our user base. ;-)
- Jordan
To Un
> However, a specific hack to cp(1) is what a lot of people don't like.
> If FreeBSD contained every little hack every committer had used to
> address specific problems, it'd be a mess.
I was told that the "hack" everyone is referring to is already
implemented in several other operating systems,
> And to come back on topic: Portable scripts also should
> _not_ assume that there are no limits on the length of
> shell commands. On the other hand, portable scripts can
> legitimately assume that xargs supports -i and -I, which
> ours doesn't.
Agreed on both counts. I guess we should fix t
From: Oliver Fromme <[EMAIL PROTECTED]>
Subject: Re: cp -d dir patch for review (or 'xargs'?)
Date: Sat, 21 Apr 2001 17:27:04 +0200 (CEST)
> Not all users use /bin/sh. Scripts needn't be written
> in /bin/sh ...
Actually, just to jump in and correct this, scripts *should* be
written in /bin/sh.
> Do you have a script that will pull in the latest snapshot and write an
> ISO image? This would be a nice addition to the supplied documentation.
No, since I don't do release engineering that way, but someone else
should certainly feel free to do this. :)
- Jordan
To Unsubscribe: send mail t
> There used to be a similar snapshot server for -stable, but it seems to
> have disappeared.
Hurm? releng4.freebsd.org has been around for ages. Before that it
was called releng3.freebsd.org, hence the name change.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
They're not in ISO format, but releases from both -stable and -current
are available from releng4.freebsd.org and current.freebsd.org (hmm,
there should also be a stable.freebsd.org - I'll request that).
>From those bits, it's pretty easy to make an image with mkisofs/mkhybrid
- Jordan
To Unsubs
===> usr.bin/kdump
cc -O -pipe -march=pentiumpro -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.
bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/
kdump.c
cc -O -pipe -march=pentiumpro -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.
bin/kdump/../.. -I/usr/obj
Cool. Does this mean that any of the foocontrol programs can go away?
I've long wished that we could have some of the wireless control stuff
go directly into ifconfig rather than having to run an external
program before bringing up the interface.
- Jordan
To Unsubscribe: send mail to [EMAIL PRO
===> if_ef
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
echo "#define IPX 1" > opt_ipx.h
echo "#define INET 1" > opt_inet.h
echo "
echo "
echo "
echo "
rm -f .depend
mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev
-I@/../include -I/usr/obj/usr/src/i386/usr
> Yes, I mean when we extract and install all /etc files, is it possible
> to add then then md5 checksum to all installed config files into the
> cvs header ? (With grep -v "$FreeBSD:" of course).
Oh. No, not easily.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
From: Martin Blapp <[EMAIL PROTECTED]>
Subject: Re: Proposal to mergemaster
Date: Wed, 14 Mar 2001 09:51:28 +0100 (CET)
> If it is possible to add these checksums also in sysinstall when
> extracting the first time you install, nothing has to be done
> with commit scripts and also the first time
Hmmm, this is nice! I've wanted this option for a long time. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
From: "David O'Brien" <[EMAIL PROTECTED]>
Subject: Re: sysinstall option for softupdates
Date: Sat, 10 Mar 2001 15:43:52 -0800
> Why not add the softupdates option to newfs? Since newfs contains every
> tunefs option other than softupdates, I consider it a bug that newfs
> didn't gain that funct
From: James FitzGibbon <[EMAIL PROTECTED]>
Subject: sysinstall option for softupdates
Date: Sat, 10 Mar 2001 04:19:51 -0500
> Are there any issues/plans to let users enable softupdates from inside of
> sysinstall ?
No "plans", but it's certainly something which could be done.
> If this is a goo
I don't object - they're obvious bug fixes.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
From: John Baldwin <[EMAIL PROTECTED]>
Subject: RE: Labeling Vinum partitions in the sysinstall(8) [patch]
Date: Fri, 02 Mar 2001 09:28:31 -0800 (PST)
> Heh, I wrote http://www.FreeBSD.org/~jhb/patches/sysinstall.vinum.patch
> probably a year ago now, but because it only changes the disklabel edi
In his article at http://www.daemonnews.org/200102/armoring.html,
Markus Delves describes the usage of the SSH ftp command to do secure
file copies. I further notice that we install the sftpd server in
both -stable and -current (though we don't include any prototype
information on how to start it
> Once we have an extensible facility for mount options, you will be
> able to say:
>
> mount -t devfs devfs /home/jail/dev
> ( cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails )
> mount -u -o nonewdev /home/jail/dev
Couldn't you also do "mount -t devfs -o nonewdev devfs
> What's not clear ;-) Use -lc_r instead of -pthread.
>
> gcc -Wall -o foo foo.c -lc_r
>
> The old way was:
>
> gcc -Wall -D_THREAD_SAFE -o foo foo.c -pthread
H. And does the -pthread argument do anything anymore? If not,
why not have it default to simply linking in libc_r f
===> usr.bin/vmstat
cc -O -pipe -I/usr/src/usr.bin/vmstat/../../sys -I/usr/obj/usr/src/i386/usr/in
clude -c /usr/src/usr.bin/vmstat/vmstat.c
/usr/src/usr.bin/vmstat/vmstat.c:483: warning: `pgtok' redefined
/usr/obj/usr/src/i386/usr/include/machine/param.h:166: warning: this is the loca
tion of t
Weren't the zero-copy patches supposed to make it into -current some
time back? I recall a little grumbling over it since it made it
necessary for some other projects to sync up their own work, but
nobody seemed to object in principal and zero-copy TCP is a real
marketing point if we can actually
I've actually been seeing this for about 2 months now but only just
now got motivated enough to enable crashdumps and get some information
on what happens whenver I try to use the printer attached to my (sadly :)
-current SMP box:
IdlePTD 3682304
initial pcb at 2e70e0
panicstr: page fault
panic m
> yeah, but it can be used as many things. If invoked as "rm" sysinstall
> behaves just like the real rm, it happens to be one big binary.
This, however, is merely "post-installation behavior" - if you rebuild
and reinstall sysinstall in order to catch up with a bug fix to it,
however, then this
> Let's put sysinstall back in sbin/ then. It _used_ to live there until someo
ne
> moved it. :)
I won't argue - move away! Just have one of the CVSmeisters do it as
a repo-copy, of course.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body
> My personal opinion is that sysinstall.8 is a part of the base system
> and shouldn't be optional. If we take your suggestion, it means that
> installworld will sometimes install this manpage and sometimes it won't.
I think we should simply move the stupid man page into man8. It's a bit
weird
> The generated ld.so has bloated a bit :-) but works fine. So we could
> in principle build ld.so for every release. It's just a question of
> whether we should. I think we should. But it might be just as easy
> to copy it off the 3.3 CD every time. It's dead end stuff after all.
>
> Does t
> I've been noticing this on my daily builds for the last five days. I've just
> tried the attached patch, which works for me.
Well, that's a fix, just not the right one. :) There should be no
"dangling references" to soft updates if SOFTUPDATES is not defined.
- Jordan
To Unsubscribe: send m
sh ../../conf/newvers.sh BOOTMFS
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../dev -I../../../include
-I../../contrib/dev/acpica/Subsystem/Include
Whoops, it's just been brought to my attention that I inadvertently
committed a couple of harmless changes relating to the zero-copy stuff
when I committed a PR fix to newvers.sh. Last I checked, there were
also plans to bring the zero-copy code rather imminently into -current
but I haven't seen
Not likely to happen - people have an investment in the current scheme
and it would certainly mess with their heads if one day FreeBSD
suddenly started doing something entirely different than what it's
been doing for the last 7 years. For those who really want to track
the NetBSD way of doing thi
> No, KSE has paid developers working on it. When was the last cycle spent
> on libh?
I'm glad you brought that up - I've been trying to find more things
for you to do. I'll bring it up during the engineering staff meeting
today. ;-)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
My feeling on this is that sysinstall is (and always has been :-) at
the end of its life and adding multi-lingual capabilities to it is a
reasonable part of its retirement. The libh project is promising but
suffers from a lack of volunteers, volunteers who aren't working on
sysinstall either so I
Thanks, good compromise.
> On Tue, Dec 05, 2000 at 07:02:35PM -0800, Thomas D. Dean wrote:
> > Is it possible to go back to the old style of reporting world time in
> > Makefile? I have been collecting make time stats.
>
> I added it back, but in a way I think will not be objectionable for the
> Not sure if this the right place to complain or not, but current.freebsd.org
> does not appear to be on the net. traceroutes to both current.freebsd.org
> and usw2.freebsd.org (its alterego) fail. I did find that ftp7.de.freebsd.or
g
> has the 27 November 2000 snapshot of current on it .. was
> But I don't understand why you need the whole historical cvs repository
> when you only use it to check out the current source, which you already
> has online.
> Or am I missing something too?
You're missing something too. You can build a release with the tag
set to anything you like - modulo
> I want to start building releases on a home box since it's not doing much
> else when I'm at work. But I have a rather low bandwidth, so I was
> wondering about the CVS checkout of /usr/src that the make release does.
Well, it's fairly easy to keep a cvs repo up to date even at low
bandwidth
ve done a buildworld since
> experiencing this problem ...
>
> On Mon, 27 Nov 2000, Jordan Hubbard wrote:
>
> > I know this:
> >
> > ===> usr.bin/netstat
> > cc -O -pipe -Wall -DIPSEC -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/inc
lude
> > -c /usr/src/usr.bin/n
I know this:
===> usr.bin/netstat
cc -O -pipe -Wall -DIPSEC -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include
-c /usr/src/usr.bin/netstat/if.c
In file included from /usr/obj/usr/src/i386/usr/include/net/if_var.h:78,
from /usr/src/usr.bin/netstat/if.c:49:
/usr/obj/usr/src/i386
Kaboom. Looks like the fixes to perl unfixed the release.
--- Forwarded Message
Return-Path: [EMAIL PROTECTED]
Delivery-Date: Mon Nov 20 05:13:27 2000
Return-Path: <[EMAIL PROTECTED]>
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
by winston.osd.bsdi.com (8.11.1/
> So I looked through sysinstall source and libdisk source and guess what ! -
> libdisk doesn't know about ar? devices yet.
Committed, thanks!
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> After the crt changes the following piece of code, which worked previously,
> gives a 'host: dlopen() failed: ./module.so: Undefined symbol
> "__register_frame_info' error message (yeah, I know that it's better to check
> handle == NULL first, but it's the way some apps work).
Huh! So that's w
If you look at make release's output:
>>> make release started on Sun Nov 5 23:27:21 GMT 2000* T1
>>> Making hierarchy
>>> Installing everything..
>>> elf make world started on Mon Nov 6 00:25:54 GMT 2000 * T2
>>> Rebuilding the temporary build tree
>>> stage 1: boo
> There are many discussion aboud having NetBSD style rc.d. However, I
> think it takes for a period of time.
> Once, I wish to commit my changes to be in time for 4.2-RELEASE.
I think people were talking only about -current here anyway.
A NetBSD style rc.d is certainly not planned for -stable.
1 - 100 of 150 matches
Mail list logo
