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 Jul 11, 2013, at 7:27 AM, Julian Elischer 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 put
> them into
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, b
> website (http://www.freebsd.org/~green/FreeBSD-68k.txt). In about two
> weeks I'll have a spare Macintosh IIsi and would like to have a run at
> FreeBSD on it. So, to the point, where can I get it? :)
I'd say that's a question for Grant Stockly, the person mentioned in
green's web-cited messag
> On Mon, 19 Jul 1999, Jordan K. Hubbard wrote:
>
> > > website (http://www.freebsd.org/~green/FreeBSD-68k.txt). In about two
> > > weeks I'll have a spare Macintosh IIsi and would like to have a run at
> > > FreeBSD on it. So, to the point, where can
> FreeBSD can wait till unified-ipv6 is made available, since:
> - IPv6 is not that urgent task and
> - it will be messy if FreeBSD integrates KAME first,
> then switch to unified-ipv6.
Both of these remain true. I certainly see and unders
> I just wish that it was the other way around. I'd actually run
> NT if I could get it in a VMWare compartment under FreeBSD.
You would do well to pass these sentiments on to vmware; they're
currently counting noses in FreeBSD-land to see if it makes
market sense. All the techs there appear to
> the parts that they need. However right after 3.2-R came out there was a
> flurry of -questions mail about broken pkg dependencies because sysinstall
> wasn't properly registering the X install. If the port depending on the
Just to clear up a misconception; this isn't actually a sysinstall
probl
> But we can install from a single downloaded boot floppy, over the
> Internet, which is better.
1. Irrelevant, since most people who want to try BSD/OS out probably
aren't concerned about how FreeBSD installs itself; they're
simply different products.
2. Incorrect, since we don't install o
> * it's part of the dependancy chain now for a lot of packages,
>
> You are entitled to you opinion, but please don't misrepresent the
> facts. They are not part of the dependency chain for any *packages*.
Sorry if the english I used was ambiguous - I should have said "to
install packages usi
We got off onto a big tangent about switches and vlans and stuff and I
learned a number of interesting things, don't get me wrong, but we
still haven't established any consensus on the trade-offs of enabling
bpf. This wasn't meant to be a hypothetical discussion, I'm truly
trying to measure the tr
> It will let us use a dhcp client in the install programs, this is of
> tremendous use to many people as DHCP starts to become much more
> popular. I cannot net install a machine at home since that is on a
> DHCP cable modem service.
Well, just to clarify this, if you're installing a 4.0 snapsho
> There's no good reason to not have bpf in at least the boot disk kernel.
It already is. That's not the question under discussion here - we're
talking about how to make things work in the post-installation boot
scenario.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubs
> I thought we decided that the networking gurus we're going to make it
> possible to send out broadcast packets on an unconfigured interface so
> that DHCP would work, so that bpf wasn't required.
I believe we decided that this would be the preferred method, yes. I
don't think, however, that we
> There are no security levels > 3. I'd be happy with > 0. This is
> consistant with the meaning of "raw devices".
Would you be willing to make this change?
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
http://features.linuxtoday.com/stories/8191.html
A story on upcoming plans for the Linux 2.4 kernel. Since they're
going after a lot of the same performance goals we are, it's worth a
read.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the bo
> I am pro.
>
> It takes a root compromise to use it anyway, and its usefulness
> for DHCP and rarpd is too compelling.
>
> Perhaps the comments in the GENERIC file could be updated.
Well, given that I've gotten primarily positive support for this I
guess it's time to do it. Warner, do you want
> Mm-hmm. ld -Bshareable as opposed to ar rc.
This demonstrates a superficial understanding of the process, nothing
more.
> I just think we're not seeing eye to eye.
I'd be more inclined to say that John simply understands this where
you don't. Go study up, then come back and engage the poor gu
> I have a parallel port Iomega Zip Drive. I have installed 3.2-RELEASE and
> although the vpo0 is detected it does not see da0, and when I try "mount -t
I'm not surprised, since da0 would be a SCSI device.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-h
Sorry, I wasn't aware that the parallel port SCSI stuff had been
CAM'd yet.
- Jordan
> In message <11366.934157...@localhost> "Jordan K. Hubbard" writes:
> : > I have a parallel port Iomega Zip Drive. I have installed 3.2-RELEASE an
d
> : > although the
The use of /stand/sysinstall to do a live upgrade has always been
discouraged, though it's not outright disallowed since I believe in
every man's right to blow his feet off if he really wants to.
Nonetheless, for the expected installation experience one is
encouraged to boot the desired OS release
> So Solaris does the right thing by understanding underscore I guess.
> Since it is not forbidden to use it in hostnames.
It does not do the right thing and it is indeed forbidden. :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of
It was given about a year ago and is now out of date. XiG promised
to update their web site, but evidently this just hasn't happened
yet.
- Jordan
> on Xinside site (www.xig.com) it says...
>
> FreeBSD 3.x is not yet supported on the advice of some members of the FreeBSD
> core team.
>
> Why w
> On Mon, 23 Aug 1999 11:28:20 -0400
> Dennis wrote:
>
> > I heard a rumor that freebsd runs on a sparc, but I dont see any backing
> > for that. Is it in the works?
>
> FreeBSD does not run on the SPARC. I think they've been talking about it
> for ... what, 5 years now... but it never mate
> (I believe it got bounced due to my mistake in To: line.
> sorry if you got it multiple times)
>
> Hello, if this mailing list is inappropriate please tell me so.
>
> I contacted radisson hotels for FreeBSDCon reservation with
> special discount, to get the followi
Heh, I didn't prod him *personally* - we're not quite in the same
social circles as that (yet ;).
- Jordan
> "Jordan K. Hubbard" wrote:
> >
> > I
> > prodded Scott McNealy a couple of weeks ago about this, and he
> > responded...
>
> That&
> marder-1:/usr/marko{57}% ./a.out
> short == 2
> int == 4
> long == 4
> long long == 8
> marder-1:/usr/marko{57}%
But on the Alpha:
j...@beast-> ./foo
short == 2
int == 4
long == 8
long long == 8
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" i
> Does it make sense to make src/crypto/sys for kernel code?
> (for IPsec we need crypto code *in kernel*).
I'd say it makes a lot of sense.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
se. :)
- Jordan
> In message <10335.936082...@localhost>, "Jordan K. Hubbard" writes:
> >>Does it make sense to make src/crypto/sys for kernel code?
> >>(for IPsec we need crypto code *in kernel*).
> >
> >I'd say it makes a lot of sense
> In message <28661.936093...@critter.freebsd.dk> Poul-Henning Kamp writes:
> : >Hmph. I guess common sense wins over ITAR in this case. :)
> :
> : That's certainly an improvement in that particular battle :-)
>
> Speaking of ITAR, has anybody actually every approached FreeBSD to say
> what we'r
> Where sun are involved, I wouldn't get your hopes up until you actually
> see source or something. And I wouldn't exactly call them quick,
> either.
This is wise counsel.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
> CPU: Pentium/P54C (132.73-MHz 586-class CPU)
> Origin = "GenuineIntel" Id = 0x52c Stepping=12
> Features=0x1bf
>
> Seems more precise and informative. For 386/486 based hardware
> someone could adapt one of the numerous CPU speed detection routines
> out there.
Indeed. In fact, if someon
> Nice Idea however wrong operating system. The losers should
> have done it for FreeBSD instead of linux.
1. Unconstructive (losers?)
2. Irrelevant (what gets done for Linux by XFree86 et all gets to FreeBSD
pretty quickly)
3. Needlessly cross-posted (watch your cc lines, loser! :).
- Jor
It can go in after the freeze - it's a bit late to be asking now. :)
> On Wed, 15 Sep 1999, Dan Nelson wrote:
>
> > RCS file: /home/ncvs/src/bin/dd/dd.c,v
> >
> > revision 1.17
> > date: 1999/06/19 19:49:32; author: green; state: Exp; lines: +25 -21
> After a week of struggle, I am pleased very much to announce
> that Luigi's sound driver now has a midi interface and a sequencer!
Excellent! I'm very happy to hear this. Any idea when you guys will
be able to support the on-board MIDI interfaces featured on many sound
cards? Once that day co
> This is getting out of hand. It's pretty clear none of us understand
> what's up behind the scenes on this, because I'd swear the thing could
> have been written from scratch in less time than this port is going to
> take.
I can't really give you specifics, but let's just say that we're
curre
> Fair enough. Can you throw us some kind of a bone as to why the delivery
> date keeps leaping ahead, a year at a time? When I put my deposit down,
> it was due in November of 1998. A cursory search through mail shows a
Deposit? Didn't you simply register your card with us for billing
when it
As most of you attending USENIX (http://www.usenix.org/events/usenix99)
this year in Monterey, CA already know, the "terminal room", a cluster
of 40 networked PCs for public use, will be running FreeBSD this year.
A total of 12 volunteers is needed to staff this terminal room and
I think about 7 o
> Jordan, what do you think ?
I don't think it's worth it for just xanim. Give me more incentive
than this. :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
> I now have the driver for OPL3 ready to go!
Great news!
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
> I have a fresh installation of FreeBSD 3.2 on my
> laptop.
What happens if you select the 2.2 compat dist during installation?
- Jordan
>
> I tried to install netscape 4.08 from both
> ports and then as a package.
>
> Both times, I get the following error
>
> Couldn't load /usr/libexec/ld.s
> I installed it both during installation and then
> again via /stand/sysinstall just to make sure.
>
> Still no luck.
Hmmm. So much for that idea. :) Oddness..
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
> It breaks because compat22 is installing _everything_ in
> /usr/lib/compat/aout. We've reproduced this locally - compat22 is
> hosed.
Hmmm. Good thing I took that out of the default list of installation targets
then. :)
I tend to think that the compat22 distro simply aged and died but nobod
1> Could it be possible to unite these ones in /src/sys/boot/i386/mbr/ ?
It could be possible, yes. :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
> What make OpenBSD so "secure" ? Or can this kind of security be
> reproduced with FreeBSD ports ? I think of tools like:
It's not the tools but the amount of time supposedly invested in
improving security. I say "supposedly" because a lot of the buffer
overflow issues they've dealt with haven't
> I'm not sure..I've been wandering through the openbsd source tree and merging
> useful diffs from binaries, but I haven't been too organised about it so far,
> and haven't encountered much in the way of "important" fixes. I'm sure there
> are some, though.
While it can rightfully be said that Op
> Since doing so would allow someone to build what was on the 3.2-RELEASE
> CDROM, maybe we should ask Jordan if the tag shouldn't be slid forward
> for src/lib/compat/compat22/Makefile.
Sorry, the release is already out and I don't slide a fixed reference
tag after its reference point has indelib
Anyone here going to USENIX who'd also like to trade a free
registration in exchange for playing "scribe" for the FREENIX track at
the USENIX technical conference this year? http://www.usenix.org for
details.
- Jordan
--- Forwarded Message
Date: Tue, 25 May 1999 16:09:53 -0800
To: freenix-c
t;
>
> On Wed, 26 May 1999, Larry Lile wrote:
>
> >
> > On Wed, 28 Apr 1999, Larry Lile wrote:
> >
> > > On Wed, 28 Apr 1999, Jordan K. Hubbard wrote:
> > >
> > > > > I don't mind waiting until after the freeze/release, I just wan
... for a quick promo tour and would be more than happy to meet people
while I'm there.
So far, I have the evening of 5/31 free for whatever (group dinner?)
and I'll be speaking at the Japan Unix Society meeting on 6/1 from
18:30 - 20:30, after which we'll be having a small dinner party until
arou
> wonderful! You know, I should use that myself! "Hey Bill: my network
> crashed." "Well, there's probably something you could do to fix that
> but I don't know the details." Yes! I like it! Instead of trying to help
> people, I'll be maddeningly vague! I'll pretend to be helpful but stop
You hav
Perhaps we can cut through all the finger pointing and counter-finger
pointing here and just move on to the chase by asking one simple
question: Will you be at USENIX? That would be an excellent
opportunity to discuss it in person, where emotion and
facial-expression stripping isn't such a huge pr
Excellent. Let's assume then that all the core folk who are there,
plus any committers who have an interest in the issue (since core has
to listen to its developers' opinions too or we can no longer honestly
claim to represent their interests), will be getting together during
the week to discuss t
> I'm sure that the fact that -release ended up with such obvious
> instabilities was out of your control (IMHO RELENG_3 shouldn't have
> been dubbed -stable 'till 3.2 was tagged), but I'd bet that this did
Just a side comment on this - there was tremendous flammage that the
RELENG_3 branch was
> I'm not saying he should have backed out his changes, I'm saying that
> they shouldn't have been made - that's why removing the commit bit
> was the right move.
Let me just explain something here which I think may either make Matt
happier or less so, depending on his priorities. :)
Matt's com
> It isn't something as simple as not putting bpf into the install kernel is
> it?
I'm afraid not. :) The symptom was that dhcp started up just fine, it
just refused every lease offered by the server. Debugging stuff on
the boot floppy is also kinda hard and the deadline was coming up
so I had t
Not to pick on Brian, but can we end this pathetic and sorry thread
already? Everybody: Just play nice with your little brother and
stop poking him in the back seat - we'll get to where we're going
soon and then everybody can have a milkshake if they've been good.
Thank you.
- Jordan
To Unsubs
> Forgive my ignorance, but what exactly is meant by a "variant link", and
> what might one be used for?
Gee, it's refreshing to see someone other than myself bringing this
subject up. :)
Variant symlinks, which many of us fell in love with back in our Apollo
days, are essentially just symlinks w
> And have /usr/bin point to /binaries/i386/bin or /binaries/mips/bin
And before people jump on me, let me just clarify in advance that I
was not meaning to imply that Apollo ever used the x86 architecture.
They didn't. It was just an example. :)
- Jordan
To Unsubscribe: send mail to majord...
> For the benefit of those of us who weren't at USENIX, can we please
> have a summary of what was discussed/decided?
Nothing was [deliberately] decided but much was discussed. As soon as
one of us lands back home in some reasonable state, a summary will be
posted. I've yet to do this myself and
> symlinks have caused me grief (Pyramid OSx) and never joy. I hope it fails
> yet again to appear in FreeBSD. Just think of the new security holes for a
> start.
Name one, please. You can currently point a symlink anyplace you
like; whether the user has permission to *read* or execute the targ
> is better. Unless you're Danish you don't just get to delete bits of the
s/Unless/Especially if/ :-)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
> to do actually it. Personally, I think it would be a doable
> project if someone wanted to have a go at it - to allow a filesystem
> to be grown or shrunk on a cylinder-by-cylinder basis. The only real
> complexity occurs when you are shrinking a filesystem - you have to locat
> I agree with the approach. But why write a simplistic volume manager
> when we already have vinum?
vinum is far from simplistic, but I suppose it might also do. :)
Still, it would someday be nice if you could use vinum as the very
powerful swiss-army knife that it currently is OR as a dull axe
> through so-called "spiffy" installs is growing exponentially. Keeping a
> simple interface rather than trying to play human engineering with no
> real human interfaces lab and a 500K$ testing budget might be better.
> Just my 2 cents... I'll shut up now... (I mean, why should *I* beef so
> much?
> What actual marketing information do we actually have that says that in
> order to go after the desktops we aren't currently installed on we have to
> add a lot of engineering effort to the installer? Would it be better to
Well, just to clear up what looks like a misunderstanding in the
making,
I assume you mean a major character device number only? You can
have 127 (decimal).
Any prediction on when you think this driver will be ready to bring
into -current? It sounds quite promising!
- Jordan
>
> Folks,
>
> I have been developing firewire (IEEE1394) device driver on FreeBSD and
>
> Would it be possible to have this code put up for www/ftp or
> something, so that anyone who is interested could have a look?
Feel free, just don't ask me questions about it since I honestly don't
have time right now to explain to many hundreds of people how to build
this stuff. In a nutshell,
Four. :)
> On Fri, Jul 02, 1999 at 05:15:14PM -0700, Mike Smith wrote:
> > > I have to agree with Eivind, I know of people in my lab that have
> > > FTP_PASSIVE_MODE defined to nosense values since that is all that was
> > > required before. Now what are these poor souls to do when they upgrade
>
I'm going to have a "core team page" worked on which has pictures and
brief bios, perhaps something by next week.
Such things may seem frivolous, but I it helps people relate a little
more directly to the core team if they can see what they look like and
read a bit about them. Same for the commit
> Which can be disabled in the bash port before the next release...
No, that's a really stupid idea.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
I think that whomever actually writes it will get to name it whatever
the hell they way, that's what I think. :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
> just collecting URLs for people home pages might be an easier task
> perhaps ?
It needs to look better than that. A list of URL's would not look
like a staff page, it would look like a cheesy, uninteresting page of
links. :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "u
I'm not asking any of you to prepare a resume - we're starting JUST with
the core team bios and pictures here. :)
- Jordan
> > > just collecting URLs for people home pages might be an easier task
> > > perhaps ?
> >
> > It needs to look better than that. A list of URL's would not look
> > like
> I think you'll find, once you get that far, that things are anything
> but trivial. I'm certainly open to suggestions, but consider:
>
> vinum -i /dev/something volumename
>
> Where does it insert it? What if the volume has more than one plex,
> which it will in the case of a mirror?
OK,
> Yuck. That's a complete abomination. What's the point of it? It's turning
Paging Terry Lambert, Terry Lambert - do you read me? It's time for
your annual rant on the topic of memory overcommit. :-)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers"
Whatever you do with identd, just make it work through NAT. That's
the #1 request from folks where this is concerned.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
> Jordan should have to say something about this. AFAIR, bumps are
> allowed but only by one between releases. We will have to provide
> libc_r.so.3 in /usr/lib/compat/compat3x, though (we'll have to do this
> anyway by the time 4.x is released).
I'd prefer not to bump it... John Birrell and I a
> I don't care one way or the other. I could leave out the wrapped
> poll() very easily and avoid the issue all together. This would
> provide -stable with everything -current has, except of course
> poll(). I'd prefer to add poll, though...
I'm OK with adding poll(), it just seemed odd that th
On Aug 15, 2013, at 3:38 PM, Jakub Lach 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
http://lists.freebsd.org/mailman/l
Amen!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Jan 26, 2005, 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
> 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
>
> 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
> 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
> 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
> dis
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 shoo
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
> > > so
> 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 PROTECT
h my proposed diff in
any case. Red Hat Linux, interestingly enough, returns errno 25 in
this case (ENOTTY)!
This is your libc. This is your 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
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 FreeB
://cvs.opendarwin.org/index.cgi/src/Libinfo/
- 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, bu
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
work
m. Comments, advises or
so.
Who can I talk about bsd.ports.mk improvements?
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:
mm - [EMAIL PROTECTED]; [EMAIL 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 Ma
't go to the stars" - JMS/B5
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
--
Jord
OTECTED]
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
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
ement 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]"
it. Then
you can reboot off the hard drive and get much fancier with a VGA16 X
server or ncurses based installer which 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
1 - 100 of 245 matches
Mail list logo
