Hi. I've finally installed FreeBSD 4.0 and to tell you the truth, I'm
not very impressed. I was expecting some bugs but not like that...
I don't see a problem with FreeBSD 4.0 so much as a problem with
someone jumping beyond their abilities. :)
Please, go back to 3.2-STABLE. 4.0-CURRENT is
Luckycasino.com now blocked by spam filters. Sorry, as always, for
the interruption.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I was wondering what to attribute this better performance to. Could
this be due to the new network driver / newbus integration?
The CVS metadata was removed, reducing the inode count per port significantly.
This results in faster extraction time and hence "faster" downloads, assuming
that
It sounds like ppp is simply exiting immediately. I'll turn debugging
on and give it a shot myself; perhaps somebody broke something.
- Jordan
I should have also stated that I tried all the other "F" keys also.
The only vty that is available/active is vty1 for debugging. Every other
F-key
Mkisofs is good for creating an ISO 9660 file systems. Wormcontrol and
dd are a good combination for writing them.
This would be true if the worm driver wasn't actually dead. You
should at least check on these things before publically recommending
obsolete mechanisms. :)
In the world of CAM
All of this would be true if your personal definition of "emulator"
were the prevailing one, but that is unfortunately just not the
case. :)
When the average computing public thinks of an "emulator", they think
of something like MAME or the SNES emulator. Even the more
compute-minded folks tend
So can we have the manufacture and model of your cd-recorder ? 8)
Yes, it's a "Smart and Friendly" (gah!) "Rocket Recorder" - it does
8X CDR, 6X CDRW and 24X CD. I like it. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
Others have pretty much already listed my preferences:
"Linux compatibility"
"Linux ABI support"
"Linux binary compatibility"
or any of the other obvious permutations thereof...
- Jordan
Okay, I will bite.
What would you call the linux emulator to convey the proper
meaning to the suits
In my case, you should always assume SCSI unless expressly indicated
otherwise. I hate ATAPI devices, no insult to Soren's fine work
intended. :)
- Jordan
I take it that the absence of the interface means your cd-recoder uses scsi.
Tnks A Lot!
So can we have the manufacture and
I agree with this as well.
"Linux compatibility"
"Linux ABI support"
"Linux binary compatibility"
The suggested "linux mode", has a nice non-technical simple ring to it.
If we called it this, the non-educated might not come away with the wrong
idea. Management(tm) may not understand
I gather the reason for using the X trick *and* the quotes is because there
might be some whitespace in there, too.
Actually, that's mostly just historical legacy. When the quotes, it's
safe even if the expansion is empty or contains whitespace. I got
kinda annoyed with this last night and
For the immediate future, it looks like it will -- it seems as though
we don't have the man power to make the necessary changes to sysinstall
to support "installing the docs as packages", so I'm going to fix up
src/release/Makefile as necessary to cope with the new directory structure.
I
As of a few days ago, ppp(8) supports the -nat flag (as well as
the -alias flag for backwards compatibility), however, it's not
clear that we really want to go the whole hog and change the
library name interface too.
I've been on both sides of this issue, to be sure, but I have to say
But it's not going into the tree, no. I think Kevin's point and the
experiences we had with Hasbro should already have convinced people of
that much.
I think people are being almost clinically paranoid here. Hasbro and
folks got upset over TRADEMARK infringement, e.g. from using a name
The issue with boggle and tetris wasn't the name, it was "look and feel".
No, it was the name. Believe me, I read the letters we got from their
lawyers. :)
Unless we produce a movie with the name "Matrix" somewhere in it, I
doubt we're going to be in the same boat. Hasbro objected to our
I seriously doubt they'll win this lawsuit. You can sue someone for
anything and everything, including having a hair color which
^ in the States
Sorry, I've lived in Europe, you can't pull that one on me. :)
In Germany, for example, it's possible to sue someone
I'm noticing some new output. What does it mean and is it going
to stay there? :-)
- Jordan
ahc0: Adaptec aic7850 SCSI adapter irq 16 at device 4.0 on pci2
ahc0: aic7850 SBLKCTL = 0x0
SSTAT0 = 0x0
SFUNCT = 0x0
Single Channel A, SCSI Id=7, 3/255 SCBs
ahc0: Host Adapter Bios disabled. Using
This worked just fine with -current as of a week ago, and I've changed
nothing else (the hardware is the exact same). Now I get the
following when I attempt to mpegify one of my audio CDs with "ripit"
dscheck: b_bcount 512 is not on a sector boundary (ssize 2048)
dscheck: b_bcount 512 is not on
This could be another si_bsize casualty.
Try this patch
Nope, it still occurs. You're definitely in the right ballpark
though since I added some printfs and it's this check:
} else if (ssp-dss_secshift != -1) {
if (bp-b_bcount (ssp-dss_secsize - 1))
ahc0:0:4:0): cddone: got error 0x16 back
- Jordan
What is the name of the port you're using ?
In message 409.935917817@localhost, "Jordan K. Hubbard" writes:
This could be another si_bsize casualty.
Try this patch
Nope, it still occurs. You're definitely in the ri
Thats not where it dies :)..
Be more specific. Just saying "it dies" does not help anyone here.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
The only thing I don't like about this is that it introduces a point of
incompatibility between FreeBSD and other unices, and I'm not sure the
I think there was a lot of this sort of "compatibility" lost when BSD
introduced its whole hier(7) enforced subtree scheme, and about the
only
I just forgot to commit a header file. Sorry about that. I test all
of my code, unlike you Poul.
Insert nasty message about how people shouldn't post idiotic comments.
Ummm. I don't see this going in positive directions at all and I'd
appreciate it highly if everyone involved
Mutual respect doesn't exist when one of the parties refuses to listen
to *anyone's* advise, ever.
I am getting wholely sick and tired of having to clean up after Poul's
commit bugs. I've spent at least a hundred hours and probably more in
the last month fixing things
I'm just suggesting here that it would be nice if the authors of
this code would make it _equally functional_ to what was removed.
It's not nice to remove functionality unconditionally and then
provide no replacement at all...
That work is underway, and something to understand about -current
If that was only true. Or should I ask why didn't CAM from -3.3 get
reverted to the old scsi code before 3.3 was released. I have seen
no less than 2, and perhaps 3 people try to get cards that did work
under pre-CAM 3.x working under post-CAM 3.x. I know this is a slippery
slope, but it
Anyway, all good to know. There are almost certainly more perl
speakers than awk speakers these days, so it probably makes sense
to do these things in perl rather than awk.
I think that's sort of in the grey area. There are also many Hardened
Traditionalists(tm) like myself who don't know
I've got a box running yesterday's -current and it can't compile
or install things like XFree86 or ImageMagik due to syntax errors
in this file. Investigating further, I find that the trouble begins
around line 127, where we see:
#if defined(_P1003_1B_VISIBLE) || defined(KERNEL)
See the mails from October 15th, esp. the ones from Marcel Moolenaar
and Sheldon Hearn.
I did, but they don't fix the XFree86 3.3.5 build problem.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
From current.freebsd.org's release build log:
linking BOOTMFS
if_ed_isa.o: In function `ed_isa_probe':
if_ed_isa.o(.text+0x45): undefined reference to `ed_probe_WD80x3'
if_ed_isa.o(.text+0x54): undefined reference to `ed_release_resources'
if_ed_isa.o(.text+0x5a): undefined reference to
Suppose I need to install on a bunch of machines. What I'd do, is
install once, get all the pieces/ports/customizations right and then
make a tarball of the system. To install the next machine, I'd use
sysinstall to partition and label the new machine and then just nfs
mount the machine
I don't think any of the authors would mind if it went into /usr/games,
I certainly wouldn't. It would be an old game returning home to the
Berkeley world, and I also used to play it a lot on the HP-2000.
The 'ol HP 2000 access, now that brings back memories... Did you know
I once wrote
I guess the real question is: /usr/games or /usr/ports? I don't care
which, but I would personally prefer /usr/games because it really is
an old-time berkeley program.
Perhaps we should ask Kirk... ;)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
No. Make it a port. Policy, remember? 8)
I guess the anti-bloatists would have a point on this one...
I would not object to a port. It certainly eliminates the
bike shed arguments over it.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
I don't want to get nasty here, but was it _really_ necessary to forward
the entire, original, humungous mail to add a few lines of commentary to
Sorry, but as I already commented to another person, I actually only
read the first two paragraphs of Matt's message before replying and
didn't even
Hmmm, I can understand the build/install portion but will it boot
since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE.
Are you still running current, Vince? I thought we established over a
year a go that -current was *not* for you since you don't take the
requisite time
I think a lot of the people who run older versions of -current, and
upgrade sporadically, have done so because there are particular things
missing out of -STABLE that they need (or want).
Which is a fair point, and hopefully we'll be branching 4.0 sooner
this time so the wait is not so long.
I don't agree with any of this, I'm afraid. The specific model we have
today was evolved with reasonable purpose.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Months. :)
Any idea of when 4.0-RELEASE will be out, in terms of months or years?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body
sh ../../conf/newvers.sh ZIPPY
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf
I am quite well aware of the mailing list etiquette. I read through many of
them frequently.
Then you're aware that cross posts are also strongly frowned upon,
especially on both -current and -hackers. Only one mailing list at a
time please, no cross posts.
- Jordan
To Unsubscribe: send
if they used an MII transceiver, then it should work okay, but if
not you could be in for trouble. I wish I didn't have to say that,
but I just don't have the hardware to test with.
You know what I tell people who use that excuse... ;)
- Jordan
To Unsubscribe: send mail to [EMAIL
Yes, I'm sure you all never expected it, but we're actually on the
road for a 4.0 release in Q1 2000 (hopefully early January) and before
we can realistically begin that process, we have to stop throwing
kitchen sinks into -current and start making it work again instead. :-)
To that end, we'll
The last of the new millennium celebrations are still more than a year away.
Well, if you want to get technical, some people have already started early. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Also useful would be a review status of the freebsd tree. So (approved)
people can "sign off" on a particular file or directory as having been
reviewed as of a certain date, and we can work in a coordinated fashion.
Well, IMHO what you guys most significantly need is a "tinderbox"
style page
I'm certainly willing to do what I can to help, although I have
to admit that I may need a bit of help identifying what I can do. ;-)
That's Mark's job - he's the security leader. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
This means nothing out of context. I hope we don't go on a witch hunt.
No, but there is some merit to simply replacing these so that they
don't show up on our radar later. I don't see any reason, for
example, why anyone should still be using gets() and our
implementation even gets whiney
It seems that sysinstall will completely refuse to install unless we
have made a swap partition. Then for some reason it didn't allow
us the option of partitioning our second disk after "committing".
Why force swap? I swear we were going to configure it after the
install. :)
Hmmm. I'm
I'm still here for another hour, dammit. :-)
I'm also going to be reachable for most of that week since Holland
does have Internet connections now, you know. They got it along with
electric lighting and running water at least several years ago. :)
- Jordan
In message [EMAIL PROTECTED], Kevin
You need to track -current. I fixed this on:
revision 1.155
date: 2000/02/24 08:28:06; author: jkh; state: Exp; lines: +2 -2
Do USA_RESIDENT properly.
Hi!
Please commit it:
--- release/sysinstall/config.c.old Tue Feb 29 23:56:47 2000
+++ release/sysinstall/config.c Tue
I have upgraded a machine to the latest -current snapshot (it
was running a -current from the end of January before). Every-
thing went fine, except for one thing: ssh didn't work anymore.
It used to work fine before.
You really need to read the -current mailing list if you're going to
run
I keep asking myself this question; a default sysinstall package would
give us the same end result.
I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with
breakage.
Would you guys quit spreading FUD and start actually giving us some
DETAILS on this alleged breakage?
Good god, I am saying that the files to merger dont existthere is nothing
to merge...
You need to be reading -current or stop running it. The issue with
/etc/ssh/sshd_config has been discussed to death.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
You know people, it's quite sad that those with knowledge simply refuse
to answer simple questions without "RTFM" attitudes and indirect (and
What you and others don't seem to understand is that there are also
"minimum responsibilities" that have been established for users of our
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-2307-CURRENT
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307-CURRENT
With ISO images available from:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-2307-CURRENT/
.. just as soon as they finish uploading
I tried an FTP SNAP install this morning, and all the crypto libs from
current were unavailable. I switched over to the debug console, but there
was no additional info. The files seem to be on the ftp site just fine.
Is this a known issue ?
Please try again - I *just* fixed this problem
There were a couple of sysinstall related bogons, one related to
variable toggling in rc.conf and another related to the crypto
distribution (it was still looking in des/). Both of these have been
fixed and rolled into the updated boot floppies as well as the ISO
images, which are still
For just ftp (wizard) or on current (usw2) as well?
These snapshots are only going up on ftp, sorry for the confusion.
The stuff on current is just the daily snapshot stuff and not entirely
equivalent to the URLs I specifically gave out.
- Jordan
To Unsubscribe: send mail to [EMAIL
Urk! Geeze, how did I not notice that. Must have been the hour.
I'm fixing this now, sorry guys.
- Jordan
On Wed, 8 Mar 2000, Jordan K. Hubbard wrote:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-2307-CURRENT
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307
Good point, I forgot the link. Fixed!
- Jordan
Says, it can't chdir into the 4.0-2307-CURRENT directory.
It does work from current.FreeBSD.org. Looking on ftp.freebsd.org
I do not see a link under /pub/FreeBSD/releases/i386/ ? that maybe
the missing link ?
--
Regards, Ulf.
The other possibility would be to fix the wine port so it calls
dllockinit() to set up locking. I don't know for sure how hard that
would be, but it's probably a feasible solution.
To be honest, I'd be the most comfortable with this solution but also
trust John's skills with the linker
, 2 Mar 2000, Jordan K. Hubbard wrote:
Date: Thu, 02 Mar 2000 03:12:09 -0800
From: "Jordan K. Hubbard" [EMAIL PROTECTED]
To: Dmitry Valdov [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: sysinstall mistake
You need to track -current
OK!
You have my OK to change the option, but you'll need Jordans
OK to commit it.
Poul-Henning
In message [EMAIL PROTECTED], Warner Losh writes:
Given that OpenBSD had the -e flag to fdisk first, and that it means
edit there and that disklabel -e means edit, I'd like to apply the
Hi:
I did an install of 4.0-RC3 last night and found the following:
1:Unable to transfer the local distribution from
ftp://current.freebsd.org/pub/FreeBSD/Snapshots/i386
Because it's not there. I listed the URLs I listed *very
specifically* and that is the ONLY location you can
I got the install floppies from the ftp directory that you listed. When the
install came to a point where it asked for the ftp site to get the
distribution, it listed a "primary" site (ftp.freebsd.org, I believe) and
This should work now - it just needed some symlinks to be created.
-
I installed a -current snap from internat.freebsd.org that was built
with crypto source from internat. I answered yes when sysinstall asked
me if I want the crypto stuff, but then found that it marked me as an
USA_RESIDENT=YES in /etc/make.conf and it also asked me later if I
want to install
IMO (and I suggested this the other day), we should make the crypto
collection mandatory, and have sysinstall ask a question about whether to
point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is
I'm still waiting for your diffs which do this. :)
- Jordan
To Unsubscribe:
That was fixed days ago - get a more recent snap. :)
Hi.
I'm testing 2307-SNAP and I found that USA_RESIDENT is set to YES
even if I installed from CD-ROMs with crypto distribution compiled
from international crypto sources.
How about adding something like following patch to
Well yeah, that's fun to say, but my days have been literally completely
full with getting other things ready for 4.0.
And you think mine haven't been? :) My point is simply that I'm going
to need a lot more than rough suggestions at this point if people want
to help. I don't have time to go
I think I'm just going to go to the 3.4 bits; I don't have a definitive
XFree86 distribution for 4.0 and I don't think I'm going to get one in
time to make a difference.
- Jordan
It looks like the X11 associated with the snapshots on current.freebsd.org
is still broken:
I was actually talking about FreeBSD 4.0, not XFree86 4.0. :)
On Tue, 14 Mar 2000, Jordan K. Hubbard wrote:
I think I'm just going to go to the 3.4 bits; I don't have a definitive
XFree86 distribution for 4.0 and I don't think I'm going to get one in
time to make a difference
In my 4.0 cvsupped from 3/20 /etc/rc.firewall says this:
# Suck in the configuration variables.
if [ -r /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
elif [ -r /etc/rc.conf ]; then
. /etc/rc.conf
fi
which would be fine, but
Good idea, terrible name. Can't you guys some up with something better? :)
On Tue, Mar 21, 2000 at 04:32:35PM -0800, Doug White wrote:
I would be in favor of renaming the boot.flp to something obviously
different, like 288boot.flp, to untrain us 2.x heads that got used to the
Great
kern-144.flp
root-144.flp
boot-288.flp
Winner! Much better than my personal favorite of bigbooty.flp. :-)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hmph, it seems sysinstall (and thus make release) is broken in -current:
I don't know what version of sysinstall you're using, but it builds just
fine for me under -current. I saw some other kvetching about kget
being broken and just tried building it last night. Observe:
root@zippy- make
Urk, sorry guys, I've been cvsupping the repo faithfully but evidently not
cvs updating my tree as faithfully. :-)
I'll find and fix it.
- Jordan
On 24-Mar-00 Jordan K. Hubbard wrote:
Hmph, it seems sysinstall (and thus make release) is broken in -current:
I don't know what version
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../../../include -D_KERNEL -include opt_global.h -elf
-mno-fp-regs -Wa,-mev56 ../../alpha/alpha/clock.c
I did and created malloc.conf as documented there. And things were
fine after that. Wouldn't it be better if the build process created
a default /etc/malloc.conf ?
It's purely an optional file; one doesn't need to be installed by
default in order for things to behave as expected. Consider it
Speaking of which, why is /home/ncvs on beast not pointing to
the current CVS repository? I got bit by the same error after
doing (what I thought) was a correct `cvs update' on beast.
Sorry, "my bad"; the alpha releases were falling over on some sort of
NFS bogon (and cvs checkouts using
You moved tcpdump into the crypto distribution with revision 1.25 of
its Makefile. I am still scratching my head and trying to figure out
why, however, since most people expect tcpdump to be in the bin
distribution where it's always been. Did you have some really good
reason for this which
Just out of curiosity, why is there an "AGAIN" in the subject line,
since this is the first email I've gotten on the subject?
Sorry, the first queries about this probably didn't go directly to you
since it was only yesterday that I actually bothered to go track down
the specific commit which
Sounds perfectly reasonable to me. I'd be happy if someone else wants
to look at this, or I can look at it on the 10th when I get back from
Australia. This would mean there's a src/secure/usr.sbin/tcpdump that
builds with crypto and src/usr.sbin/tcpdump that builds without?
Correct! Both
There *were* several problems with the .ifdefs in the tcpdump makefile
which I fixed prior to 4.0, and I thought I had fixed the problem of
tcpdump in the bin distribution being linked against libcrypto (this was
broken in the initial 4.0 Release but fixed when jkh rereleased it). If I
It is down right now. It will be back soon. Thanks for asking
so loudly.
Why is this machine (current.freebsd.org) always rejecting guest privileges
and why won't ANYBODY answer the question?
Thanks in advance,
Tom Veldhouse
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
For the latest 4.0-STABLE snapshots:
ftp://releng4.freebsd.org/pub/FreeBSD
For the latest 5.0-CURRENT snapshots:
ftp://current.freebsd.org/pub/FreeBSD
I don't run mirrors of these machines so please don't ask where you
can get the bits closer/faster/cheaper/etc. If you want to mirror
Try again, the DNS wasn't updated yet.
"Jordan K. Hubbard" wrote:
For the latest 4.0-STABLE snapshots:
ftp://releng4.freebsd.org/pub/FreeBSD
Unfortunately does not work ...
root[amb]@pinta# nslookup releng4.freebsd.org. who.cdrom.com
Server: who.cdrom.co
We argue about this a lot. Nobody has, as yet, ever done the work to
make "bindist" a meta-package which depends (perhaps selectively) on
sub-packages like groff, sendmail, gcc, et al. to achieve the required
state of "bundling by default but not by requirement" in FreeBSD.
This is despite the
I have a machine which isn't doing much right now, so I have decided
to set it up as an automatic "FreeBSD Build checker".
Welcome to the current.freebsd.org game. :)
Once per day the machine cvsups, checks out a virgin source tree,
tries to build GENERIC, GENERIC98, LINT and world. If
But does this also check the kernels ? It was my understanding that
it only did world/release ?
It only does the world/release (and it's the chrooted make release
"world build" which is reported on, not the host system's BTW) but
could easily add a kernel build just for the benefit of the
IMHO, it's not such a bad idea. freebsd-current _is_ the place to
report problems with -current, why can't the report be produced by a
daemon?
Becuase it's chunky and regular enough that I don't see why we
also can't just create a new notification service for it.
Think a bit bigger-picture
Does this mean that the burdon of proof of patent problems shifts from
those doing the software to those who think there's a problem?
That's the way things generally work, yes. :)
does that mean things can go ahead with the integration of the
firewire drivers that are out there? It sounds
cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/
src/usr.bin/netstat/ipx.c
cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/
src/usr.bin/netstat/route.c
/usr/src/usr.bin/netstat/route.c: In function `p_tree':
In general I agree with the concept but I think .0 releases have to
have a bit more flexibility, and that 4.0 in particular (due to the
rules change made for the BSDI merger) has to be even more flexible.
And this is something I can render an opinion on right away: I
Really, then you have a short memory. Why don't we ask Jordan for a
clarification.
How about if you let me review the patches in question and I'll render
a decision.
If you, Matt, could put the SMP and linux stuff into -current first
and then give me a day or so to check it out, I'll
Gee, is that perhaps because FreeBSD keeps breaking the ABI to modules
so every vendor that has ever tried to use them has been bitten by the
fact that they have to maintain N version for each branch of FreeBSD???
Can you list some specific examples? I'm not trying to be a wise-ass,
I'm
So you guys (core) choose -- do you want 4.x to reap the benefits of
further SMP development or not?
I've read all the feedback on this thread and now feel that it would
be worthwhile to simply bring the SMP changes in on Wednesday. As others
have pointed out, we don't have enough 3rd
Are there any 3rd party NIC klds yet?
NTMK.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
And if I put up, will you (the organization) use it? It's certainly too much
work to prove the obvious. I don't have to convince myself of anything.
The only value accrues if it gets used.
Erm, haven't we been here with you before? I can even replay the
script from heart:
1. Richard comes
wishlist
Not sure if this is a silly question or not, but could the kernel somehow
view a specific dir on a ext2fs disk as the freebsd root and boot a
freebsd system from it? Also being able to access the stuff below the
I think there's a more general need to have a loader variable which
What sort of fallback behaviour would you want in case of error here?
Just let chroot() either succeed or fail. It's own "fallback behavior"
in such a case should prove adequate. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
1 - 100 of 404 matches
Mail list logo
