Re: ATA atapi-all.c problems/fixes/cleanups

2000-01-06 Thread Soren Schmidt
It seems Brian Fundakowski Feldman wrote: It's just as well. It's almost 4 AM and I've just about given up on getting this all working. Anyway, if everything has to be DEV_BSIZE, then I guess that would simplify things, except when I try, say, writing 4697 bytes as an audio blocksize (2 *

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Mike Smith
Personally, I think the timeline laid down - 25(?) days from now until 4.0 release is too aggressive. Given that the announcement (to me) seemed to be rather autocratic and possibly driven by marketting factors ("we need 4.0 out now regardless" ?) than by the general stability and

Small fix to netstat argument processing

2000-01-06 Thread Stephen McKay
I've got very used to an alias ns='netstat -f inet' which lets me do all the things I like to do without annoying me with stuff I don't want to see. All the options that don't care about the address family just ignore that option. Or, used to. Recently that changed, and "netstat -f inet -i" in

Re: rlogin from 3.X to 4.0 problem...

2000-01-06 Thread Mark Murray
With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine: rlogin bsd4 assword:hey this is great! why is the initial 'P' missing, and the password echoed ? MFC of etc/pam.conf coming to fix this... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Donn Miller
On Thu, 6 Jan 2000, Julian Elischer wrote: I agree with this.. I think that 4.0 is clsoe but it's just not there yet. I think it needs IPV6 to have reached a better milestone, and certainly the stuff that warner is doing (and others) needs to be a little further down the track. I agree.

Re: Small fix to netstat argument processing

2000-01-06 Thread Yoshinobu Inoue
Recently that changed, and "netstat -f inet -i" in particular changed to give the -f flag priority over the -i flag. This makes no sense to me, so I intend to commit this patch: Could this be left with adding sflag check? Because now there is interface statistics display mode, when, e.g.

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Amancio Hasty
Curious , what is elischer.org ? 8) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Small fix to netstat argument processing

2000-01-06 Thread Yoshinobu Inoue
I think my last description was poor. Could this be left with adding sflag check? Because now there is interface statistics display mode, when, e.g. Maybe improved one is, Because now there is a mode where protocol specific statistics over each interface is displayed. Yoshinobu Inoue

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Ruslan Ermilov
On Thu, Jan 06, 2000 at 02:32:47AM -0800, Amancio Hasty wrote: Curious , what is elischer.org ? 8) According to www.elischer.org, this is the temporary home page for the Elischer family's internet enterprises and Family stuff. -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL

GDB Problems !

2000-01-06 Thread Pascal Hofstee
Hello, I think i already mentioned the following issue several months ago ... but just noticed this again. And considering 4.0 is coming up soon, I really think this ought to be fixed. see the following testcase: #include stdio.h int main(int argc, char **argv) { int i = 0;

wormcontrol replacement coming!

2000-01-06 Thread Soren Schmidt
I've just done a replacement for wormcontrol that allows burning CDR/CDRW with just one command. Its simpleminded but it works. Just a FYI as I know several people have said they where thinking about doing such a thingy. The API to the kernel has changed too, finally I got around to cleaning

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Brad Knowles
At 5:25 AM -0500 2000/1/6, Donn Miller wrote: I agree. Why rush 4.0-RELEASE out the door if it's "not there yet"? One possibility is to make our 4.0-current something like 3.9-RELEASE, and when everything has been added, release 4.0-RELEASE. No, I disagree. There's too much in

Re: Small fix to netstat argument processing

2000-01-06 Thread Yoshinobu Inoue
Hmm, I've just noticed some small misalignment of column headings in the default output. I'll fix that too. Stephen. I also noticed that my another IPv6 related change is one of main cause of the misalignment. So I also tried to make patches for it, including "netstat -f inet -i" issue.

Installation problem

2000-01-06 Thread Satyajit Das
I'm new in FreeBSD. Today i install FreeBSD3.3 sucessfully. I have 2 harddrive both 6.4GB. In one harddisk I have Redhat and another one i install FreeBSD 3.3 now. I install Freebsd boot manager but i don't find it. but when i add Freebsd in Lilo (edit /etc/lilo.conf file) it shows : hdb1 =

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Robert Watson
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). If

BOOTP and IPFIREWALL

2000-01-06 Thread David Gilbert
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 IPFIREWALL in a BOOTP-loaded machine,

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Steve Ames
I agree. Why rush 4.0-RELEASE out the door if it's "not there yet"? One possibility is to make our 4.0-current something like 3.9-RELEASE, and when everything has been added, release 4.0-RELEASE. 3.9-RELEASE would be a lot like 4.0-REL, only with some missing parts (such as IPV6 you just

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Andreas Klemm
On Thu, Jan 06, 2000 at 12:55:06PM +0100, Brad Knowles wrote: More releases more often are better than indefinitely holding up releases waiting for just that one last thing to be finished. Second that. And to follow on that... FreeBSD 4.0 will become the new STABLE. So 4.0 should become

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Steve Ames
More releases more often are better than indefinitely holding up releases waiting for just that one last thing to be finished. I think a recent thread on -STABLE indicates that the majority of end users seem to believe that -RELEASE means STABLE and should be fully operational not a

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Steve O'Hara-Smith
On 06-Jan-00 Andreas Klemm wrote: On Thu, Jan 06, 2000 at 12:55:06PM +0100, Brad Knowles wrote: More releases more often are better than indefinitely holding up releases waiting for just that one last thing to be finished. Second that. And to follow on that... FreeBSD 4.0 will

mergemaster(8) busted

2000-01-06 Thread Andy Farkas
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. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications

Re: ata: Mount root failure: 6

2000-01-06 Thread Alexander Langer
Thus spake Alexander Langer ([EMAIL PROTECTED]): Here are the messages regarding ata and hdd's: ata-pci0: VIA 82C586 ATA controller at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0:

Booting with a Mylex-DAC960PL Installed

2000-01-06 Thread Lawrence Farr
I downloaded Jan 2nd Current, made the floppies, and tried to boot a box with a DAC-960PL installed. The system hung as soon as it started to read from floppy. Rebooted, turned off the BIOS on the Mylex, system booted OK. Installed directly to the Mylex, and it all came to a halt with "Tried to

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Warner Losh
In message [EMAIL PROTECTED] Eivind Eklund writes: : I believe putting down RELENG_4 without having a finished IPv6 and : functional laptop support (I'm not sure what state this is in right : now) would be a bad idea. The laptop support is approx that of 3.x. The fe device is no longer

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Eivind Eklund
On Thu, Jan 06, 2000 at 09:09:22AM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Eivind Eklund writes: : I believe putting down RELENG_4 without having a finished IPv6 and : functional laptop support (I'm not sure what state this is in right : now) would be a bad idea. The

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Warner Losh
In message [EMAIL PROTECTED] Eivind Eklund writes: : On Thu, Jan 06, 2000 at 09:09:22AM -0700, Warner Losh wrote: : The laptop support is approx that of 3.x. The fe device is no longer : supported as a pccard. The sn device has been added. The YE_DATA : floppy device isn't supported, but

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread David O'Brien
On Thu, Jan 06, 2000 at 09:09:22AM -0700, Warner Losh wrote: : I believe putting down RELENG_4 without having a finished IPv6 and : functional laptop support (I'm not sure what state this is in right : now) would be a bad idea. The laptop support is approx that of 3.x. The fe device is

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread David O'Brien
On Thu, Jan 06, 2000 at 09:45:11AM -0500, Steve Ames wrote: My question is how much time are developers/testers being given between feature freeze (9 days from now) and release to get all code working and stable? My question is not how much time the developers are being given -- the *real*

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread robgar
On Thu, Jan 06, 2000 at 03:49:45PM +0100, Andreas Klemm wrote: On Thu, Jan 06, 2000 at 12:55:06PM +0100, Brad Knowles wrote: More releases more often are better than indefinitely holding up releases waiting for just that one last thing to be finished. Second that. And to follow on

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Patrick Bihan-Faou
Hi, 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 community though. Also,

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Warner Losh
In message [EMAIL PROTECTED] Alex writes: : - Better laptop (PC card) support, possibly Cardbus (Warner Losh) Won't happen by Jan 15th unless someone my boss comes into my office today and tells me to work on nothing else except pccard/cardbus for the next 9 days. The old pccard code will be

Re: wormcontrol replacement coming!

2000-01-06 Thread Soren Schmidt
It seems Luigi Rizzo wrote: [Charset ISO-8859-1 unsupported, filtering to ASCII...] I've just done a replacement for wormcontrol that allows burning CDR/CDRW with just one command. Its simpleminded but it works. Just a FYI as I know several people have said they where thinking

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Warner Losh
In message 006001bf586a$409b4b00$[EMAIL PROTECTED] "Patrick Bihan-Faou" writes: : Look at the 3.x history: we just got some major features in the late 3.x : (netgraph in 3.4) this does not mean that 3.0 was a bad release. Actually, 3.0 was a bad release, support for which was dropped before

Re: wormcontrol replacement coming!

2000-01-06 Thread Luigi Rizzo
I've just done a replacement for wormcontrol that allows burning CDR/CDRW with just one command. Its simpleminded but it works. btw for the records -- on 2.2.x i noticed i needed some wait between the transfer of data to CDR, and the "fixate" command (in other words, the fixation would

Re: wormcontrol replacement coming!

2000-01-06 Thread Luigi Rizzo
[Charset ISO-8859-1 unsupported, filtering to ASCII...] I've just done a replacement for wormcontrol that allows burning CDR/CDRW with just one command. Its simpleminded but it works. Just a FYI as I know several people have said they where thinking about doing such a thingy. this would

patches for SMP

2000-01-06 Thread Mohit Aron
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 below).

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread robgar
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Steve Ames
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Frank Mayhar
(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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Darren Reed
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?

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Amancio Hasty
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Poul-Henning Kamp
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 -RELEASE

Re: mergemaster(8) busted

2000-01-06 Thread Chris Piazza
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 arguments

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Josef Karthauser
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 fine.

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Christian Kuhtz
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Tom Bartol
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 laptop)

rlogind message in /var/log/messages

2000-01-06 Thread Mohit Aron
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Dennis Glatting
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Marcel Moolenaar
"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 PROTECTED]

PCCARD - after installing a snapshot, no pccard support

2000-01-06 Thread Jesper Skriver
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,

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Warner Losh
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread David O'Brien
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

HEADS UP! wormcontrol and sys/dvdio.h users

2000-01-06 Thread Soren Schmidt
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

Re: ATA driver problems

2000-01-06 Thread Peter Jeremy
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

Re: PCCARD - after installing a snapshot, no pccard support

2000-01-06 Thread Warner Losh
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 merge

Problem exposed with sym driver

2000-01-06 Thread Michael Reifenberger
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Peter Jeremy
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread scanner
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 anything

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Randy Bush
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Mike Smith
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,

So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Jordan K. Hubbard
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 and on the console at the same time (cd0:ahc0:0:4:0):

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Matthew Jacob
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

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Matthew Jacob
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Jordan K. Hubbard
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Randy Bush
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_ with all of

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Jordan K. Hubbard
[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 anything

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Jordan K. Hubbard
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

Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th)

2000-01-06 Thread Jordan K. Hubbard
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

Re: Mounting CD-ROM with ATA driver hangs system

2000-01-06 Thread Peter Jeremy
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread fifi - the hamster - asami
* 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

Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th)

2000-01-06 Thread Christian Kuhtz
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

Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th)

2000-01-06 Thread Christian Kuhtz
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 not

Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th)

2000-01-06 Thread Mike Smith
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

Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th)

2000-01-06 Thread Mike Smith
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 read

Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th)

2000-01-06 Thread David O'Brien
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

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Mark Newton
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 now

Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th)

2000-01-06 Thread Mike Smith
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

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Karsten W. Rohrbach
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

-current or 3.4 with KAME ???

2000-01-06 Thread Boozy
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

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Adam
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 has

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Andy Sparrow
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. One

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread David Greenman
* 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

Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th)

2000-01-06 Thread David Greenman
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

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Warner Losh
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 :-)

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Jordan K. Hubbard
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

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Kenneth D. Merry
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 reasons

Re: [solicite review and confirmation of tcp for IPv6 patches]

2000-01-06 Thread Yoshinobu Inoue
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.

Re: 4.0 code freeze scheduled for Jan 15th

2000-01-06 Thread Wes Peters
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 reason not to

New kernel no longer boots on one of my machines... ata, other problems

2000-01-06 Thread Matthew Dillon
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: *

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Kenneth D. Merry
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

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Kenneth D. Merry
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 both - no go.

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Jordan K. Hubbard
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 that

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Jordan K. Hubbard
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.

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Jordan K. Hubbard
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 0 0 c 0

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Kenneth D. Merry
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,

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-06 Thread Matthew Dillon
: * First, it locks up with process 0 stuck in 'atawait' while I meant 'atacmd' here. -Matt To Unsubscribe: send mail to [EMAIL

Re: Small fix to netstat argument processing

2000-01-06 Thread Stephen McKay
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

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-06 Thread Matthew Dillon
: :: * First, it locks up with process 0 stuck in 'atawait' while : : : I meant 'atacmd' here. : : -Matt From what I can tell so far,

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Oliver Fromme
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. :-) To

Re: So, tell me again why we can't read audio CDs in SCSI drives?

2000-01-06 Thread Kenneth D. Merry
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 drive to

  1   2   >