Re: Found it --- 'ata' driver screwing up the machine (was Re: New kernel no longer boots on one of my machines... ata, other proble

[Soren Schmidt]

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 (until I CTL-ALT-ESC)... 
> :
> :has someone messed with spl*()'s anywhere recently?
> 
> Another datapoint:  When I DDB the machine and 'print *ticks',
> it comes up 0, and when I panic it it says "uptime 0s".
> 
> If I remove the 'ata' drivers I get the bootconf screen
> since there is no root - but *ticks is incrementing!
> 
> If I add 'ata' back in, buckus (DDB> print *ticks yields 0, machine
> is screwed up).
> 
> When I remove 'ata' and enable the 'wd' driver, everything works 
> normally.  The machine boots up fine.

Thats to be expected, the wd driver doesn't use config_intrhook_establish()
to hook in the probes when interrupts should be running.
>From your previous mail it looked like you had both ATA & SCSI in there,
then tried without SCSI and it kindof worked. The error 6 problem has
been up here before, but I dont remember the solution off hand, but
you should use /dev/ad* entries in you fstab, and have MAKEDEV'd 
them fairly resently, new bootblocks and loader are also a must.
My best guess is that config_intrhook_establish() screws up something
when more than one consumer uses it to hook into the boot process...

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP! wormcontrol and sys/dvdio.h users

[Soren Schmidt]

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 wd*
> stuff.
> 
> Could wormcontrol at least stay as the wd* drivers stay?

Sure, I dont se why not, but it adds to the confusion...

> ata* doesn't work for me at the moment, thus I'm using the wd drivers.

What is your problem ??

> Or am I wrong? Can I use burncd with the wd drivers?

No.

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Found it --- 'ata' driver screwing up the machine (was Re: New kernel no longer boots on one of my machines... ata, other problems)

[Matthew Dillon]

: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 messed with spl*()'s anywhere recently?
:

Another datapoint:  When I DDB the machine and 'print *ticks',
it comes up 0, and when I panic it it says "uptime 0s".

If I remove the 'ata' drivers I get the bootconf screen
since there is no root - but *ticks is incrementing!

If I add 'ata' back in, buckus (DDB> print *ticks yields 0, machine
is screwed up).

When I remove 'ata' and enable the 'wd' driver, everything works 
normally.  The machine boots up fine.

I think there's something weird going on with the ata driver but I'll
be damned if I know what it is.


As much as I like the idea of updating the wd driver, I think removing
it as the default is a big mistake.  The ATA driver is *NOT* ready for
prime time yet.  It certainly isn't ready for the warning that 'config'
gives you if you have 'wd' configured --- that warning is what caused
me not to even *try* to go back to the 'wd' device for three or four
hours.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Daniel O'Connor]

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
or change the intertrack gaps you need to burn in Disk-At-Once mode..

cdrdao and the newer versions of cdrecord support DAO.

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Ronald Kuehn]

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). The xcdrdao tool provides
a graphical user interface too.

Bye,
  Ronald
-- 
Give a man a fish, and you feed him for a day.
Tell him he should learn how to fish himself,
and he'll hate you for a lifetime.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

HEADS UP: SHA-1 password support gone

[Kris Kennaway]

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 use of the feature will have to update their passwords
back to MD5 before they reinstall the library.

Kris



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Amancio Hasty]

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 message

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

[Daniel O'Connor]

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 run cdrecord like so ->
cdrecord -dev=x,y,z -speed=a -audio track1.wav track2.wav ...

Easy! :)

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Amancio Hasty]

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" in the body of the message

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

[Oliver Fromme]

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 PROTECTED]>

I upgraded the hardware and OS of this box recently, and not
everything is configured correctly yet (not enough time)...
There _should_ be a valid Reply-To line in my email messages.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Oliver Fromme]

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 (VCD) tracks.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Jordan K. Hubbard]

> 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 on reading
audio data, but in this case it's a mid-tower case with lots of disks
in it and I can only fit one CD drive in. :)

> Jordan, if you can get that drive to work with tosha somehow,
> please let me know, so I ca add it to the regular tosha
> distribution.

I'll certainly be happy to do that.

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Louis A. Mamakos]

> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Alexander N. Kabaev]

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 world cvsupped on on Jan 4.

BTW, running dd on my DVD fails with the following error:
# dd if=/dev/rcd0a bs=2k of=/dev/null
dd: /dev/rcd0a: Invalid argument
0+0 records in
0+0 records out
0 bytes transferred in 0.001683 secs (0 bytes/sec)

Jan  7 00:04:51 kan /kernel: (cd0:ahc0:0:6:0): READ(10). CDB: 28 0 0 0 0 0 0 0
1 0
Jan  7 00:04:51 kan /kernel: (cd0:ahc0:0:6:0): ILLEGAL REQUEST asc:64,0
Jan  7 00:04:51 kan /kernel: (cd0:ahc0:0:6:0): Illegal mode for this track
Jan  7 00:04:51 kan /kernel: (cd0:ahc0:0:6:0): cddone: got error 0x16 back
J

Is that something to be expected? How to copy a complete CD-ROM image into ISO
file then?


On 07-Jan-00 Jordan K. Hubbard wrote:

> 
> Any other SCSI CD owners here currently using tosha?  I'd be
> quite interested to know if this is drive-specific.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 function.
> 
> I'm reading this thread, and no, I have no idea.  :-)
> To be honest, I've never heard about an "SAF" drive.
> 
> If I had such a stubborn drive, I would start trying a bunch
> of "typical" parameter sets that are known to work with other
> drives, and then try to interpret the results.  Maybe try to
> contact the vendor and ask for docs, but that's pretty much
> fruitless, as experience shows.  If all else fails, make a
> brute-force attack on density codes...
> 
> Jordan, if you can get that drive to work with tosha somehow,
> please let me know, so I ca add it to the regular tosha
> distribution.

I suspect that it may be a MMC drive.  I took a look at the spec, and the
cdda2wav source, and I've got a patch that may do the trick.  Once Jordan
sends output from cdda2wav, I'll know more.

> 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 PROTECTED]>

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 be honest, I've never heard about an "SAF" drive.

If I had such a stubborn drive, I would start trying a bunch
of "typical" parameter sets that are known to work with other
drives, and then try to interpret the results.  Maybe try to
contact the vendor and ask for docs, but that's pretty much
fruitless, as experience shows.  If all else fails, make a
brute-force attack on density codes...

Jordan, if you can get that drive to work with tosha somehow,
please let me know, so I ca add it to the regular tosha
distribution.

Regards
   Oliver

PS:  The email address that Ken mentioned isn't valid, please
use <[EMAIL PROTECTED]>.

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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, 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 messed with spl*()'s anywhere recently?

-Matt
Matthew Dillon 
<[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

[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 mode, when, e.g.
>
>  netstat -s -I bar0 -f inet6
>
>is specified. (though this is inet6 only now.)

I see where you are going now.  The syntax of netstat, already complex,
is becoming even more complex.  More detail in the man page will be
necessary soon.  Also, the "iflag" variable might have too many uses
now.  But this can wait, now that the immediate difficulties have
been resolved.

Stephen.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Matthew Dillon]

:   * First, it locks up with process 0 stuck in 'atawait' while 


I meant 'atacmd' here.

-Matt


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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,
> > thus the invalid field)
> > 
> > The second error message likely means that it needs a mode select of some
> > sort in order to function.
> 
> Hmmm.  That's another reasonable explanation for the behavior, yes. :)
> I'll try playing with different density codes, perhaps.

I think it's a 1 byte field, so you've got 256 possibilities.  It may take
a while.  Another possibility is that this is a MMC compliant CD-R drive.
cdda2wav can apparantly handle MMC drives.

>From the spec, MMC drives use a different read command that includes an
"expected sector type", which you can set to CD-DA.

Anyway, verbose output from cdda2wav might help me figure out whether that
is indeed the case.

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 
(pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0
(pass0:ahc0:0:4:0): Invalid field in parameter list

And the second:

(pass0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 20 0 0 a 0 
(pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0
(pass0:ahc0:0:4:0): Illegal mode for this track

Which is kind of interesting in that it means that the very first
command to the drive is going south, be it the mode select or (if
that's disabled) the read.

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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.

Any other SCSI CD owners here currently using tosha?  I'd be
quite interested to know if this is drive-specific.

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 it needs a mode select of some
> sort in order to function.

Hmmm.  That's another reasonable explanation for the behavior, yes. :)
I'll try playing with different density codes, perhaps.

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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.
> 
> The first produces:
> 
> (pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 
> (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0
> (pass0:ahc0:0:4:0): Invalid field in parameter list
> 
> And the second:
> 
> (pass0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 20 0 0 a 0 
> (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0
> (pass0:ahc0:0:4:0): Illegal mode for this track
> 
> Which is kind of interesting in that it means that the very first
> command to the drive is going south, be it the mode select or (if
> that's disabled) the read.

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 it needs a mode select of some
sort in order to function.

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 help determine what
cdda2wav is doing that tosha isn't.

> 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.
> 
> Any other SCSI CD owners here currently using tosha?  I'd be
> quite interested to know if this is drive-specific.

tosha works fine for me (I've got a Plextor 12x CDROM drive).  Have you
recompiled tosha between the time it worked and the time it didn't?  It
could be the problem was introduced in tosha-0.6.  (The previous version
was tosha-0.5 with CAM patches.)

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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:

* First, it locks up with process 0 stuck in 'atawait' while 
  trying to scan the CDRom on the second IDE bus.  This is after
  it has successfully scanned the hard drive on the first IDE bus. 

* Second, if I remove the 'ata1' config entry it gets past the
  initial ata probe but then locks up in 'conifhk' which is in 
  the run_interrupt_driven_config_hooks() procedure
  in kern/subr_autoconf.c

  It locks up here after printing 'waiting 15 seconds for SCSI devices
  to settle'.  Several minutes later it's still waiting :-(.

* If I remove the second ata device AND I remove the SCSI devices
  and controllers so it detects no SCSI devices, it gets all the
  way to where it says "Mounting root on wd0s4a", then gets an error 6,
  then says "Mounting root on wd0a", then just stops.  Breaking into
  DDB and doing a ps shows 'init' and 'sh' both blocked in 'wait'.
  The hard drive appears to work -- panic does sync the disks.

* The second time I did this when I CTL-ALT-ESC'd into DDB I suddenly
  got a whole bunch of console startup output.  I 'cont'd from DDB,
  and nothing... CTL-ALT-ESC'd into DDB and got some more console
  output from the normal startup sequence before it gave me the DDB
  prompt.  'cont'd. nothing.

  I got it to the point where ping works but nothing else does.


HELP!  Whats happening!!! :-( :-( :-(

At the moment I am stymied.  I switched to a GENERIC kernel and got the
same results, so it isn't anything weird that I have done in my own 
kernel config.

I was hoping that someone would have an idea. 

-Matt

Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #1: Mon Nov 29 22:10:35 PST 1999
[EMAIL PROTECTED]:/FreeBSD/FreeBSD-4.x/src/sys/compile/ARCHIVE
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 66751430 Hz
CPU: Pentium/P54C (66.75-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x524  Stepping = 4
  Features=0x1bf
real memory  = 67108864 (65536K bytes)
avail memory = 61698048 (60252K bytes)
Preloaded elf kernel "kernel.bak" at 0xc0335000.
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
ign0 at device 1.0 on pci0
isab0:  at device 2.0 on pci0
isa0:  on isab0
vga-pci0:  irq 10 at device 6.0 on pci0
xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 9 at device 12.0 on pci0
xl0: Ethernet address: 00:10:5a:e0:82:29
miibus0:  on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ncr0:  irq 11 at device 14.0 on pci0
devclass_alloc_unit: npx0 already exists, using next available unit number
fdc0:  at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0
wdc0: unit 0 (wd0): , 32-bit, multi-block-16
wd0: 12970MB (26563824 sectors), 26353 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0
wdc1: unit 0 (atapi): , removable, 
ovlap, dma, iordis
wcd0: drive speed 2066KB/sec, 128KB cache
wcd0: supported read types: CD-R, CD-DA, packet track
wcd0: Audio: play, 256 volume levels
wcd0: Mechanism: ejectable tray
wcd0: Medium: no/blank disc inside, unlocked
atkbdc0:  at port 0x60-0x6f on isa0
vga0:  at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 on isa0
sio0: type 16550A
ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
lpt0:  on ppbus 0
lpt0: Interrupt-driven port
IP packet filtering initialized, divert enabled, rule-based forwarding disabled, 
default to accept, unlimited logging
Waiting 5 seconds for SCSI devices to settle
Mounting root from ufs:wd0s4a
Root mount failed: 6
Mounting root from ufs:wd0a
link_elf: symbol splash_register undefined
cd0 at ncr0 bus 0 target 3 lun 0
cd0:  Removable CD-ROM SCSI-2 device 
cd0: 10.000MB/s transfers (10.000MHz, offset 8)
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed


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

[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 release and ship a
> > > 4.0-beta? -CURRENT = development which scares people. Beta means most bugs
> > > already ironed out and looking for test by larger audience.  -RELEASE should
> > > not be a beta, ever.
> >
> > What do you think 3.0-RELEASE was ?
> > This seems to be how FreeBSD works now.
> 
> It's how FreeBSD's users seem to want it to work, since they have utterly
> refused to cooperate with any other arrangement.  Those of us behind the
> release-engineering effort have tried everything realistic that's been
> suggested (and a great many other things); history speaks for itself as
> to the results.

Alpha, Beta, 4.0, are all just semantic labels anyhow.  Every product, or at
least every producer of software, develops their own terminology for how
software is released to "customers."  In the FreeBSD world, it has evolved
that .0 means "ready to run, but not in production" and .1 or .2 means "now
ready for prime time."  While this may differ from whatever other system you
are used to, it doesn't make it wrong, just different.

Release 4.0 won't be a beta, it will just be a .0 release.  Thank everyone
that unlike most web browsers, we at least do >.0 releases.

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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.
> 
> http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/kernel-tcp.2103
> http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/trpt.19991228

I found a bug at tcp_reass() and there might be a problem in
e.g. large file transport case.
(If tcp segments don't arrive in order it is not processed.)

I fixed the bug and using the patched machine from remote. Now
it seems to be working well.
I also simplified the patch to nfs_socket.c.
Updated patches are below. (patches to trpt is same as last version.)

  http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/kernel-tcp.2107
  http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/trpt.19991228

Please try these patches anyone interested. If it seems to be
working well also in other environment, I'll commit them into
the repository.
Thanks,

Yoshinobu Inoue


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 outlined
> > above.  It may be possible in some situations, but it was probably just a
> > fluke.
> 
> root@zippy-> tosha -t 1
> Device: /dev/cd0c -- "SAF" "CD-R8020" "1.20"
> 
>  track   playing  startend raw size  mp3 size   # of   track
>  number   timesector  sector   in bytes  128 kbps  frames  type
> -
> 13:57'58  32   17864   41943216   38052089103  audio
> error sending SCSI command: Invalid argument
> [and on the console]
> (pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 
> (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0
> (pass0:ahc0:0:4:0): Invalid field in parameter list
> 
> (I've also tried read codes 0xD4 and 0xD8 in addition to 0x28, just
>  for fun, but they were invalid ops for this drive).

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

The first one is probably what you tried.  The second one disables the mode
select.  It would be highly unusual if that drive didn't require a mode
select.  Every other drive that tosha supports that uses a standard read
command needs a mode select.  But, if your drive doesn't need a mode
select, that might explain why dd worked.

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 probably just a
> fluke.

root@zippy-> tosha -t 1
Device: /dev/cd0c -- "SAF" "CD-R8020" "1.20"

 track   playing  startend raw size  mp3 size   # of   track
 number   timesector  sector   in bytes  128 kbps  frames  type
-
13:57'58  32   17864   41943216   38052089103  audio
error sending SCSI command: Invalid argument
[and on the console]
(pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 
(pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0
(pass0:ahc0:0:4:0): Invalid field in parameter list

(I've also tried read codes 0xD4 and 0xD8 in addition to 0x28, just
 for fun, but they were invalid ops for this drive).

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 :-)

Warner


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)

[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 think that we don't want this code integrated, or
>that we don't care about it?  Have you bothered to actually read those
>sides of this discussion that have come from the release engineering team?
>
>Wouldn't it be much more sensible of you to assume that there are good 
>and valid reasons for things being the way they are?  Wouldn't it be much 
>more sensible of you to enquire as to what these reasons are, or perhaps 
>to even have paid attention to all the discussions and progress that have 
>gone on over the last few months (or even just stayed up to date in the 
>last week, where the whole matter has been discussed)?
>
>Or are you just too lazy?  Too lazy to pay attention?  Too lazy to 
>actually participate in this process?  Too lazy to do anything other than 
>to wait until it's too late to do anything, and then randomly sling blame 
>around?  What _do_ you think you achieve with this?  How do you think 
>that insulting the people that are actually trying to do the work while 
>you sit on the sidelines is going to help the process?
>
>It's been said before, and I'm sure it'll be said again; if you can't 
>or won't offer support or assistance, the very least you can do is avoid 
>being actively destructive.  Take a few moments to think about what it is 
>that you and we want to achieve, and how best to get there.  And take a 
>hint; insulting us is not how to go about it.

   Mike, I think this is just a bit over the top and doesn't belong in our
mailing lists. Please stop doing that.
   It really isn't fair to blame the FreeBSD developer base at large, and
users as well for the slowness of the integration. The KAME team has never
asked for integration help as far as I can recall and the primary reason for
the delay was actually due to their attentions being focused on NetBSD (with
the justification that they were about to freeze for a release).
   This all said, I don't think we are that far away from having a functional
IPv6 implementation in FreeBSD. Most (all?) of the stack is there and what is
needed now is the completion of support in the various system utilities. I
think this part of the merger could be completed in an amount of time that
is measured in weeks if the KAME developers can find the time to put into it
right now. If not, then this whole discussion is a waste of bandwidth and
everyone should just stop gritching over it.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.


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

[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 rest of the work?  Sorry, it might work
> * that way for hamsters but it doesn't work that way for code!  Somebody
>
>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 so i have
>full access to his computer.  (ooohh nude hamster pics)
>
>that said, i don't think you need to push back the release date.
>
>sincerely,
>fifi
>
>p.s. pardon the lack of capital letters but my paws can't quite reach
> the shift key and the alphabet keys at the same time

   If that is true, then how were you able to push the paren keys?

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.


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)

[Yoshinobu Inoue]

> 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 naturally use IPv6,
so I would also like to do it before 15th, if there are time
for it.

Yoshinobu Inoue


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 of the main reasons for springing the extra $$$ for a Plextor
is that they (unlike most other CDDA implementations) actually got
the firmware right: the beast does jitter correction in firmware,
/and/ reads at near-data speeds whilst it does it.

Many CD drives with buggy implementations jitter like crazy, and/or
won't deliver CDDA much quicker than 1x, regardless of what the
rated data speed is.


  http://www.tardis.ed.ac.uk/~psyche/cdda

is a good resource for software links and reviews of various models
of CD-ROM drives, if CD-DA ripping is of interest. Most good CDR
drives also do a good job of CD-DA ripping (Philips CDD-2000,
Toshiba CW-7502, from my direct experience), but you probably don't
want to wear 'em out doing CD-DA - at least, I know I don't ;-).

Personally, I found that tosha worked perfectly even on a Plextor
6x (the only Plextor with flawed firmware, this is pretty well-known).
:-)

Something like cdparanoia would probably be good for those cheap
IDE CD-ROMs (I bought a couple of 16x Hitachi drives cheap - they
don't do CD-DA very well at all).

Cheers,


AS



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 all that fancy jitter and scratch
>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 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...
>



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

[Warner Losh]

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 several months and would allow any
: code updates, but prevent the introduction of new features.  This
: would then be followed by a _CODE_ freeze sometime in 2000Q1, leading
: to 4.0-RELEASE late in 2000Q1.  (My understanding of the difference is
: that during the code freeze, only changes that demonstrably fix known
: bugs, without deleterious side effects, are allowed).

This was my understanding as well...  Don't feel bad.

Warner


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)

[Josef Karthauser]

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 of IPv6 _IS_ currently in 4.x if you
compile your kernel with INET6 enabled:

genius% uname -a
FreeBSD genius.systems.pavilion.net 4.0-CURRENT FreeBSD 4.0-CURRENT #32: Sun Jan  2 
18:15:42 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GENIUS  i386
genius% ifconfig -a
lp0: flags=8810 mtu 1500
lo0: flags=8049 mtu 16384
inet6 fe80:2::1 prefixlen 64 
inet6 ::1 prefixlen 128 
inet 127.0.0.1 netmask 0xff00 
ep0: flags=8843 mtu 1500
inet6 fe80:3::260:8ff:fe95:a83c prefixlen 64 
inet 10.0.0.3 netmask 0xff00 broadcast 10.0.0.255
ether 00:60:08:95:a8:3c 
media: 10baseT/UTP
supported media: 10base2/BNC 10baseT/UTP 10base5/AUI
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...]
genius% traceroute6
usage: traceroute6 [-dlnrv] [-m max_hops] [-p port#] [-q nqueries]
[-s src_addr] [-g gateway] [-w wait] host [data size]

>From route(8):
 For AF_INET6, the -prefixlen qualifier is available instead of the -mask
 qualifier because non-continuous masks are not allowed in IPv6.  For ex-
 ample, -prefixlen 32 specifies network mask of
 ::::::: to be used.  The default value of
 prefixlen is 64 to get along with the aggregatable address.  But 0 is as-
 sumed if default is specified.  Note that the qualifier works only for
 AF_INET6 address family.

I don't understand how you can say that it _isn't integrated!

Joe
-- 
Josef KarthauserFreeBSD: Take the red pill and we'll show you just how
Technical Manager   deep the rabbit hole goes. (http://www.uk.freebsd.org)
Pavilion Internet plc.  [[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Kenneth D. Merry]

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
> 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 youre reading on a plextor drive (such as
> my pxw4220t) or something else that has a native mode for extracting 
> audio.
> 
> 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...

Both tosha and cdda2wav are supported, and both work with my plextor
drives.  Why didn't tosha work with your drive?  Did you contact the author
(Oliver Fromme)?

Many of the opinions I've seen recently are that you jitter correction
isn't necessary for most newer CDROM drives.  If you want jitter
correction, you can port cdd to CAM.

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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.

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 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 probably just a
> > fluke.
> 
> root@zippy-> tosha -t 1
> Device: /dev/cd0c -- "SAF" "CD-R8020" "1.20"
> 
>  track   playing  startend raw size  mp3 size   # of   track
>  number   timesector  sector   in bytes  128 kbps  frames  type
> -
> 13:57'58  32   17864   41943216   38052089103  audio
> error sending SCSI command: Invalid argument
> [and on the console]
> (pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 
> (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0
> (pass0:ahc0:0:4:0): Invalid field in parameter list
> 
> (I've also tried read codes 0xD4 and 0xD8 in addition to 0x28, just
>  for fun, but they were invalid ops for this drive).

Okay, I just looked through the cdda2wav soure, and it appears that "SAF"
stands for "Smart and Friendly".  Apparantly some of its drives may be Sony
OEM (or act like it) and some may be Teac OEM (or act like them).  Yours
isn't listed.

See if cdda2wav (part of the cdrecord port) works with your drive.  It has
a little broader device support than tosha.

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.

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Oliver Fromme]

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 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 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...

"Port of tosha"?  Tosha is a native FreeBSD program.  :-)
BTW, it reads audio tracks off my Plextor drive at 20x - 24x
speed.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

-current or 3.4 with KAME ???

[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 FreeBSD 4.0?
-

Thanks,

Luciano Rabelo
Salvador - Bahia - Brazil




*Luciano Rabelo*
* Analista de Sistemas *
*   Salvador - Bahia - Brasil  *
*   http://www.rabelo.eti.br/  *
*  [EMAIL PROTECTED]  *
*UIN - 8642704 *


  /"\ 
  \ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML 
   X  ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL 
  / \



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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 youre reading on a plextor drive (such as
my pxw4220t) or something else that has a native mode for extracting 
audio.

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...

/k

Jordan K. Hubbard ([EMAIL PROTECTED]) @ Thu, Jan 06, 2000 at 03:47:31PM -0800:
> 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 
> (cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0
> (cd0:ahc0:0:4:0): Illegal mode for this track
> (cd0:ahc0:0:4:0): cddone: got error 0x16 back
> dscheck(#cd/2): b_bcount 512 is not on a sector boundary (ssize 2048)
> 
> and I've gotten this behavior for quite some time.  I didn't *use* to
> have this behavior, as my mpeg backups of various CDs done on this
> same machine can demonstrate, but if we can't even read data off an
> audio CD with dd then you can rest assured that utilities like tosha
> aren't going to be able to read data either, and that really sucks.
> 
> Drive information:
> 
> cd0 at ahc0 bus 0 target 4 lun 0
> cd0:  Removable CD-ROM SCSI-2 device 
> cd0: 10.000MB/s transfers (10.000MHz, offset 8)
> cd0: cd present [227322 x 2048 byte records]
> 
> Controller information:
> 
> ahc0:  irq 10 at device 4.0 on pci2
> ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs
> 
> [This is a BIOS-less Advansys controller, used exclusively for the CD
>  drive.  The machine also has dual on-board 7895 wide controllers
>  which are used just for disk in order to avoid mixing wide and narrow
>  devices in (what I consider) less-than-elegant fashion]
> 
> I also say "tell me again" because this issue isn't new and I brought
> it up back when this first broke.  Justin said it clearly wasn't his
> code, SCSI device or no, and phk intimated that maybe it had something
> to do with the blockdev stuff and then handed me several patches which
> didn't have any effect on the problem.  All I know is that my FreeBSD-current
> box has lost a powerful and popular capability and I'm more than willing
> to test patches or work with someone in fixing it.  This area of the
> kernel isn't my forte', but my love of mp3s may send me in there at
> some point if this is still broken as we get close to code freeze. :-)
> 
> - Jordan
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message

-- 
> Hackers know all the right MOVs.
http://www.nacamar.de - http://www.nacamar.net - http://www.webmonster.de 
http://www.apache.de - http://www.quakeforum.de - finger [EMAIL PROTECTED]
KR433/KR11-RIPE - PGP-KFP = F9 A0 DF 91 74 07 6A 1C  5F 0B E0 6B 4D CD 8C 44


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)

[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 think that we don't want this code integrated, or
that we don't care about it?  Have you bothered to actually read those
sides of this discussion that have come from the release engineering team?

Wouldn't it be much more sensible of you to assume that there are good 
and valid reasons for things being the way they are?  Wouldn't it be much 
more sensible of you to enquire as to what these reasons are, or perhaps 
to even have paid attention to all the discussions and progress that have 
gone on over the last few months (or even just stayed up to date in the 
last week, where the whole matter has been discussed)?

Or are you just too lazy?  Too lazy to pay attention?  Too lazy to 
actually participate in this process?  Too lazy to do anything other than 
to wait until it's too late to do anything, and then randomly sling blame 
around?  What _do_ you think you achieve with this?  How do you think 
that insulting the people that are actually trying to do the work while 
you sit on the sidelines is going to help the process?

It's been said before, and I'm sure it'll be said again; if you can't 
or won't offer support or assistance, the very least you can do is avoid 
being actively destructive.  Take a few moments to think about what it is 
that you and we want to achieve, and how best to get there.  And take a 
hint; insulting us is not how to go about it.


-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




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

[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 so i have
 > full access to his computer.  (ooohh nude hamster pics)
 
http://www.realhamster.com

- mark :-)

-- 
Mark Newton   Email:  [EMAIL PROTECTED] (W)
Network Engineer  Email:  [EMAIL PROTECTED]  (H)
Internode Systems Pty Ltd Desk:   +61-8-82232999
"Network Man" - Anagram of "Mark Newton"  Mobile: +61-416-202-223


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)

[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 they???


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)

[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 those
> > sides of this discussion that have come from the release engineering team?
> 
> Yes.  As a matter of fact, I have.

Then I'm puzzled as to which parts you haven't understood.

> 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'm sorry.  I thought you'd been keeping up to date.  There's a perfectly 
good mail archive provided by the Project for your use; I suggest that 
you'd be best served by using it to locate all the mail that you've read 
and forgotten or otherwise misunderstood.  Discussion on the state of 
the KAME integration has been going on for over a year now, and the work 
itself for well over six months.  I'm not about to do your research for 
you; I have other work to do in order to avoid being randomly flamed by 
someone else like yourself.

> Nobody is trying to insult anyone here.  Quit taking things personal.  Just
> because people are lurking doesn't mean they're not paying attention.

In your case, you're not lurking and still not paying attention.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




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)

[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 where to
> start.

First, you need a time machine.

Second, you should go back to when the KAME folks started talking about 
their integration work (that's about eight or ten months now).

Third, you should start working with them on the integration process.

Fourth, and this is probably more important since the first three are 
probably beyond your reach right now - start paying attention.  If you 
hadn't been asleep at the wheel, you'd already know all this, and the 
entire issue would be moot because you'd be helping already.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




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)

[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 assuming that everyone's completely stupid. So,
that said, stick your flame thrower where it came from and assume for one
second that I'm not completely stupid and follow your own proposed lead.

> Do you _always_ assume that anyone other than yourself is a complete
> moron? 

Where did this and all that other stuff come from?

>  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 those
> sides of this discussion that have come from the release engineering team?

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. 

Nobody is trying to insult anyone here.  Quit taking things personal.  Just
because people are lurking doesn't mean they're not paying attention.

Cheers,
Chris

-- 
Christian Kuhtz Architecture, BellSouth.net
<[EMAIL PROTECTED]> -wk, <[EMAIL PROTECTED]> -hm   Atlanta, GA
"Speaking for myself only."


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)

[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
start.

-- 
Christian Kuhtz Architecture, BellSouth.net
<[EMAIL PROTECTED]> -wk, <[EMAIL PROTECTED]> -hm   Atlanta, GA
"Speaking for myself only."


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Kenneth D. Merry]

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 in
> 0+0 records out
> 
> (cd0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 0 0 0 4 0 
> (cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0
> (cd0:ahc0:0:4:0): Illegal mode for this track
> (cd0:ahc0:0:4:0): cddone: got error 0x16 back
> dscheck(#cd/2): b_bcount 512 is not on a sector boundary (ssize 2048)
> 
> and I've gotten this behavior for quite some time.  I didn't *use* to
> have this behavior, as my mpeg backups of various CDs done on this
> same machine can demonstrate, but if we can't even read data off an
> audio CD with dd then you can rest assured that utilities like tosha
> aren't going to be able to read data either, and that really sucks.

Some drives need a special mode select command before they'll let you read
off audio blocks.  Some drives use special read CDBs for reading CDDA.
Toshiba drives, in particular, need a special mode select command before
you can read audio blocks.  After that, they use a standard read command.

In any case, the point is, reading raw audio data off a CDROM drive is not
standard across drives.  So I'm surprised that you could ever read audio
tracks off your CDROM drive using dd, or anything else that accesses the
raw/block devices.

tosha and cdda2wav should work, however, since they know about many
different kinds of drives and access methods.  They may need tweaking to
recognize the specific vendor name there, but they should work.  (tosha at
least has a nice rc file that you can use to tweak this kind of thing)

One way that this *might* have worked is if you were using some utility on
your CDROM drive that did the special mode select stuff, and didn't reset
the mode to 'normal' before you did the dd.  That could cause problems with
reading normal data CDs, however.

> Drive information:
> 
> cd0 at ahc0 bus 0 target 4 lun 0
> cd0:  Removable CD-ROM SCSI-2 device 
> cd0: 10.000MB/s transfers (10.000MHz, offset 8)
> cd0: cd present [227322 x 2048 byte records]
> 
> Controller information:
> 
> ahc0:  irq 10 at device 4.0 on pci2
> ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs
> 
> [This is a BIOS-less Advansys controller, used exclusively for the CD
>  drive.  The machine also has dual on-board 7895 wide controllers
>  which are used just for disk in order to avoid mixing wide and narrow
>  devices in (what I consider) less-than-elegant fashion]

You mean an Adaptec controller, right?

> I also say "tell me again" because this issue isn't new and I brought
> it up back when this first broke.  Justin said it clearly wasn't his
> code, SCSI device or no, and phk intimated that maybe it had something
> to do with the blockdev stuff and then handed me several patches which
> didn't have any effect on the problem.  All I know is that my FreeBSD-current
> box has lost a powerful and popular capability and I'm more than willing
> to test patches or work with someone in fixing it.  This area of the
> kernel isn't my forte', but my love of mp3s may send me in there at
> some point if this is still broken as we get close to code freeze. :-)

Like I said, I'm not sure how this ever worked properly.

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 probably just a
fluke.

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


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

[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 rest of the work?  Sorry, it might work
 * that way for hamsters but it doesn't work that way for code!  Somebody

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 so i have
full access to his computer.  (ooohh nude hamster pics)

that said, i don't think you need to push back the release date.

sincerely,
fifi

p.s. pardon the lack of capital letters but my paws can't quite reach
 the shift key and the alphabet keys at the same time


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

[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
>^^^
>You have enabled ATAPI DMA in your kernel config, dont, your
>drive apparently doesn't support it.

Oops.  It looks like I didn't read the caveats carefully enough
when I copied the options from LINT and GENERIC to my config file :-(.

Sorry for the false alarm.

Peter


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)

[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: So, tell me again why we can't read audio CDs in SCSI drives?

[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: 4.0 code freeze scheduled for Jan 15th

[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 else to make it happen. It's simply, include it even though
> it's buggy or dont.

Well, all I can say is that this represents one of the most bizarre
and frankly unrealistic perspectives I've seen for a long, long time
(well, maybe not that long - Karl's message was pretty recent, wasn't
it?).

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 rest of the work?  Sorry, it might work
that way for hamsters but it doesn't work that way for code!  Somebody
has to DO the integration and then be willing to stand behind it while
10,000 people start screaming how broken it is and how it needs to be
fixed in the following 4,891 ways.  That requires resources, resources
which even the KAME folk (who certainly know this code better than
anyone else) have been hard-pressed to provide or the IPv6/IPSec
support would already BE in FreeBSD today!

- 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

[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 v6, well most of it?
>> where's your competitive advanatge in the latter?
> Give me a break.
> Take a look at http://www.ipv6forum.org and ask yourself whether this is
> just somebody's science project.

give whom a break?

take a look at , and you
will see that i am the ietf area director for ngtrans, i.e. one of those
responsible for the ipv6 transition.

now read my question again.  there will always be new releases of freebsd,
we hope.  if v6 is not completely ready for this one, then delaying for any
considerable time will not help you compete today in the ipv6 game.

my point is that we can only wait politely and appreciatively for the kame
folk to continue their work to a point where it is more fully rounded.
until then, we should not forget that other features are also driving the
4.0 release train.

now laptoy support on the other hand 

randy


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

[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

[Julian Elischer]

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

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

[Christian Kuhtz]

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 FreeBSD.

For what it's worth, this isn't just about research in my particular case,
as I'm not part of an R&D organization or educational space but in a commercial
environment.

Will you guys please wake up and realize that things like the IPv6forum
(http://www.ipv6forum.org) aren't just somebody's science project?  Look at the
list of founding members on that page.  

There's serious demand for this stuff!  And we got code that's been in the
works for a long time, so, lets take a step and merge it.

I have a preference to use FreeBSD for this work.  However, right now it is 
more practical to go with a different OS (yes, merging external code with a
a given code tree is a significant issue).  And the longer this goes on, the 
less likely it will be that FreeBSD will be reintroduced.  That's just a fact 
of life.  Projects move forward with the exposure being given to one piece and
not another.  Result is, you've got to have really good reasons to switch
later, and most times once you set the track it's a done deal.

Or, it's actually more the one of a missed window and opportunity.  And I'm 
sure I'm not the only one in this situation.

Get IPv6 into the tree.  Now.  Thank you.

Cheers,
Chris

-- 
Christian Kuhtz Architecture, BellSouth.net
<[EMAIL PROTECTED]> -wk, <[EMAIL PROTECTED]> -hm   Atlanta, GA
"Speaking for myself only."


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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

[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 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 several months and would allow any
> code updates, but prevent the introduction of new features.  This
> would then be followed by a _CODE_ freeze sometime in 2000Q1, leading
> to 4.0-RELEASE late in 2000Q1.  (My understanding of the difference is
> that during the code freeze, only changes that demonstrably fix known
> bugs, without deleterious side effects, are allowed).
> 
> A few weeks ago, I saw comments that it had slipped a month, followed
> a few days ago by Jordan's announcement of a code freeze.
> 
> Peter
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[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

(cd0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 0 0 0 4 0 
(cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0
(cd0:ahc0:0:4:0): Illegal mode for this track
(cd0:ahc0:0:4:0): cddone: got error 0x16 back
dscheck(#cd/2): b_bcount 512 is not on a sector boundary (ssize 2048)

and I've gotten this behavior for quite some time.  I didn't *use* to
have this behavior, as my mpeg backups of various CDs done on this
same machine can demonstrate, but if we can't even read data off an
audio CD with dd then you can rest assured that utilities like tosha
aren't going to be able to read data either, and that really sucks.

Drive information:

cd0 at ahc0 bus 0 target 4 lun 0
cd0:  Removable CD-ROM SCSI-2 device 
cd0: 10.000MB/s transfers (10.000MHz, offset 8)
cd0: cd present [227322 x 2048 byte records]

Controller information:

ahc0:  irq 10 at device 4.0 on pci2
ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs

[This is a BIOS-less Advansys controller, used exclusively for the CD
 drive.  The machine also has dual on-board 7895 wide controllers
 which are used just for disk in order to avoid mixing wide and narrow
 devices in (what I consider) less-than-elegant fashion]

I also say "tell me again" because this issue isn't new and I brought
it up back when this first broke.  Justin said it clearly wasn't his
code, SCSI device or no, and phk intimated that maybe it had something
to do with the blockdev stuff and then handed me several patches which
didn't have any effect on the problem.  All I know is that my FreeBSD-current
box has lost a powerful and popular capability and I'm more than willing
to test patches or work with someone in fixing it.  This area of the
kernel isn't my forte', but my love of mp3s may send me in there at
some point if this is still broken as we get close to code freeze. :-)

- 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

[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, 
just like the rest of you.  And in fact, if you cared at all about it, 
rather than waiting until _now_ and whining about it, you could have 
noticed that they were falling behind and offered to _help_ them with 
their work in order to make the deadling.

> Now everyone is perfectly aware of the fact that -core tries to keep
> releases and FreeBSD in general as stable as possible.

Actually, -core don't do this at all.  It's the responsibility of the 
entire developer team to do it, and it's one that many of you seem to 
enjoy shirking. 
-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




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

[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 lots-o-features but not all of v6
  o release _considerably later_ with all of v6, well most of it?

where's your competitive advanatge in the latter?

randy


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP! wormcontrol and sys/dvdio.h users

[Alexander Langer]

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 the wd* drivers stay?
ata* doesn't work for me at the moment, thus I'm using the wd drivers.

Or am I wrong? Can I use burncd with the wd drivers?

Thank you.

Alex
-- 
I doubt, therefore I might be. 


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

[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 about time. Im not the one setting a deadline for
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.
Looking at the 4.4BSD Design and Implementation book you can see that on
all major releases NEW items were added, TCP/IP, VM, etc..
Now everyone is perfectly aware of the fact that -core tries to keep
releases and FreeBSD in general as stable as possible. And ultimely it's
up to david and the rest what is going in and what is not. No one is going
to argue with that. All I am saying and I think other's as well is that
leaving v6 OUT of 4.0 would possibly be a negative move for the OS.

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 else to make it happen. It's simply, include it even though
it's buggy or dont. Thats how I see it anyway. There are people who are
speaking up saying "Yes I want to see v6 in 4.0". I personally can live
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 FreeBSD.

That's all i'm saying take it for what its worth.

Chris



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

[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 that there'd be a
feature freeze from 15th December 1999.  I got the impression that
this was going to be in effect for several months and would allow any
code updates, but prevent the introduction of new features.  This
would then be followed by a _CODE_ freeze sometime in 2000Q1, leading
to 4.0-RELEASE late in 2000Q1.  (My understanding of the difference is
that during the code freeze, only changes that demonstrably fix known
bugs, without deleterious side effects, are allowed).

A few weeks ago, I saw comments that it had slipped a month, followed
a few days ago by Jordan's announcement of a code freeze.

Peter


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Problem exposed with sym driver

[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 is that the sym-driver probes the disks
as (excerpt from dmesg_sym.txt):

da1 at sym0 bus 0 target 1 lun 0
da1:  Fixed Direct Access SCSI-2 device
da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled
da1: 8715MB (1785 512 byte sectors: 255H 63S/T C)

whereas the ncr-driver probes as (excerpt from dmesg_ncr.txt):

da1 at ncr0 bus 0 target 1 lun 0
da1:  Fixed Direct Access SCSI-2 device
da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled
da1: 8715MB (1785 512 byte sectors: 255H 63S/T C)

Usually the IBM-FAQ suspects a cabling/termination Problem if one has a Problem
at 40MHZ.
But I have the 4 disks in a external case from kingston with a proper kable and
terminator and furthermore LVD-drives should have a better signal quality.
Furthermore I have zero problems at 20MHZ.

You can see in neg_before.txt the output of a 'camcontrol neg' which look right,
in neg_after.txt the output of the same command after the disk hang up and
the bus reseted.
neg_ncr.txt contains the output using the ncr-driver.

BTW: I have the same problems with the ncr-driver when using the kernel-config
parameter: SCSI_NCR_DFLT_SYNC=10 

And now the question: Whats going wrong?

If it is the HW, how can it be proven? Are it the IBM-disks? Kabel?...
Is it the Software?
If I want to live with 40MB/s is there a knob to pre-set the speed in the
kernel-config or at boot-time?

Any clues?

Bye!

Michael Reifenberger
Plaut Software GmbH, R/3 Basis


g = 2
  
Features=0x383fbff

real memory  = 268423168 (262132K bytes)
config> #flags wdc0 0xa0ffa0ff
Invalid command or syntax.  Type `?' for help.
config> #flags wdc1 0xa0ffa0ff
Invalid command or syntax.  Type `?' for help.
config> #irq isic0 10
Invalid command or syntax.  Type `?' for help.
config> #pnp 1 0 bios enable port0 0x220 irq0 5 drq0 1 drq1 3
Invalid command or syntax.  Type `?' for help.
config> #pnp 1 0 bios enable port0 0xd80 irq0 11
Invalid command or syntax.  Type `?' for help.
config> pnp 1 1 os enable irq0 5 drq0 1 port0 0x220
Invalid command or syntax.  Type `?' for help.
config> #iosiz npx0 262144
Invalid command or syntax.  Type `?' for help.
config> quit
avail memory = 256712704 (250696K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  1, version: 0x00040011, at 0xfee0
 cpu1 (AP):  apic id:  0, version: 0x00040011, at 0xfee0
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec0
Preloaded elf kernel "kernel" at 0xc0362000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc036209c.
Preloaded elf module "bktr.ko" at 0xc03620ec.
VESA: v2.0, 8192k memory, flags:0x1, mode table:0xc02f5b42 (122)
VESA: Matrox Graphics Inc.
Pentium Pro MTRR support enabled
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
vga-pci0:  irq 16 at device 0.0 on pci1
isab0:  at device 4.0 on pci0
isa0:  on isab0
pci0: Intel PIIX4 ATA controller (vendor=0x8086, dev=0x7111) at 4.1
uhci0:  irq 19 at device 4.2 on pci0
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
intpm0:  at device 4.3 on pci0
intpm0: I/O mapped e800
intpm0: intr IRQ 9 enabled revision 0
smbus0:  on intsmb0
smb0:  on smbus0
intpm0: PM I/O mapped e400 
ahc0:  irq 19 at device 6.0 on pci0
ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs
pci0: unknown card (vendor=0x10b7, dev=0x9055) at 9.0 irq 19
bktr0:  irq 18 at device 10.0 on pci0
bktr0: Hauppauge Model 61344 D121
bktr0: Detected a MSP3410D-B4 at 0x80
Hauppauge WinCast/TV, Philips FR1216 PAL FM tuner, msp3400c stereo, remote control.
pci0: unknown card (vendor=0x109e, dev=0x0878) at 10.1 irq 18
ncr0:  irq 17 at device 11.0 on pci0
isic0:  irq 16 at device 12.0 on pci0
isic0: Error, IPAC version 2 unknown!
device_probe_and_attach: isic0 attach returned 6
isa0: too many memory rangesfdc0:  at port 0x3f0-0x3f7 irq 6 drq 
2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0:  at port 0x60-0x6f on isa0
atkbd0:  irq 1 on atkbdc0
vga0:  at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
sio2: configured irq 19 not in bitmap of probed irqs 0
sio3: configured irq 19 not in bitmap of probed irqs 0
ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0
ppc

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

[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 tonight and see if it breaks
anybody.

Warner


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

[Mike Smith]

> 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? -CURRENT = development which scares people. Beta means most bugs
> > already ironed out and looking for test by larger audience.  -RELEASE should
> > not be a beta, ever.
> 
> What do you think 3.0-RELEASE was ?
> This seems to be how FreeBSD works now.

It's how FreeBSD's users seem to want it to work, since they have utterly
refused to cooperate with any other arrangement.  Those of us behind the 
release-engineering effort have tried everything realistic that's been 
suggested (and a great many other things); history speaks for itself as 
to the results.


-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA driver problems

[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 request to the underlying driver.
2) The ata-disk driver doesn't check for (and ignore) zero-length
   requests, instead passing them onto the disk.

See kern/15956 for details and patches.

Peter


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

HEADS UP! wormcontrol and sys/dvdio.h users

[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 soon.

-Søren


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

[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 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.

-- 
-- David([EMAIL PROTECTED])


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

[Warner Losh]

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 something like this, I'm reporting second hand
stuff).

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

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

[Jesper Skriver]

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
> installed system, there was no pccard support, and the ep0 device wasn't
> found, wouldn't it be smart to install a kernel with support for pccard,
> when installing from the pccard floppies ?

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.

/Jesper

-- 
Jesper Skriver, jesper(at)skriver(dot)dk
Work:Network manager @ AS3292 (Tele Danmark DataNetworks)
Private: Geek@ AS2109 (A much smaller network ;-)

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.


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

[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 support until 4.1 or 4.2, given Warner's work situation.

I think that Matt Dodd will be working on this.  We's waiting for
hardware that is on order before he can complete fixing this.  I
strongly suspect that he'll be able to fix it within a few hours of
the arrival of the hardware.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

PCCARD - after installing a snapshot, no pccard support

[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, wouldn't it be smart to install a kernel with support for pccard,
when installing from the pccard floppies ?

/Jesper

-- 
Jesper Skriver, jesper(at)skriver(dot)dk
Work:Network manager @ AS3292 (Tele Danmark DataNetworks)
Private: Geek@ AS2109 (A much smaller network ;-)

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.


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

[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]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


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

[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 community though.
> 

Speaking with my Infrastructure Services hat on, if 4.0 supported
IPsec on IPv4 I would deploy FreeBSD more widely.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

rlogind message in /var/log/messages

[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 10:56:17 idli rlogind[1806]: PAM authentication failed

in /var/log/messages each time I do a remote login (using rsh or rlogin). Can
this problem be fixed for the FreeBSD-4.0 release if possible. Thanks,



- Mohit


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

[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) and go with NetBSD where my 3c589d works
> > just fine.
> > 
> 
> My 3c589d works just fine now, along with suspend/resume :)  (under 4.0).
> 

  And these are also working perfectly for me as well under -current on a
ThinkPad 770.

Tom




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

[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 think people will notice much when you introduce new protocol stacks
in minor releases (.1, .2, etc)?  If you dispute that, perhaps you're due for
a routine reality check.

Cheers,
Chris

-- 
Christian Kuhtz Architecture, BellSouth.net
<[EMAIL PROTECTED]> -wk, <[EMAIL PROTECTED]> -hm   Atlanta, GA
"Speaking for myself only."


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

[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.
> 

My 3c589d works just fine now, along with suspend/resume :)  (under 4.0).

Joe
-- 
Josef KarthauserFreeBSD: Take the red pill and we'll show you just how
Technical Manager   deep the rabbit hole goes. (http://www.uk.freebsd.org)
Pavilion Internet plc.  [[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: mergemaster(8) busted

[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 instead of chown to change
ownership of device nodes now.  You should probably build world
before you sync /etc, anyway. 

-Chris
-- 
[EMAIL PROTECTED]   [EMAIL PROTECTED]
Abbotsford, BC, Canada


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

[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 actually being a
>wide beta so that some code can get a workout.

Who said anything about -RELEASE being a beta ?  Some parts of a release
will always be new, but the majority of it is the same code we released
as 3.X, 2.X and even 1.X.

We need for people to stop thinking of FreeBSD as commercial software
which comes in "natural number" style enumerable packets.

FreeBSD style is "real number", it is a continuously evolving
quantity which every now and then passes a natural number on the
way to infinity.

We can now spot a milestone called 4.0 and that's very nice, but we
are not going to stop, because the road goes on past 4.0.


I'm sorry you you can't have ${insert pet feature here} in 4.0 if
it is not ready yet.  That's too bad, check in later.

In the meantime please enjoy:

NTFS filesytem

Netware support

Jail facility

Tons of new device drivers

Netgraph

etc, etc

Isn't that just that very incomplete list worth a release ?

FreeBSD-4.0 because now the time is right!

Poul-Henning


--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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

[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 way.
> 
> 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.

For the short term the impact will be nill , zero , nada... Is not like companies
get hold of a new technology and instantly start deploying it -- it will take 
some time ;specially, nowdays after a lot of companies are getting somewhat
of a relief from Y2K work or scare  

With respect to FreeBSD people can always get an upgrade or cvsup . They
want more ? Talk to  JKH I am sure is willing to strike a sweet deal 8)








-- 

 Amancio Hasty
 [EMAIL PROTECTED]




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

[Darren Reed]

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.

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.

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.

Darren


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

[Mr. K.]

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. Any reason not to release and ship a
> > 4.0-beta? -CURRENT = development which scares people. Beta means most bugs
> > already ironed out and looking for test by larger audience.  -RELEASE should
> > not be a beta, ever.
> 
> What do you think 3.0-RELEASE was ?
> This seems to be how FreeBSD works now.
> 
There really isn't an alternative.  If there were thousands of people
begging for beta code to test and we decided to just call it a release,
that would be a different story, but there aren't.



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

[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? -CURRENT = development which scares people. Beta means most bugs
> already ironed out and looking for test by larger audience.  -RELEASE should
> not be a beta, ever.

What do you think 3.0-RELEASE was ?
This seems to be how FreeBSD works now.

Darren


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

[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 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 support until 4.1 or 4.2, given Warner's work situation.
-- 
Frank Mayhar [EMAIL PROTECTED]


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

[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 primary committer has already expressed his
opinion on what can and can't be done by 1/15.

> 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 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? -CURRENT = development which scares people. Beta means most bugs
already ironed out and looking for test by larger audience.  -RELEASE should
not be a beta, ever.

-Steve


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

[Matthew Dillon]

:> 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 FreeBSD is chasing the wrong goals, IMHO.
:
: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.
:
:Chris

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.

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.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


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

[scanner]

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 that doesn't
> happen, then FreeBSD is chasing the wrong goals, IMHO.

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.

Chris



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: patches for SMP

[Mohit Aron]

> 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 to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: patches for SMP

[Luoqi Chen]

> 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). If these haven't
> been applied already, can someone please apply them so that the FreeBSD-4.0
> release scheduled for January 15th has this bug removed.
> 
> 
> 
> - Mohit
> 
That "someone" was me :-) I'll commit it before the deadline.

-lq


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: BOOTP and IPFIREWALL

[Doug Ambrisko]

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 IPFIREWALL
| in a BOOTP-loaded machine, there are good reasons for it...

They are not really incompatible just your use is :-)  Add 
  options IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default
to your kernel.  IPFW stuff is blocking any network traffic.  So add
this to your kernel and you firewall will default to open so BOOT etc
will work (including nfs mounting of root & swap), then during the 
boot use the rc.firewall stuff to setup the firewall correct and then
remove the default open rule.

This is what I've done when playing with natd on a netbooted machine.
(natd require ipfw & divert).

If this fails it's news to me.

Doug A.


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

[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 functionality, ple
> 
> Sadly, you've picked a particular bit of technology that we've been
> waiting more than a year for.  If I had any assurance that a couple of
> months would make a difference for KAME, I might even contemplate that
> as a strong option, but they don't work to those kinds of schedules.
> Based on past experience, it could easily be another year before the
> KAME group is ready with everything you're asking for.  Should we wait
> a year?  Clearly not, and we have to make our schedules independently
> of the long-term project groups or we'll never release anything.
> 
> - Jordan

That is true, and has always been true. Things get done when people are ready to
get them done and not before.

Rob


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

[Jordan K. Hubbard]

> 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 that we've been
waiting more than a year for.  If I had any assurance that a couple of
months would make a difference for KAME, I might even contemplate that
as a strong option, but they don't work to those kinds of schedules.
Based on past experience, it could easily be another year before the
KAME group is ready with everything you're asking for.  Should we wait
a year?  Clearly not, and we have to make our schedules independently
of the long-term project groups or we'll never release anything.

- 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

[Jordan K. Hubbard]

> 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 Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message