> On Wed, 23 Jun 1999, Doug wrote:
>
> > First a question, namely what is the current state of the ATA
> > drivers in -current? Are they reliable (where "reliable" goes by -current
> > terms obviously)? I finally am in a position to test them with a new
> > workstation that has IDE disks, so
find /usr/src -name \*.c | xargs grep DEV_DRIVER_MODULE
and check the changes on that file.
For your reference, the changes that have recently been made to ugen.c
with respect to the cdevsw thingies:
RCS file: /home/ncvs/src/sys/dev/usb/ugen.c,v
retrieving revision 1.12
retrieving revision 1.1
It seems Michael Class wrote:
> > On Wed, 23 Jun 1999, Doug wrote:
> >
> > > First a question, namely what is the current state of the ATA
> > > drivers in -current? Are they reliable (where "reliable" goes by -current
> > > terms obviously)? I finally am in a position to test them with a new
>
Some interesting comments from an interesting source.
BTW. I'd appreciate it if everyone noticed how friendly and helpful Linus
is and Not find some thing to rag on linux about with this. The aim of
this thread is to improve FreeBSD in any way we see as being a real
improvement. Don't cc him bac
Nine'th update to the new ATA/ATAPI driver:
The atapi subsystem has gotten better error handeling and timeouts,
it also tries a REQUEST SENSE command when devices returns errors,
to give a little more info as to what went wrong. It might be a
little verbose for now, but I'm interested in as muc
On Thu, Jun 24, 1999 at 07:42:59PM -0700, JMS Internet <[EMAIL PROTECTED]>
wrote:
> I recently purchased a Intel Pro 100+ Server Adapter
> for my FreeBSD machine (3.1), but I can't find any information if it is
> supported,
> or not... I'm also not sure which driver I would use for it.. I
[EMAIL PROTECTED] wrote:
>
>Are there any plans to port FreeBSD to the IA-64 architecture when it
>comes out? The docs have recently been released
> http://developer.intel.com/design/ia64/architecture.htm
>so I was wondering if anyone had a chance to look at the stuff.
When I looked a coupl
> 1) a cross-reference to http://www.freebsd.org/FAQ/FAQ243.html#246
>in the docs in /usr/src/release is useful!
>
> how about adding one to the Makefile
>
> 2) you can't always do a make release without 1:1 agreement between
>your runtime state and the CVS and /usr/src repositarie
I just noticed that traceroute in -current is starting its probes
with port 1 instead of 33435 as it is supposed to do:
tcpdump: listening on fxp0
09:05:03.527313 206.213.73.12.38947 > 204.216.27.21.1: udp 12 [ttl 1]
09:05:03.532569 206.213.73.12.38947 > 204.216.27.21.2: udp 12 [ttl 1]
09:05:03.5
I've come across several instances where I need to fiddle with state that
is also touched by a timeout handler. From a naming standpoint,
splsoftclock() sounds like the correct spl routine to use for protecting
these activities. Unfortunately this only holds true if splsoftclock()
is used in a p
I've come across several instances where I need to fiddle with state that
is also touched by a timeout handler. From a naming standpoint,
splsoftclock() sounds like the correct spl routine to use for protecting
these activities. Unfortunately this only holds true if splsoftclock()
is used in a p
[ Sorry for the duplicate message for some of you. I botched the headers
on the original mail. ]
I've come across several instances where I need to fiddle with state that
is also touched by a timeout handler. From a naming standpoint,
splsoftclock() sounds like the correct spl routine to use
Why have splr semantics? That is, it raises to splsoftclock if current
priority is lower, else doesn't fiddle with it.
On Fri, 25 Jun 1999, Justin T. Gibbs wrote:
> I've come across several instances where I need to fiddle with state that
> is also touched by a timeout handler. From a naming s
Trying the updated driver, I notice that the first time I try
to mount the cdrom drive, it hangs, I hit ^C and get this
error:
atapi_error: PREVENT_ALLOW - timeout error = 00
After that, I can mount it fine. This system is all SCSI except
for the cdrom, which is a generic 6x IDE cdrom drive.
H
What is the device node that is used to access the cdrom in ATA?
/dev/acd0c doesnt seem to work, although that is the one specified in
dmesg
acd0: CDROM drive at ata0 as slave
acd0: drive speed 4125KB/sec, 128KB cache
acd0: supported read types: CD-R, CD-RW, CD-DA
acd0: Audio: play, 256 volume l
[ I've dropped [EMAIL PROTECTED] based on a request from Theo since
he cannot post back to some of these lists. ]
>Why have splr semantics? That is, it raises to splsoftclock if current
>priority is lower, else doesn't fiddle with it.
This is what I meant to suggest, but if this is not doable,
It seems Neal Westfall wrote:
> Trying the updated driver, I notice that the first time I try
> to mount the cdrom drive, it hangs, I hit ^C and get this
> error:
>
> atapi_error: PREVENT_ALLOW - timeout error = 00
>
> After that, I can mount it fine. This system is all SCSI except
> for the cd
On Fri, 25 Jun 1999, Soren Schmidt wrote:
> > atapi_error: PREVENT_ALLOW - timeout error = 00
> >
> > After that, I can mount it fine. This system is all SCSI except
> > for the cdrom, which is a generic 6x IDE cdrom drive.
>
> Hmm, that is a little wierd since:
>
> > Here is the relevant pro
Here is the complete output of dmesg in case it is helpful:
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 #106: Fri Jun 25 10:00:44 PDT 1999
[EMAIL PROTECTED
On Thu, 24 Jun 1999, Stephen J. Roznowski wrote:
> On 24 Jun, Nick Hibma wrote:
> >
> > The logfile for CRON is in the wrong place IMHO. It's in /var/cron/log.
> > The FreeBSD style is to put those things in /var/log (/var/log/cron).
> >
> > Anyone any opinions on this? Which scripts depend on
I'm working on restoring ctm finally (now the disk is working, and the
extra room is terrific!)
I am going to do things manually for a short while, so the interval of
things is going to be unpredictable, but I'd consider it a favor if,
when you get a ctm, you email me directly. Keep the ctm stuf
I was working on my com console stuff and when I went into
/sys/i386/boot and did a 'make all install clean' to rebuild my boot
blocks (after changing /etc/make.conf) it fails due to an error in the
netboot sub directory. I don't need netboot so I just deleted it
temporarily in the makefil
I set up a serial console on my -current box and putting "-P" in
/boot.config worked just fine, but I'd really like to use the new loader
and such, plus according to the man page for loader /boot.config is
deprecated. The only problem is I couldn't figure out where exactly this
option shou
It'd be interesting to see where FreeBSD stacks up
-- Forwarded message --
Date: 25 Jun 1999 17:00:02 -0400
From: Ramana Juvvadi <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: NT vs Linux benchmark saga continues
http://www.zdnet.com/pcweek/stories/news/0,4153,1015266
[cd image making code removed]
Bewdiful. just what the docter ordered.
thanks!
-George
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
John Polstra wrote:
>
> I just noticed that traceroute in -current is starting its probes
> with port 1 instead of 33435 as it is supposed to do:
>
> tcpdump: listening on fxp0
> 09:05:03.527313 206.213.73.12.38947 > 204.216.27.21.1: udp 12 [ttl 1]
>
> It broke in revision 1.9 of "src/contrib/tr
Karl Pielorz writes:
> > I just noticed that traceroute in -current is starting its probes
> > with port 1 instead of 33435 as it is supposed to do:
> >
> > tcpdump: listening on fxp0
> > 09:05:03.527313 206.213.73.12.38947 > 204.216.27.21.1: udp 12 [ttl 1]
> >
> > It broke in revision 1.9 of "sr
>>Why have splr semantics? That is, it raises to splsoftclock if current
>>priority is lower, else doesn't fiddle with it.
splsoftclock() has always had spllower() semantics, and its main users
(kern_clock.c and kern_time.c) depend on this.
FreeBSD has a precedent of not changing poor spl names
> >>Why have splr semantics? That is, it raises to splsoftclock if current
> >>priority is lower, else doesn't fiddle with it.
>
> splsoftclock() has always had spllower() semantics, and its main users
> (kern_clock.c and kern_time.c) depend on this.
Okay. Then Justin's suggestion of splcallout
> I was working on my com console stuff and when I went into
> /sys/i386/boot and did a 'make all install clean' to rebuild my boot
> blocks (after changing /etc/make.conf) it fails due to an error in the
> netboot sub directory. I don't need netboot so I just deleted it
> temporarily in the
Hi all,
I did a cvsup on the night of June 24/25, got the world built,
installed, /etc updated, the kernel config file updated, built
the kernel, updated it, and when I attempt to boot, I get the
following error:
.: Out of file descriptors
This is shortly after the "
>
>
>Hi all,
>
>I did a cvsup on the night of June 24/25, got the world built,
>installed, /etc updated, the kernel config file updated, built
>the kernel, updated it, and when I attempt to boot, I get the
>following error:
>
> .: Out of file descriptors
You copied /e
From: Bruce Burden <[EMAIL PROTECTED]>
>I did a cvsup on the night of June 24/25, got the world built,
>installed, /etc updated, the kernel config file updated, built
>the kernel, updated it, and when I attempt to boot, I get the
>following error:
>
> .: Out of file descriptors
>
C
On Fri, 25 Jun 1999, Mike Smith wrote:
> > I was working on my com console stuff and when I went into
> > /sys/i386/boot and did a 'make all install clean' to rebuild my boot
> > blocks (after changing /etc/make.conf) it fails due to an error in the
> > netboot sub directory. I don't need net
On Fri, 25 Jun 1999 13:13:20 MST, Doug wrote:
> I can submit patches for the man page(s) if I can get a grip on what's
> happening where (and when). :-/ What I'd really like to see is a
> chronological listing, like:
I think you're reading the wrong manpage. I've just had a look at
loader(8)
On Fri, 25 Jun 1999 18:46:05 MST, Doug wrote:
> Where would I go if I wanted to rebuild my boot blocks to make the
> com console run at a different speed, or is this something I could set
> with one of the voluminous conf files in /boot, or??
Try src/sys/boot ?
Tip for the future: When you ne
I've tried numerous times (updating the kernel, buildworld, etc) to get
gdb to work, but so far it seems like ELF coredumps are broken (course
this could be a C++ issue too):
zippy:~#gdb `which konqueror` konqueror.core
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free softwa
37 matches
Mail list logo