On Aug 15, 2013, at 3:38 PM, Jakub Lach jakub_l...@mailplus.pl wrote:
Well, that took me by surprise...
That's probably the same thing 20th Century Fox's legal counsel said this
morning. ;-)
___
freebsd-hackers@freebsd.org mailing list
On Jul 11, 2013, at 7:27 AM, Julian Elischer jul...@freebsd.org wrote:
I could imagine that we could stash away a vimage stack just for this purpose.
yould set it up on boot and leave it detached until you need it.
you just need to switch the interfaces over to the new stack on panic and
Wow. A couple of questions.
1. Is it really worth messing with code as old as crunchgen(1) at all?
Seriously. What's there isn't exactly broken, and it seems like needlessly
walking into a vampire's crypt without so much as a stake or clove of garlic on
your person. Only something bad can
On May 10, 2007, at 8:20 PM, Garrett Cooper wrote:
Yipes. The name of the game is to get something working in the base
system, instead of dragging in multiple 3rd party packages, with
licensing schemes that may not be aligned with the BSD license.
SQL's great, SQL's wonderful for db use,
, at 4:14 AM, Robert Watson wrote:
It's always surprised me netcat isn't in the base system -- it's a very
useful testing tool.
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
___
freebsd-hackers@freebsd.org mailing list
http
Sounds similar to, but not as functional as, the lookupd in Mac OS X. :)
On Mar 5, 2004, at 12:45 AM, Michael Bushkov wrote:
We want you to look at this lookupd. It would be great for us to know
if
you like or not the way we made it. And we also want to know if this
project can be added to
/
- Jordan
On Mar 5, 2004, at 6:46 AM, Michael Bushkov wrote:
Hello!
What do you mean exactly by saying not as functional?
Michael Bushkov
Software Engineer,
Rostov State University
On Fri, 5 Mar 2004, Jordan K Hubbard wrote:
Sounds similar to, but not as functional as, the lookupd in Mac OS X
Why not use a UNIX domain socket as the transport and then use
credential passing to pass the credentials lookupd should use to do the
lookup?
On Mar 5, 2004, at 1:27 PM, Michael Bushkov wrote:
When you're
using current nss-modules they work as part of your program - and
geteuid functions
libc on SUSv2*. Any questions?
* References:
http://www.opengroup.org/onlinepubs/007908799/xsh/fwrite.html
http://www.opengroup.org/onlinepubs/007908799/xsh/fputs.html
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
/freebsd-hackers
To unsubscribe, send any mail to
[EMAIL PROTECTED]
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe
don't like a
change that's happened, talk to them; if they're unresponsive,
be prepared to have to find 66% of people to agree with you,
because we're going to cut them a lot of slack, once they own
the area).
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
uses as much of the UI
capabilities as are available depending on what the person doing the
install is sitting in front of.
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
___
[EMAIL PROTECTED] mailing list
http
such discussion should go to libh's mailing list (where we
can talk design there)?
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe
been dead for a good while now. I was just
kicking it to make it look like we could tear something out of this
monster.
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org
agreement?
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Given ample personal experience with this issue, all I can say is that
actions speak a lot louder than words where it's concerned. :-)
I don't mean this in the usual and offensive put up or shut up sense
either, believe it or not. It's just that I've seen literally years
worth of discussion
]
with unsubscribe freebsd-hackers in the body of the message
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
To Unsubscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
?
Sem.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body
C program?
You are missing something. Someone violated policy, and put
shell code into rc.conf, instead of leaving it a name/value
pairs.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Jordan K. Hubbard
Engineering
Kientzle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
-hackers in the body of the message
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
could get a full class B, I'd have one, and
I wouldn't be questioning *why* someone had been willing to give
it to me. 8-) 8-). It just seemed mighty strange.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Jordan K
I'll bet you wouldn't have any trouble running -stable on it. There was a problem
with MTRR support which still needs a little fixing in order to shut down properly but
that's nowhere near as bad as X not running. Fix should be in FreeBSD 4.6 as well.
- Jordan
On Thursday, May 30, 2002, at
that would be very useful.
PR: 28418, 25958
Tested by: jkh, Christopher Masto [EMAIL PROTECTED]
MFC after: 2 weeks
- Jordan
On Thursday, May 30, 2002, at 06:41PM, Darren Pilgrim wrote:
Jordan K Hubbard wrote:
I'll bet you wouldn't have any trouble running -stable
Amen!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
hey, is there gonna be a freebsd or bsd booth there tomorrow
in san jose for that linux expo thing? I may go if there is
a bsd booth...
There will be a BSDi booth at the show. Look for the usual black
monolith with the daemon on it.
- Jordan
To Unsubscribe: send mail to [EMAIL
MD has supplanted MFS, it doesn't run in conjunction with it.
Just consider MD the new name for MFS if it makes it easier.
- Jordan
On Fri 2000-07-28 (17:23), Doug Barton wrote:
Ted Sikora wrote:
A while ago several people suggested using /tmp on a ramdisk along with
softupdates.
Just a heads-up to say that the last few issues have been dealt with
and it looks like we're on target for a July 25th, 18:00 PDT (Pacific
Daylight Time) tag and (as soon as that's finished) release operation.
I'll be putting the i386 and alpha bits together throughout the night
and will be
I'm trying to automate most of the FreeBSD installation process via
sysinstall's scripting mechanism. Its showing signs of life, but keeps
barfing on the disklabel step. Below is appended my script.
Do this instead:
# the disks...
disk=da0
partition=all
bootManager=standard
What happened to the plans to move to the TurboVision library?
We're still working on it.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Someone asked at the USENIX BOF about the status of ieee1394 driver
for FreeBSD. For those who want to play with DV cameras, a set of
tools to transmit DV streasms over IP is available from
http://www.sfc.wide.ad.jp/DVTS/
It includes the ieee1394 driver presented at the last year's
And while I've got Jordan's attention -- did the last attempt at
re-writing sysinstall generate any specification documents? If nothing
else, they'd be useful content for the doc project. ]
No, this is one of the items on my TODO list which I really really really
have to get to soon or
Seeing as how it has been a link on Daemon News' front page for several
months, I find that hard to believe. :-P
Not all of us read daemon news, either. As far as I'm concerned, if
it's not part of www.freebsd.org, it doesn't exist. :-)
- Jordan
To Unsubscribe: send mail to [EMAIL
People still read .sigs? :)
On Sat, 17 Jun 2000, Bill Fumerola wrote:
On Sat, Jun 17, 2000 at 07:51:38PM -0700, John Baldwin wrote:
Seeing as how it has been a link on Daemon News' front page for several
months, I find that hard to believe. :-P
... and mentioned countless
Coleman Kane [EMAIL PROTECTED] writes:
Here's the address of the 3dfx device driver I wrote for freebsd:
http://pohl.ececs.uc.edu/~cokane/
Please test it some more and give me feedback. Could someone please email m
e
with information on submitting this to the CVS commit team?
did
So, I repeat: easily done, not acceptable to freebsd core.
Erm, hello?
I really don't understand this message at all, Ron. As far as I know,
FreeBSD core has expressed NO opinion on this issue whatsoever and
it's therefore highly unfair of you to state that we:
a) Even have a firm
Actually, I have indeed dd'd the image off since I wasn't having
any luck with the DOS utilities. :(
- Jordan
On Mon, Jun 12, 2000 at 05:32:31PM -0700, Jordan K. Hubbard wrote:
Ah, I should also have noted that undelete.exe (which I also fetched
from simtel) doesn't seem to work for me
. :(
Thanks for the suggestions so far though folks!
- Jordan
In the last episode (Jun 12), Jordan K. Hubbard said:
I'm sitting here in Seoul, Korea (which is very nice, by the way) and
I've just managed to delete all 82 images of Kyoto off the FAT-12 format
Smartcard they were on. Wh
On Sat, 3 Jun 2000, Jordan K. Hubbard wrote:
Intel has furnished us with IA-64 hardware and a porting effort is
already underway. Contact [EMAIL PROTECTED] if you would like to
help out in some way with the process.
What can those of us just out here do?
That depends on what
Is there any effort(or at least, any thought) on making an
IA-64 port of FreeBSD? It seems Intel is trying to push IA-64
to be 'the platform' for servers and workstations, and I think
FreeBSD definitely can't be left out
Intel has furnished us with IA-64 hardware and a porting effort
So you are running this right before Usenix? Thats annoying - I've already
booked a flight to San Diego on the 17th. Meeting *at* Usenix would be
good though.
Well, we can do that too since most of the engineers who will be in
this meeting will be at USENIX as well (I can't speak for the
Kirk McKusick is planning an "all BSD BOF" which runs for about
4 hours (woo!). More details will be available on the BOF board
and/or from Kirk when he's got them finalized.
- Jordan
Doug Rabson wrote:
On Thu, 1 Jun 2000, Jordan K. Hubbard wrote:
Does this mean we
Just following up on this - are there any plans to merge this work
back into the mainstream so that we can generate "localized" installation
floppies for the Japanese community in future releases? Thanks!
(Yes, I'm really catching up on email over a year old today).
- Jordan
In [EMAIL
Does this mean we won't get the SMP stuff done next week?
I'm back on the 15th (you gain 10 hours coming back) and the SMP
meeting isn't until the 16th and 17th. Of course it will. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of
YesWhose brainstorm was it to use the new convoluted bus nonsense in
FreeBSD 4.0? Clearly someone who never wrote a driver with a complex
controller with indexed memory mapped registers.Whats next, assembler drivers
If you cannot conduct yourself in a professional manner in these
mailing
Anyone remember the old Pyramid OSX 'universe' command?
Yes, I do. It was very evil. :)
The way Apollo solved this problem was much more elegant and general
purpose and one of my favorite soapbox topics: Variant symlinks.
Rather than using the "universe" concept for getting at a different
I have in my archives some code from the "person" who usually brings up
the logical name stuff (the code implements them).
AIE. OK, I think this thread will probably die in *record*
time now. I'm certainly running for the hills as we speak. :-)
- Jordan
To Unsubscribe: send
1. You can run /compat/linux/bin/bash and then you in a sort of
Linux/FreeBSD directory mix. The root directory looks just like your
FreeBSD root, but changing to a directory that is in /compat/linux, like
/bin, will put in the linux tree of this directory, but changing to a
directory that
So, the time has come to think about ripping out the doc distro from
"make release", and to teach sysinstall about these packages instead.
Actually, if the doc distro becomes a set of packages then sysinstall
doesn't need to know about them as a special case at all (which is
good, every
But seriously, I think the problem can be fixed with a more transparent
interface for Linux programs. Rather than requiring Linux libraries to be put
in /compat/linux, it would be much easier if everything could be put in
/usr/lib. Which probably means having the SAME interface as Linux.
Second, the projects page we have now, with all due respect to the
people that try to keep it reasonably organised, is a mess due to the
lack of updates. people only maintain their project pages perhaps, but
certainly not the links that lead to them.
Being able to work with more people on
Jordan said that the kernel SMP thread is ready in CURRENT FreeBSD,
but I could not find any document for the SMP kthread.
Huh? I never said any such thing. You must have misinterpreted
something else I said.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
I asked a question "Is FreeBSD working on SMP thread?" at both USENIX
and FreeBSDcon last year, you answered that it is already in the kernel,
but there is no API for userland. Maybe we misunderstund each other :-(
I answered that we had *kernel* threads but that there was no native
API yet,
GCC and Compaq's proprietary compiler. Compaq's C compiler kicked
GCC's ass in almost every metric. My questions: Is such a compiler
available for *BSD?
Not yet. Talk to your friendly Compaq sales rep and request it. :)
Why is GCC so bad at Alpha optimization when it does so well on x86?
Got a new ASUS K7V with AMD K7 700Mhz processor trying to install
FreeBSD-4.0 from the kern.flp on ftp.freebsd.org. It dumps the
registers immediately after saying
Mount the kern floppy on another FreeBSD box and do some surgery on
it along the following lines:
mount /dev/fd0 /mnt
rm
in the near future I'm going to release beta version of native,
kernel side SMB/CIFS filesytem for FreeBSD. It uses device /dev/net/nsmbX
You're a committer, just grab an available one. :-)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in
The syptoms are that the machine locks up. Hard. But there's a catch:
Erm, Brian, You *know* nobody can debug a problem like this without
hard information. It's like calling a mechanic on the phone and
saying "My car won't go. It just doesn't move at all! Tell me what's
wrong!"
Compile in
Yup.. however if you use..
" pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz "
It does not use it... It just asks questions.. Problem is (with 4.0 now
being in the stable branch, that it now asks the wrong questions..
Mea culpa - I meant to fix this and got distracted away
I'm sort of thinking in my head about adding the ability for the
md driver to handle gziped images. md's drvinit() looks like
And you can't load the kernel and the gzipped images from the boot
loader, letting the boot loader decompress the stuff and just using
the existing MD_ROOT option hook
It's also the case that there's never been anything in the
release/3.x-STABLE or release/4.x-STABLE directories except a package
link since those directories are there only for sysinstall, they're
not for humans to go to and browse. Humans looking for actual source
code for these branches should
Can I step in here for a moment? I'm not going to gzip the
ISO images. Please just live with it. End of discussion. :-)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I'm definitely for it... If I can get permission from Jordan, perhaps the
attached patches can make it into upcoming release.
I think it's a fine idea, I'm just not sure one day before release
is the time to be talking about it. It should have been raised
before now. :(
- Jordan
To
I hope I'm totally wrong and that FreeBSD will continue as it was before
And I hope that people will actually wait to SEE if they're wrong
before acting as if they really know how this is all going to turn
out, as it appears you and several other people are already doing in
extremely premature
One day we will discover that we can't use FreeBSD as freely and / or
with the same quality.
I wish you doom-sayers would actually come up with some conclusive
rationale for your fears here. Nobody has yet to come up with a
single reason as to how or why all these disaster scenarios would
the equations are quite simple
Only if you're taking powerful drugs, perhaps. There are a number of
things which are hardly "simple" here and let's go over them:
bsd/os = $$ for bsdi
freebsd = lack of bsd/os sold by bsdi -- lack of $$ for bsdi
False. If BSDI thought there was no money in
FreeBSD.org website, I quote the following, "BSDI will continue to
distribute packaged versions of FreeBSD" Is this another way of saying
that in the future that the distribution of FreeBSD may take on the Sun model
for their "free" operating system software, which you pay $$$ for the
Since WC didn't control any more than the server for the CVS tree, and
since we all have mirrors of that thanks to cvsup, if they decided to
make it unfree, then we as the FreeBSD development group would just
nominate a different central server and life would continue as before, ...
without
I am sure of the FreeBSD Projects intentions but like the previous post
things can 'turn ugly fast with the greatest intentions' The fact a
for-profit company controlling it's movements is cause for concern.
How many different ways can we say this? THE COMPANY DOES NOT CONTROL
THE FREEBSD
Corporations care only for their interests. Their stockholders will be
pissed if they act otherwise. Do you really think there's something wrong
with people who are scrutinizing this move?
No, I only feel there's something wrong with those who are both
scrutinizing it and jumping to a lot of
me..). WC/BSDI could take away the bandwidth. WC/BSDI could take away the
hosting of servers, there are a ton of people with servers and bandwidth
that would take over exactly what hub/freefall/bento/etc do right now. The
USWest machines are living proof of that.
I'd even venture to say
I guess it's a sad day for FreeBSD. I can't imagine how a company selling
it's own BSD could at the same time let another BSD free.
And I can't imagine how *anyone* could take this perspective given
any of the stuff they've read so far.
FreeBSD will remain, as I have gone to great pains to
For the FreeBSD project :
- many more supported platforms (Sparc, PowerPC, Arm ?)
- better Intel SMP ?
- new developpers ?
- increased credibility via the support network of BSDi ?
Hopefully all of those things, though just days after the merger is no
time to be making promises either. All
Will there be some kind of "business-like" presentation of all the
goodies which will comme from this merge of codebases ? (BSD-mergemania
for Dummies (TM) ?)
I really couldn't say at this stage. Hopefully? :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
For complete newbies, having "two formatting menus" seems weird too, and may
be confusing. (I'm quoting one of my housemates).
For complete newbies, you really only want to ask one question up-front:
"Do you want to use all available disk space for FreeBSD?"
If the answer is yes, you go
For the level above that (and I count myself here) a merged menu might just
be more user friendly.
And I don't disagree. The only thing which prevented me from merging
them to begin with was the fact that dialog/curses represent an
insufficiently advanced UI technology for taking adequate
The first time I installed freebsd, I picked numbers that were
a little larger than the defaults for '/' and '/var', and still
found myself needing to redo the entire installation in less
than a week because /var was too small. That was fine enough
And as you've seen by subsequent
No, that's evil for a lot of reasons which I won't go into here. :)
I don't agree... A small /, and a huge /usr, with an additional var
Not surprising since you're not even arguing with the point I was
making. :) I said that a big / was evil.
- Jordan
To Unsubscribe: send mail to [EMAIL
Bottom line: I think it should stay the way it is now. :-)
And since I agree, I suspect it will. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
If you got REAL LIFE NUMBERS, based on REAL LIFE PERFORMANCE, then we
can talk. Let's see how it does Quake, then we can talk.
Alpha does quake? :-)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
The situation here, I hate to say, is that you were simply very lucky
in having a software memory tester show you anything at all.
If your experience had been more typical, you would have run memtest86
and it would have declared your memory to be free of errors. Then
you'd have gone right on
Which leads to my potentially ignorant question: Where is FreeBSD
w/regards to running on the Itanium (or other 64bit chips)?
Waiting for somebody at Intel to give us either hardware or simulator
time. Without either of those things, "working on" Itanium support
is a pretty pointless
It's something we've been considering. :)
Hi,
I was thinking (I know, I know, I shouldn't do that, it's bad for me
;)...
Since we now have 3000+ ports, what are the chances of getting a special
"FreeBSD Ports Distfiles" CD-ROM subscription set, which would just
contain the distfiles?
Since everyone seems to be jumping up and down on this, I thought I'd
just chime in with my two cents on the matter.
I saw the Lucent folks behind this when they first brought a demo of
Eclipse to FreeBSDCon '99 and, frankly, I was just pleased that they
were willing to show up as exhibitors and
Just saw it in the news,
http://abcnews.go.com/sections/tech/DailyNews/yahoo000207.html
Does anyone know the detail?
I just exchanged email with David Filo this morning about this and it
appears to have been a DoS attack using the usual array of
stream/synflood tools. It also primarily
I'm planning to work on enhancing pkg_install tools following
after NetBSD's effort. Seems they've been making some remarkable
improvements over FreeBSD's original work since 1997. For example:
As the author of these tools, I would welcome those sorts of enhancements.
- Jordan
To
Ugh, I should have brought this up before the code freeze but...
I think that pretty much says it all, and reflects my own opinion
on the matter.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Hi all,
Our primary mail server, using the special type of evil ESP abilities
which all critical hardware items possess, took advantage of everyone
(including our postmaster) being away at LinuxWorld in New York to
exhibit the "F" in "MTBF" with respect to hard drive specifications.
We have
script. The script basically translates tar commands to cpio commands,
which makes sense, since the cpio binary is a LOT smaller than tar. But
there's no cpio on the fixit floppy...
And there's no ifconfig on the floppy either, so why even bother with
telnet/ftp/mount_nfs?
You need to
There's still space on there; what else could we put there?
A copy of nethack to play while you're waiting for that fsck?
[ducks]
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I would *strongly* suggest to put rsh/rlogin + tar onto the root
filesystem. I allways found these commands to be *extremely* useful in
single user mode with all other partitions unmounted (e.g. when
reorganizing the structure of my partitions/disks etc.)
How about it?
I doubt it. :-)
-
1)Are BSD drivers not really documented?(I fear that I may not end up
re-inventing the wheel)
I assume that by "drivers" you mean "device drivers" in this context,
e.g. our code for supporting various network interface cards, SCSI
controllers, etc.
They are documented in the sense that there
Why was it removed?
If there are no good reasons, please could somebody put back rsh onto the
floppy! Currently I don't see how to do cloning easily without rsh?
The fixit floppy is very full and its days as a truly useful tool are
sort of numbered.
By the way: How about putting the boot +
Have we had an opportunity to have the Walnut Creek (or other) legal staff
review the actual rules for gotchas?
No, this is something I hope to sit down with our corporate counsel
over very shortly. It's an annoying drive to San Jose from here, but
I'm prepared to make that sacrifice. :)
-
This is very interesting data and I was just wondering about the
actual state of functionality in our AIO code just the other day,
oddly enough. Does anyone have a PR# for the mentioned patches?
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the
Though doug didn't say so, I think the equivalent code in freeBSD is
if ((fd = open("/dev/io",O_RDWR,0)) == -1) {
ERROR...
}
Correct, and I find it a little embarassing. I mean god, what a hack! :-)
There has just *got* to be a better way of granting (and checking for)
this
I think the solution here is to change the release mechanism slightly.
I believe we made a huge mistake splitting of the 4.x tree from 3.x
so early.
I was going to make a point about this, but thank you for making it
for me. :-)
My point was going to be that it was clearly not
I've been with BSD a long time--from back when my email address was
decvax!randvax!edhall. I want it to succeed, for reasons that are more
emotional than rational; my nightmare was having to say that my project
(1) worked on Solaris, (2) worked on Linux, but (3) broke FreeBSD.
And I hope
In otherwords, we should branch with the 4.1 release rather then the
4.0 release.
Sounds a lot like 3.x to me. We didn't branch at 3.0 either, we
branched one release afterwards and only after people threatened to
mutiny if we didn't since the usual pattern up to that point had been
1 - 100 of 222 matches
Mail list logo
