It seems Matthew Dillon wrote:
>
> :From what I can tell so far, something during the kernel boot is
> :disabling the timer interrupt. The ATA probe does a tsleep() which
> :never times out. Output is queued to the console during the boot
> :sequence which is never printed (unti
It seems Alexander Langer wrote:
> Thus spake Soren Schmidt ([EMAIL PROTECTED]):
>
> > The DVD ioctl's has changed numbers, so those using that
> > should recompile thier apps.
> > Wormcontrol and related files will be removed soon.
>
> I saw changes for the ioctl for the ata*, but not for the w
:From what I can tell so far, something during the kernel boot is
:disabling the timer interrupt. The ATA probe does a tsleep() which
:never times out. Output is queued to the console during the boot
:sequence which is never printed (until I CTL-ALT-ESC)...
:
:has someone m
On 07-Jan-00 Amancio Hasty wrote:
> I just thought that I would need to add an audio intergap between
> tracks
> but hey if cdrecord can do it great!
Well, if you are burning in Track-At-Once mode then there is a 2 second
gap between the tracks (and you can't do anything about it). To remove
Amancio Hasty <[EMAIL PROTECTED]> wrote:
> Hi
> Tnks for the tip!
> I just thought that I would need to add an audio intergap between tracks
> but hey if cdrecord can do it great!
Hi,
you can also use cdrdao (ports/audio/cdrdao) which has support
for DAO (control over gaps between tracks). T
As warned yesterday, I've just removed the ability for libcrypt to
understand SHA-1 passwords. This was present but undocumented in the tree
for the past few months and was removed so it can be reimplemented
properly as part of a revamped libcrypt at a later date. Anyone who was
actually making us
Hi
Tnks for the tip!
I just thought that I would need to add an audio intergap between tracks
but hey if cdrecord can do it great!
Tnks!
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mess
On 07-Jan-00 Amancio Hasty wrote:
> say do you know how to create an audio cd?
> I want to extract tracts from different audio cds and create my
> own audio cd. I have a Yamaha scsi cd writer.
Use a tool to rip the audio (tosha, cdd, cdda2wav, etc etc).. Get all
the tracks you want.
Then r
say do you know how to create an audio cd?
I want to extract tracts from different audio cds and create my
own audio cd. I have a Yamaha scsi cd writer.
Tnks!
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
Kenneth D. Merry <[EMAIL PROTECTED]> wrote in list.freebsd-current:
> [...]
>> PS: The email address that Ken mentioned isn't valid, please
>> use <[EMAIL PROTECTED]>.
>
> Then why are you still using it? This is from the headers on your message:
>
> From: Oliver Fromme <[EMAIL PROTECTE
Alexander N. Kabaev <[EMAIL PROTECTED]> wrote in list.freebsd-current:
> Is that something to be expected? How to copy a complete CD-ROM image into ISO
> file then?
You can also use tosha to read a CD-ROM track to make an ISO
image. It supports CD-ROM data tracks as well as audio and
video (VC
> I'm reading this thread, and no, I have no idea. :-)
> To be honest, I've never heard about an "SAF" drive.
It's a "Smart and Friendly CD-R8020", also sold as the "CD Rocket
Recorder" here in the U.S. It does 20X reads, 8X writes and 4X
re-writes. And no, I don't usually waste my CDR heads o
> Any other SCSI CD owners here currently using tosha? I'd be
> quite interested to know if this is drive-specific.
I've used tosha with a "TOSHIBA CD-ROM XM-6201TA 1037" SCSI drive to
read audio data for subsequent mp3 conversion with no problems.
louie
To Unsubscribe: send mail to [EMA
I have TOSHIBA DVD-ROM SD-M1201 1R08 on Adaptec 2440U2W and tosha works fine
with it. I used to get the same error messages from tosha just a
couple weeks ago. cdd2wav worked OK. I upgraded to the latest firmware
on both the controller and the drive and error messages disappeared.
Kernel and wo
On Fri, Jan 07, 2000 at 06:33:47 +0100, Oliver Fromme wrote:
> Kenneth D. Merry <[EMAIL PROTECTED]> wrote in list.freebsd-current:
> > Also, you might want to try mailing Oliver Fromme
> > <[EMAIL PROTECTED]> (the author of tosha) and see if he
> > has any idea what it would take to get your dr
Kenneth D. Merry <[EMAIL PROTECTED]> wrote in list.freebsd-current:
> Also, you might want to try mailing Oliver Fromme
> <[EMAIL PROTECTED]> (the author of tosha) and see if he
> has any idea what it would take to get your drive to function.
I'm reading this thread, and no, I have no idea. :
:
:: * First, it locks up with process 0 stuck in 'atawait' while
:
:
: I meant 'atacmd' here.
:
: -Matt
From what I can tell so far, something
On Thursday, 6th January 2000, Yoshinobu Inoue wrote:
>Does these patches fix your problem, or should another better
>fix is desired? Please give me any opinions.
It passes all my tests. Please commit it. Thank you!
And earlier you wrote:
>Because now there is interface statistics display mo
: * First, it locks up with process 0 stuck in 'atawait' while
I meant 'atacmd' here.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
On Thu, Jan 06, 2000 at 20:28:40 -0800, Jordan K. Hubbard wrote:
> > I think what is actually going on is that it doesn't like the 0x82 density
> > code that most other drives use. So that's what the first error message
> > likely tells us. (the density is given in the mode select parameter list
> In addition to trying cdda2wav, here's something else you can try in your
> tosharc:
>
> "SAF" "" "" 0x28 1 0x82 0 10 0
>
> or:
>
> "SAF" "" "" 0x28 0 0x00 0 10 0
Yep, tried both - no go.
The first produces:
(pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10
Also, I can now add that cdda2wav does work (hurrah), but it does yelp
that it can't read the CD TOC.
Of course, the mystery is that tosha no longer works yet was not
changed, nor was the ripit script I call tosha from, so something on
our side of the fence also moved with respect to this drive.
> I think what is actually going on is that it doesn't like the 0x82 density
> code that most other drives use. So that's what the first error message
> likely tells us. (the density is given in the mode select parameter list,
> thus the invalid field)
>
> The second error message likely means
On Thu, Jan 06, 2000 at 20:02:34 -0800, Jordan K. Hubbard wrote:
> > In addition to trying cdda2wav, here's something else you can try in your
> > tosharc:
> >
> > "SAF" "" "" 0x28 1 0x82 0 10 0
> >
> > or:
> >
> > "SAF" "" "" 0x28 0 0x00 0 10 0
>
> Yep, tried
On Thu, Jan 06, 2000 at 20:05:21 -0800, Jordan K. Hubbard wrote:
> Also, I can now add that cdda2wav does work (hurrah), but it does yelp
> that it can't read the CD TOC.
Weird. What does cdda2wav identify the drive as? Can you send the output?
(verbose, if there's a verbose switch) That may h
Well guys, I tried upgrading one of my older machines today to the
latest 4.0. It was running an older 4.0 kernel (Nov 29 1999).
I've included the dmesg output from the (successfully booting) older
kernel at the end.
The newer kernel locks up in several ways:
* Fi
Mike Smith wrote:
>
> > In some email I received from Steve Ames, sie wrote:
> > >
> > > *shudder* I really, really dislike the idea of -RELEASE actually being a
> > > wide beta so that some code can get a workout. LAbel it beta and more people
> > > will use it than currently do anyway. Any reas
> Hello,
>
> I prepared tcp for IPv6 patches to the current.
> I would like it to be reviewed and confirmed in many
> environment before committing it, because I think updating tcp
> code is very critical to system stability.
> The patches are placed below.
>
> http://paradise.kame.net/v6proxy/
On Thu, Jan 06, 2000 at 17:28:23 -0800, Jordan K. Hubbard wrote:
> > You mean an Adaptec controller, right?
>
> Yes, I guess Adaptec did buy those guys.
>
> > Try tosha or cdda2wav and report back on whether or not it works. dd has
> > never been a supported way to read audio tracks, for the re
> You mean an Adaptec controller, right?
Yes, I guess Adaptec did buy those guys.
> Try tosha or cdda2wav and report back on whether or not it works. dd has
> never been a supported way to read audio tracks, for the reasons outlined
> above. It may be possible in some situations, but it was pr
In message <[EMAIL PROTECTED]> "Karsten W. Rohrbach" writes:
: i think, theres a port of tosha available, but the last time i tried
: this one it wouldnt work for me so i used the l*n*x box next to my
: workstation...
Last time I tried Tosha it worked w/o a hitch for me and my 1x cdrom
changer :-
>> Get IPv6 into the tree. Now. Thank you.
>
>I don't know quite what makes you think that we came down in the last
>shower of rain, but has it ever occurred to you that we're not
>_completely_ stupid?
>
>Do you _always_ assume that anyone other than yourself is a complete
>moron? What makes
> * From: "Jordan K. Hubbard" <[EMAIL PROTECTED]>
>
> * How do you think things "get included" in the OS? Do you think one
> * just moves the KAME bits into a directory next to /usr/src, goes away
> * for 24 hours to let them bits do their thing, and then comes back to
> * find that nature has do
> genius% ping6
> usage: ping6 [-dfnqRrvwW] [-a [alsg]] [-b sockbufsiz] [-c count] [-I interface]
> [-i wait] [-l preload] [-p pattern] [-s packetsize]
> [-h hoplimit] host [hosts...]
There are suggestions that ping6 should be integrated into
ping for users could natur
On Fri, Jan 07, 2000 at 02:03:29AM +0100, Karsten W. Rohrbach wrote:
> detection and removal (real goodd error correction) and this ones also
> really fast (10x speed) when youre reading on a plextor drive (such as
> my pxw4220t) or something else that has a native mode for extracting
> audio.
I believe the cdrdao port had the abilities and some of the code from
paranoia in it.
On Fri, 7 Jan 2000, Karsten W. Rohrbach wrote:
>reading raw audio data off a cd with dd did never work for me...
>anyway, it would be a good thing(TM) if there was a tool such as
>cdparanoia under l*n*x that ha
In message <[EMAIL PROTECTED]> Peter Jeremy writes:
: Maybe I misunderstood Jordan's original announcement, but this was
: also a surprise for me. Jordan originally stated that there'd be a
: feature freeze from 15th December 1999. I got the impression that
: this was going to be in effect for s
On Thu, Jan 06, 2000 at 07:37:59PM -0500, Christian Kuhtz wrote:
>
> Yes. As a matter of fact, I have.
>
> So, where is the email which specifically states the reasons why it will not
> be integrated? I apparently missed something in this flurry of email.
I don't know if you realise, I most
On Fri, Jan 07, 2000 at 02:03:29 +0100, Karsten W. Rohrbach wrote:
> reading raw audio data off a cd with dd did never work for me...
See my response to Jordan -- it has never been a supported way to read
audio tracks.
> anyway, it would be a good thing(TM) if there was a tool such as
> cdparano
On Thu, Jan 06, 2000 at 17:28:23 -0800, Jordan K. Hubbard wrote:
> > You mean an Adaptec controller, right?
>
> Yes, I guess Adaptec did buy those guys.
Adaptec bought DPT, not Advansys. In any case, you've got a low end
Adaptec controller, with a 7850.
> > Try tosha or cdda2wav and report bac
Karsten W. Rohrbach <[EMAIL PROTECTED]> wrote in list.freebsd-current:
> reading raw audio data off a cd with dd did never work for me...
> anyway, it would be a good thing(TM) if there was a tool such as
> cdparanoia under l*n*x that has all that fancy jitter and scratch
> detection and remov
Hi Lists again :))),
I'm sorry but when I sent this message I wasn't subscribe here. So I am
puting this message again and I'd be happy if somebody reply me.
-
How are the implementation of IPv6 in FreeBSD 4.0? Is it available? Is it
stable?
What is better: use FreeBSD 3.4 with Kame or FreeB
reading raw audio data off a cd with dd did never work for me...
anyway, it would be a good thing(TM) if there was a tool such as
cdparanoia under l*n*x that has all that fancy jitter and scratch
detection and removal (real goodd error correction) and this ones also
really fast (10x speed) when yo
> Get IPv6 into the tree. Now. Thank you.
I don't know quite what makes you think that we came down in the last
shower of rain, but has it ever occurred to you that we're not
_completely_ stupid?
Do you _always_ assume that anyone other than yourself is a complete
moron? What makes you thin
On Thu, Jan 06, 2000 at 04:27:27PM -0800, fifi - the hamster - asami wrote:
> dear mr. hubbard,
> please do not insult hamsters. it doesn't work that way for hamsters
> either. we are fully aware of our surroundings and plan our lives
> accordingly. in fact, satoshi is out picking oranges
On Thu, Jan 06, 2000 at 07:04:16PM -0500, Christian Kuhtz wrote:
> <[EMAIL PROTECTED]> -wk, <[EMAIL PROTECTED]> -hm
^^^
Damnit! I've asked for some features in GCC, GNU grep, and GNU diff. I
want them *NOW* in time for 4.0-RELEASE. So where the fsck are t
> > Do you _always_ assume that anyone other than yourself is a complete
> > moron?
>
> Where did this and all that other stuff come from?
You have to ask this?
> > What makes you think that we don't want this code integrated, or
> > that we don't care about it? Have you bothered to actually
> On Thu, Jan 06, 2000 at 04:17:52PM -0800, Jordan K. Hubbard wrote:
> > > Get IPv6 into the tree. Now. Thank you.
> >
> > Start helping and stop asking. Now. Thank you.
>
> State specifically what is needed. Now. Thank you.
>
> Part of the lack of help may be the result of people clueles
On Thu, Jan 06, 2000 at 04:32:21PM -0800, Mike Smith wrote:
> > Get IPv6 into the tree. Now. Thank you.
>
> I don't know quite what makes you think that we came down in the last
> shower of rain, but has it ever occurred to you that we're not
> _completely_ stupid?
Sure it has. I think I'm
On Thu, Jan 06, 2000 at 04:17:52PM -0800, Jordan K. Hubbard wrote:
> > Get IPv6 into the tree. Now. Thank you.
>
> Start helping and stop asking. Now. Thank you.
State specifically what is needed. Now. Thank you.
Part of the lack of help may be the result of people clueless as to where to
On Thu, Jan 06, 2000 at 15:47:31 -0800, Jordan K. Hubbard wrote:
> If I stick an audio CD in my SCSI (rebadged Toshiba) CDRW drive
> and try to read data off of it, I get the following behavior:
>
> root@zippy-> dd if=/dev/rcd0c bs=2k of=/dev/null
> dd: /dev/rcd0c: Invalid argument
> 0+0 records
* From: "Jordan K. Hubbard" <[EMAIL PROTECTED]>
* How do you think things "get included" in the OS? Do you think one
* just moves the KAME bits into a directory next to /usr/src, goes away
* for 24 hours to let them bits do their thing, and then comes back to
* find that nature has done the
On 2000-Jan-06 18:38:08 +1100, Soren Schmidt <[EMAIL PROTECTED]> wrote:
>It seems Peter Jeremy wrote:
>> I just discovered that my ATAPI CD-ROM is no longer usable - when I
>> try to mount it, my maching hangs (hard).
...
>> acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA
>
> Get IPv6 into the tree. Now. Thank you.
Start helping and stop asking. Now. Thank you.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Hmm! Better hold the 4.0 Code Freeze until this sorts out!
No, just better sort it out more quickly than usual. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[Moved to just -current; this doesn't need to keep getting cross-posted]
> It's not like were moving from v4 to v6. Were just asking that it
> be included in the OS. It should be available to researchers using
> 4.0-RELEASE. That's all im saying. There is no reason to ask for resources
> or anyth
>>> time as other OS's make new releases *with* IPv6/IPSec. You work it out
>>> whether or not FreeBSD will win or lose from those two being there or not
>>> there.
>> what if the choice is
>> o release at the same time with lots-o-features but not all of v6
>> o release _considerably later_
It's a feature freeze, sorry. I still expect the loose-ends that are
in place as of that date to be tied up afterwards.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Bakul Shah wrote:
>
> fairings
>
I almost fell off my chair laughing..
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Jan 06, 2000 at 06:26:16PM -0500, [EMAIL PROTECTED] wrote:
> with it being in 4.1 or later. But if it's going to hurt FreeBSD in
> research labs, and universities who move to Linux instead or Solaris
> because they have a shipping v6 release regardless of how well it works
> that will hurt
Hmm! Better hold the 4.0 Code Freeze until this sorts out!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Yes, this is a very good point. Jordan, which is it?
On Fri, 7 Jan 2000, Peter Jeremy wrote:
> On 2000-Jan-07 01:43:09 +1100, Steve Ames <[EMAIL PROTECTED]> wrote:
> > _FEATURE_ freeze is January 15th.
>
> Not quite - Jordan specifically stated _CODE_ freeze (see the Subject:).
>
> Maybe I
If I stick an audio CD in my SCSI (rebadged Toshiba) CDRW drive
and try to read data off of it, I get the following behavior:
root@zippy-> dd if=/dev/rcd0c bs=2k of=/dev/null
dd: /dev/rcd0c: Invalid argument
0+0 records in
0+0 records out
(cd0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 0 0 0 4 0
(c
> FreeBSD releases. So thats moot. The point im trying to make is regardless
> of the state IPv6 is in, leaving it out of a major release is a no no IMO.
If you believe this is really an issue, then you should be scolding the
KAME folks and not the rest of us. They knew when the deadlines were,
> 4.0-RELEASE sounds like it will start becoming available at about the same
> time as other OS's make new releases *with* IPv6/IPSec. You work it out
> whether or not FreeBSD will win or lose from those two being there or not
> there.
what if the choice is
o release at the same time with lots
Thus spake Soren Schmidt ([EMAIL PROTECTED]):
> The DVD ioctl's has changed numbers, so those using that
> should recompile thier apps.
> Wormcontrol and related files will be removed soon.
I saw changes for the ioctl for the ata*, but not for the wd*
stuff.
Could wormcontrol at least stay as t
On Thu, 6 Jan 2000, David O'Brien wrote:
> And when will IPv6 fully be in 4-CURRENT?
> Besides offering two cents what else can you offer to make this happen?
> Time? More money?
>
> People here aren't backing their opinions by tell us *how* their to make
> their opinions happen.
I cant do any
On 2000-Jan-07 01:43:09 +1100, Steve Ames <[EMAIL PROTECTED]> wrote:
> _FEATURE_ freeze is January 15th.
Not quite - Jordan specifically stated _CODE_ freeze (see the Subject:).
Maybe I misunderstood Jordan's original announcement, but this was
also a surprise for me. Jordan originally stated t
Hi,
after enabling the sym-driver I get drive-lockups after some time of accessing
the disks hanging on the sym-driver.
It seems that at least on disk hangs up (steady disk light) until a bus-reset
"(noperiph:sym0:0:-1:-1): SCSI BUS reset detected" occurs.
A difference between ncr and sym-driver
In message <[EMAIL PROTECTED]> Jesper Skriver writes:
: Forgot the obvious, after building a new kernel, ep0 works again, but
: this could a show-stopper for many users, and with 4.0 soon to become a
: -RELEASE, this could hit quite a few unexperienced users.
I'll finish my PCCARD -> GENERIC merg
> In some email I received from Steve Ames, sie wrote:
> >
> > *shudder* I really, really dislike the idea of -RELEASE actually being a
> > wide beta so that some code can get a workout. LAbel it beta and more people
> > will use it than currently do anyway. Any reason not to release and ship a
>
On 2000-Jan-06 10:38:51 +1100, I wrote:
["dd if=/dev/rad0c of=/dev/null bs=64k" dies with an error]
I did some poking around and found that there are two bugs which
conspire together to cause this:
1) diskstrategy() does not detect dscheck() returning EOF, instead
passing a zero-length request
I've just committed burncd the wormcontrol replacement.
The ATAPI burner API has changed, so wormcontrol does
no longer work, use burncd instead (see burncd.8)
The DVD ioctl's has changed numbers, so those using that
should recompile thier apps.
Wormcontrol and related files will be removed soo
On Thu, Jan 06, 2000 at 03:02:32PM -0500, [EMAIL PROTECTED] wrote:
>
> I would like to agree with darren on this one. And think IPv6 should go
> into 4.0 even if the date needs to be pushed back. It is a major release
> and adding v6 is a major change. Thats just my 2 cents anyway.
And when will
In message <[EMAIL PROTECTED]> Josef Karthauser writes:
: My 3c589d works just fine now, along with suspend/resume :) (under 4.0).
The issue with the 3c589d is with its speed. It is falling back to
the timeout routine to send data rather than getting an interrupt when
the tx has happened (or so
On Thu, Jan 06, 2000 at 11:38:08PM +0100, Jesper Skriver wrote:
> Hi,
>
> I just installed the jan 5th 4.0-CURRENT snapshot on my brand new IBM
> 600E laptop, using the pccard floppies, it found my 3c589c just fine,
> and the installation was without any problems, but after booting the
> installe
In message <[EMAIL PROTECTED]> Frank Mayhar writes:
: On the _other_ other hand (:-), having pccard ep0 broken in 4.0-RELEASE is a
: mistake, IMHO. At the very _least_, the 589D's should work, and it would be
: Really Nice if the 574BTs worked, too. Of course, no one should expect full
: cardbus
Hi,
I just installed the jan 5th 4.0-CURRENT snapshot on my brand new IBM
600E laptop, using the pccard floppies, it found my 3c589c just fine,
and the installation was without any problems, but after booting the
installed system, there was no pccard support, and the ep0 device wasn't
found, woul
"Jordan K. Hubbard" wrote:
>
> 10 days, folks! Make 'em count.. :)
>
If people would stop sending this to -committers, I will actually have
some time left in which to do some work :-)
Better still, stop it completely.
thanks,
--
Marcel Moolenaarmailto:[EMAIL PROTECTE
Patrick Bihan-Faou wrote:
> Maybe I am wrong, but it seems to me that there is already quite a bit of
> IPv6 and IPSec stuff in the tree. Most of the kernel stuff is there (albeit
> seriously lacking documentation). To me this is not *too* critical right
> now. I see the point for the research co
Hi,
I upgraded FreeBSD-3.3 to FreeBSD-current (snapshot from Jan 3)
recently. I'm getting error messages of the form:
Jan 6 10:56:17 idli rlogind[1806]: no modules loaded for `rshd' service
Jan 6 10:56:17 idli rlogind[1806]: auth_pam: Permission denied
Jan 6 10:56:17
On Thu, 6 Jan 2000, Josef Karthauser wrote:
> On Fri, Jan 07, 2000 at 08:00:46AM +1100, Darren Reed wrote:
> >
> > btw, I completely agree with the need to have good pccard/pcmcia support.
> > For the first time there was a real reason for me to ditch FreeBSD on an
> > Intel platform box (my l
On Thu, Jan 06, 2000 at 10:14:19PM +0100, Poul-Henning Kamp wrote:
[..]
> FreeBSD-4.0 because now the time is right!
What's the rush?
If we believe that IPv6 is a noteable milestone, then what better time to
introduce it and get a "splash" with it than the ".0" major release. Do you
really thin
On Fri, Jan 07, 2000 at 08:00:46AM +1100, Darren Reed wrote:
>
> btw, I completely agree with the need to have good pccard/pcmcia support.
> For the first time there was a real reason for me to ditch FreeBSD on an
> Intel platform box (my laptop) and go with NetBSD where my 3c589d works
> just fi
On Fri, Jan 07, 2000 at 02:40:16AM +1100, Andy Farkas wrote:
>
> After cvsup'ing, a -current system based on userland/kernel dated
> 31-dec-1999, 'mergemaster -sv' is failing with mknod errors.
>
> cd src/sbin/mknod ; make all install ; make clean
> fixes it.
Uh, yeah? MAKEDEV uses mknod argu
In message <[EMAIL PROTECTED]>, Steve Ames writes:
>> On the other hand, there are *plenty* of things already in 4.0 that really
>> need to get out there and get a workout by a larger audience.
>> Delaying *them* is a big mistake.
>
>*shudder* I really, really dislike the idea of -RE
> In some email I received from Matthew Dillon, sie wrote:
> [...]
> > We are not going to repeat the 3.0 mess. IPV6 and IPSEC are important,
> > but not important enough to delay the already-delayed 4.0 release. 4.1
> > is not too late for these babies.
> [...]
>
> Well, let me p
In some email I received from Matthew Dillon, sie wrote:
[...]
> We are not going to repeat the 3.0 mess. IPV6 and IPSEC are important,
> but not important enough to delay the already-delayed 4.0 release. 4.1
> is not too late for these babies.
[...]
Well, let me put it this way.
On Fri, 7 Jan 100, Darren Reed wrote:
> In some email I received from Steve Ames, sie wrote:
> >
> > *shudder* I really, really dislike the idea of -RELEASE actually being a
> > wide beta so that some code can get a workout. LAbel it beta and more people
> > will use it than currently do anyway.
In some email I received from Steve Ames, sie wrote:
>
> *shudder* I really, really dislike the idea of -RELEASE actually being a
> wide beta so that some code can get a workout. LAbel it beta and more people
> will use it than currently do anyway. Any reason not to release and ship a
> 4.0-beta?
(Note: trimmed to just the -current list.)
Matthew Dillon wrote:
> On the other hand, there are *plenty* of things already in 4.0 that really
> need to get out there and get a workout by a larger audience.
> Delaying *them* is a big mistake.
On the _other_ other hand (:-), having p
> We are not going to repeat the 3.0 mess. IPV6 and IPSEC are important,
> but not important enough to delay the already-delayed 4.0 release. 4.1
> is not too late for these babies.
True... 4.1 is not too late. However a good part of IPv6 and IPSEC are
already present and the prim
:> For what it's worth, I think releasing 4.0 *without* IPv6 support
:> is a mistake. Why ? Because in < 12 months FreeBSD 5.0 will be
:> released *with* IPv6 support (I'd count IPv6 as being a big enough
:> change to signify a major release number change). If that doesn't
:> happen, then FreeB
On Thu, 6 Jan 100, Darren Reed wrote:
> For what it's worth, I think releasing 4.0 *without* IPv6 support
> is a mistake. Why ? Because in < 12 months FreeBSD 5.0 will be
> released *with* IPv6 support (I'd count IPv6 as being a big enough
> change to signify a major release number change). I
> That "someone" was me :-) I'll commit it before the deadline.
>
Thanks. Sorry, for not mentioning your name but I had already stripped off
the mail headers from the patch that you sent to me. The patch works great.
Please do commit it for the release.
- Mohit
To Unsubscribe: send mail t
> Hi,
> I am using the FreeBSD-4.0 snapshot from 3rd January 2000. This version
> used to panic when configured as an SMP but with less CPUs than there are
> actually in the machine (I had 4 processors but only wanted to use 1). Someone
> mailed me patches for fixing this problem (attached
David Gilbert writes:
| options BOOTP and options IPFIREWALL appear to be incompatible in
| -CURRENT. I havn't tried -STABLE. While the kernel compiles fine,
| the BOOTP code fails to send the discover packet and panic()'s.
|
| While it might not be immediately obvious that you'd want IPFIREWAL
On Thu, Jan 06, 2000 at 10:24:21AM -0800, Jordan K. Hubbard wrote:
> > There are many people who use freebsd in the real world that have been counti
> ng
> > on 4.0 including support for ipsec and ipv6, ipsec more importantly. We would
> > be willing to wait an additional couple of months for this
> There are many people who use freebsd in the real world that have been counti
ng
> on 4.0 including support for ipsec and ipv6, ipsec more importantly. We would
> be willing to wait an additional couple of months for this functionality, ple
Sadly, you've picked a particular bit of technology th
> My question is not how much time the developers are being given -- the
> *real* question is how much time the developers will give.
Thank you for saying this. If developers were constant-output
devices, we wouldn't need code freezes to motivate them into moving at
all. :-)
- Jordan
To Unsub
1 - 100 of 146 matches
Mail list logo
