> > > I notice that in the last 6 months a change has occurred in how we use
> > > our cvs tools, in that there's a great increase in the usage of tags.
>
> Would you mind giving one example where not having tags hurt us?
Sure. When multiple developers are trying to work together as well as
tra
On Mon, 21 Jun 1999, Nate Williams wrote:
> > > > I notice that in the last 6 months a change has occurred in how we use
> > > > our cvs tools, in that there's a great increase in the usage of tags.
> >
> > Would you mind giving one example where not having tags hurt us?
>
>
> Sure. When multi
On Sun, 20 Jun 1999, Justin T. Gibbs wrote:
> It looks like isa/sio.c still won't allow you to set a port as both
> a low-level console and the gdb port. I could not get remote gdb
> to work correctly after the sio probe without designating the port
> for low-level console I/O. Now that I've d
Matthew Dillon wrote:
>
> Here's the location:
>
> http://www.backplane.com/FreeBSD4/
>
> It's in the 'NFS bugs first found by David E. Cross' section.
>
I've looked it over a bit and can't see any major problems..
and it definitly does fix some problems..
Has anyone tried i
I have not tested, but I also gave it a very good look, and it looks solid.
I would certainly like to see it in -current for some real life testing
and then MFC-ed at the earliest convience :).
Currently we are running off of some patches that I have written... that
scares me, alot :) I would l
> I get very stubborn when I'm given (what appears to me to be) a bogus
> argument, even if the ultimate conclusion is right. The reason given
> for the conclusion has to hold water.
I figured somebody else would jump on this one, which is why I never
bothered to respond myself. :)
- Jordan
T
I have 3 AHC devices that work great under -STABLE, but -CURRENT doesn't
even acknowledge they exist. GENERIC kernels on both. Here is the boot
information from the working -STABLE system:
Probing for devices on PCI bus 1:
ahc0: rev 0x00 int a irq 21 on pci1.4.0
ahc0: aic7890/91 Wide Channel
David E. Cross wrote...
> I have 3 AHC devices that work great under -STABLE, but -CURRENT doesn't
> even acknowledge they exist. GENERIC kernels on both. Here is the boot
> information from the working -STABLE system:
>
> Probing for devices on PCI bus 1:
> ahc0: rev 0x00 int a irq 21 on pci
Oliver Fromme <[EMAIL PROTECTED]> wrote:
> This sounds like a bug in the device driver.
If it is, then the driver succeeds into getting the card into a state it
can't recover from. I rebooted and the problem persisted. It actually
took a powercycle to make the card operational again.
I'll see w
In the next few hours I will commit a bunch of changes to syscons
console driver. This is the second phase of syscons reorganization.
Here are some warnings :)
1) Because a few new files will be added to the source tree, you will
need to run config(8) on your kernel configuration file before
co
Julian Elischer writes:
> Matthew Dillon wrote:
> >
> > Here's the location:
> >
> > http://www.backplane.com/FreeBSD4/
> >
> > It's in the 'NFS bugs first found by David E. Cross' section.
> >
>
>
> I've looked it over a bit and can't see any major problems..
>
Doug White schrieb:
>
> Some PC BIOSes won't boot a disk without a MS partition table. Try
> booting a dangerously dedicated disk on a Phoenix machine and you'll see
> what I mean.
Hmm, I remember having exact this problem with a machine (Phoenix BIOS).
After some hacks to the secondary boot I
Julian Elischer writes:
> Matthew Dillon wrote:
> >
> > Here's the location:
> >
> > http://www.backplane.com/FreeBSD4/
> >
> > It's in the 'NFS bugs first found by David E. Cross' section.
> >
>
>
> I've looked it over a bit and can't see any major problems..
>
Ok I 've incorporated that into the patch set I have ready to commit..
I've also been playing in 3.x
The patches apply almost cleanly there, except for 3 small problems that
I'm fixing by hand..
I'll then make a 3.x version of the patches available.
Hopefully people can start testing that..
jul
I'll be happy to test a 3.2-STABLE version of the patches as soon as they
become available.
Tom
On Tue, 22 Jun 1999, Julian Elischer wrote:
> Ok I 've incorporated that into the patch set I have ready to commit..
> I've also been playing in 3.x
>
> The patches apply almost cleanly there, exc
As I said on -hackers..
>
> There is a backported version of MAtt's NFS fixes at:
>
> ftp://ftp.whistle.com/pub/julian/nfs-3.diffs
>
> These include Andrew's fix to the fix
>
> results apreciated.
> If you've been having NFS server side problems on 3.x check these out..
>
> julian
>
>
On
The recent patches include a reference to "strerr()" in kernel mode... there
is no such beast.
--
David Cross | email: [EMAIL PROTECTED]
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
Rensselaer Polytechnic Institute, | Ph: 5
On Tuesday, 22 June 1999 at 17:14:29 -0400, David E. Cross wrote:
> The recent patches include a reference to "strerr()" in kernel mode... there
> is no such beast.
Ugh. Fixed. That's what you get for compiling before I've enabled it.
Greg
--
See complete headers for address, home page and pho
Ok, now that you have fixed the strerr() bug, I have another -current
vinum dilema...
I have 3 disks... da0, da1, and da2. da0 has a 100M /, 200M /var,
2048M /usr, 512M swap. each of da1 and da2 have 512M swap.
I have a vinum config similiar to:
disk drive1 /dev/da0s1h
disk drive2 /dev/da1s1h
On Tuesday, 22 June 1999 at 22:14:55 -0400, David E. Cross wrote:
> Ok, now that you have fixed the strerr() bug, I have another -current
> vinum dilema...
>
> I have 3 disks... da0, da1, and da2. da0 has a 100M /, 200M /var,
> 2048M /usr, 512M swap. each of da1 and da2 have 512M swap.
> I have
Hello Greg,
If I may intrude in this discussion, I was wondering what is the correct
syntax for naming vinum drives in rc.conf.
I've got two drives merged and striped with vinum, but I'm not sure what
to put in rc.conf
vinum_conf :
drive drive1 device /dev/wd1s1h
drive drive2 device /dev/wd2s1h
On Wednesday, 23 June 1999 at 7:33:35 +0200, Thierry Herbelot wrote:
> Greg Lehey wrote:
>>
>
> [SNIP]
>
>> I've also changed the names of the drives. With the old ones, you
>> won't be able to start the volume after a reboot. To quote vinum(8):
>>
>> drive name option
>>
>>Def
Neither is correct, you want to leave the parition identifier ("h") off of
it. When vinum starts it scans all the partitions by attempting to add
one of [abdefgh] to the end of whatever you give it. If you give it
"wd0s1h" it will look for "wd0s1ha ... wd0s1hh" and never find it.
--
David Cros
On Wednesday, 23 June 1999 at 1:50:19 -0400, David E. Cross wrote:
> Neither is correct, you want to leave the parition identifier ("h") off of
> it. When vinum starts it scans all the partitions by attempting to add
> one of [abdefgh] to the end of whatever you give it. If you give it
> "wd0s1
Using a recent (few days) -current I had a process lock up on me
last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a
while. When I issued a 'ktrace -C' in another screen, everything froze and
the kernel panic'ed. I dropped to the debugger on the console and it was
def
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 I thought I'd give it a go.
Also, I was t
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 I thought
On Wed, 23 Jun 1999, Brian F. Feldman 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
On Wed, 23 Jun 1999, Doug wrote:
> On Wed, 23 Jun 1999, Brian F. Feldman 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)
On Wed, 23 Jun 1999, Doug wrote:
> Using a recent (few days) -current I had a process lock up on me
> last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a
> while. When I issued a 'ktrace -C' in another screen, everything froze and
> the kernel panic'ed. I dropped to th
>For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course,
>I'm happy with the atapi-fd driver :) See:
UDMA mode 2 is normal 33 MB/sec UDMA mode and has been supported by the
old driver for about 2 years now (although not for all chipsets).
Bruce
To Unsubscribe: send mail t
On Thu, 24 Jun 1999, Bruce Evans wrote:
> >For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course,
> >I'm happy with the atapi-fd driver :) See:
>
> UDMA mode 2 is normal 33 MB/sec UDMA mode and has been supported by the
> old driver for about 2 years now (although not for
On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote:
> Using a recent (few days) -current I had a process lock up on me
> last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a
> while. When I issued a 'ktrace -C' in another screen, everything froze and
> the kernel p
On Thu, 24 Jun 1999, Greg Lehey wrote:
> On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote:
> > Using a recent (few days) -current I had a process lock up on me
> > last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a
> > while. When I issued a 'ktrace -C' in anoth
On Wednesday, 23 June 1999 at 18:11:21 -0700, Doug wrote:
> On Thu, 24 Jun 1999, Greg Lehey wrote:
>
>> On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote:
>>> Using a recent (few days) -current I had a process lock up on me
>>> last night, so I did a 'ktrace -p whateverthepidwas' and le
I have a problem with the way my soundcard behaves. It stutters when using
mpg123, where a small segment of music is played a number of time before
moving onto the next segment. Looking at the code, I see that the DMA is set
up in auto mode. I can only surmise that interrupts are not being ser
Oops, forgot my pnpinfo output
Checking for Plug-n-Play devices...
Card assigned CSN #1
Vendor ID CSC4236 (0x3642630e), Serial Number 0x
PnP Version 1.0, Vendor Version 5
Device Description: Crystal Codec
Logical Device ID: CSC 0x630e #0
Device Description: WSS/SB
TAG Start
Maybe I didn't get all the changes. I'm going to cvsup again and check.
Thanks,
ed
cc -nostdinc -O -pipe
-I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes
-I/usr/src/sbin/dhclient/../../contrib/isc-dhcp
-I/usr/obj/usr/src/tmp/usr/include -static -o dhclient clparse.o
dhclient.o alloc
Can some one back out the recent commits in usr.sbin/pkg_install
that adds ? to getopt(3) optarg string?
--
Steve
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried
every variation of the kernel I can think of, including GENERIC, and same
thing. I finally changed to vt0 and it booted up fine.
I am using the standard sio0 config with the 0x10 flag and a /boot.config
file with "-h".
C
Grrr, forgot the trap information:
>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried
every variation of the kernel I can think of, including GENERIC, and same
thing. I finally changed to vt0 and it booted up fine.
I am using the standard sio0 config with the 0x10 flag a
>>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried
>every variation of the kernel I can think of, including GENERIC, and same
>thing. I finally changed to vt0 and it booted up fine.
A bug was found earlier today in syscons_isa.c. Apply the following
patch to /sys/isa/s
That fixed it. Thanks!
Tim
On Thu, Jun 24, 1999 at 04:44:50PM +0900, Kazutaka YOKOTA wrote:
> >>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried
> >every variation of the kernel I can think of, including GENERIC, and same
> >thing. I finally changed to vt0 and it b
On Wed, 23 Jun 1999 14:16:23 MST, Doug wrote:
> If you are saying that I ought to include atapicd in my kernel config
> and use the acdN device node, that's all I need to know, but it does
> bring up the question of why the two things are different. It seems
> like unecessary obfuscation to me.
Doug <[EMAIL PROTECTED]> writes:
> On Wed, 23 Jun 1999, Brian F. Feldman wrote:
> > A device name isn't necessarily the same as a device node, you know.
> Actually I do know that, but I've never come across a situation in
> freebsd where I would call something one thing in my kernel config f
"Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> I didn't mean that mode 2 was special, but Ultra DMA mode 2 in its entirety being
> very nice :) The old driver never did any form of DMA for me, much less UDMA, so
> I'm very glad to have the ATA drivers.
controller wdc0 at isa? port IO_WD1 irq 14
Hi Ed,
>
> cc -nostdinc -O -pipe
> -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes
> -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp
> -I/usr/obj/usr/src/tmp/usr/include -static -o dhclient clparse.o
> dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o hash.o
> icm
Hi all,
Has this problem been fixed?
===> sbin/ifconfig
cc -O -pipe -DUSE_IF_MEDIA -DUSE_VLANS -DNS -Wall -Wmissing-prototypes -Wcast-qual
-Wwrite-strings -Wnested-externs -I.. -c /omni/usr/src/sbin/ifconfig/ifconfig.c
/omni/usr/src/sbin/ifconfig/ifconfig.c: In function `status':
/
Dag-Erling Smorgrav wrote:
>
> Doug <[EMAIL PROTECTED]> writes:
> > On Wed, 23 Jun 1999, Brian F. Feldman wrote:
> > > A device name isn't necessarily the same as a device node, you know.
> > Actually I do know that, but I've never come across a situation in
> > freebsd where I would call s
Make sure you install the include files.
In message <[EMAIL PROTECTED]>, Bruce Burden write
s:
>
> Hi all,
>
> Has this problem been fixed?
>
>===> sbin/ifconfig
>cc -O -pipe -DUSE_IF_MEDIA -DUSE_VLANS -DNS -Wall -Wmissing-prototypes -Wcast-qual
>-Wwrite-strings -Wnested-externs -I.. -
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 that location?
Nick
http://www.freebsd.org/cgi/query-pr.cgi?pr=7682
To Unsubscribe: send mail t
On 24 Jun 1999, Dag-Erling Smorgrav wrote:
> "Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> > I didn't mean that mode 2 was special, but Ultra DMA mode 2 in its entirety being
> > very nice :) The old driver never did any form of DMA for me, much less UDMA, so
> > I'm very glad to have the ATA
> Are there any plans to port FreeBSD to the IA-64 architecture when it comes
> out? The docs have recently been released
There have been plans to do this for as long as Intel has had plans to
make the processor. :)
The question will simply come down to hardware availability and
documentation.
It seems Jordan K. Hubbard wrote:
> > Are there any plans to port FreeBSD to the IA-64 architecture when it comes
> > out? The docs have recently been released
>
> There have been plans to do this for as long as Intel has had plans to
> make the processor. :)
>
> The question will simply come d
>controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff
>
>Will enable DMA mode with the old driver. It doesn't support UDMA on
>all chipsets (e.g. ALI), and in some cases may give very poor
Not e.g. ALI (Aladdin IV/V) (unless the ALI support is broken).
>performance when using UDMA disks,
On Fri, 25 Jun 1999, Bruce Evans wrote:
> >controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff
> >
> >Will enable DMA mode with the old driver. It doesn't support UDMA on
> >all chipsets (e.g. ALI), and in some cases may give very poor
>
> Not e.g. ALI (Aladdin IV/V) (unless the ALI supp
Bruce Evans <[EMAIL PROTECTED]> writes:
> >controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff
> >
> >Will enable DMA mode with the old driver. It doesn't support UDMA on
> >all chipsets (e.g. ALI), and in some cases may give very poor
>
> Not e.g. ALI (Aladdin IV/V) (unless the ALI suppo
You misunderstand. I _cannot_ disable UDMA in my BIOS.
Brian Fundakowski Feldman _ __ ___ ___ ___ ___
[EMAIL PROTECTED] _ __ ___ | _ ) __| \
FreeBSD: The Power to Serve!_ __ | _ \._ \ |) |
http://www.FreeBSD.org/ _ |___/___/___/
"Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> You misunderstand. I _cannot_ disable UDMA in my BIOS.
I know. The mail you answered wasn't addressed to you.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in th
Hello,
Sorry for being annoying but is there still anything wrong with CTM
generation? The last src-cur delta was from 8th of June.
Regards,
Vladimir
===|===
Vladimir Kushnir |
[EMAIL PROTECTED], |Powered by FreeBSD
[EMAIL PR
I'm working on a fix to PR kern/12265 (panic when trying to RTM_GET
the default route while there is none).
The problem is that in route_output(), in that case, rn_lookup()
returns the root node of the radix table (he got it from rn_match()),
while the code expects NULL or a node with an AF_INET
On 24 Jun 1999, Dag-Erling Smorgrav wrote:
> "Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> > You misunderstand. I _cannot_ disable UDMA in my BIOS.
>
> I know. The mail you answered wasn't addressed to you.
*apologies*. However, many Award BIOSes (all?) do not allow you to turn
off UDMA.
>
>*apologies*. However, many Award BIOSes (all?) do not allow you to turn
>off UDMA.
All Award BIOSes that I have (for 5 working systems) support it if the
hardware supports it (2 systems).
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of th
On Fri, 25 Jun 1999, Vladimir Kushnir wrote:
> Hello,
> Sorry for being annoying but is there still anything wrong with CTM
> generation? The last src-cur delta was from 8th of June.
I know, we're waiting until Ulf gets the new disk up and spinning. It's
taking some time, but I think he's havi
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 repositaries being use
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 that location?
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr
The machine itself is back up. Services are being restored
currently.
The machine has now a 12GB vinum filesystem for /ctm and
should not run out of space so fast again.
--
Regards, Ulf.
-
Ulf Zimmermann, 1525 Pacific Ave., Al
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.. Intel's
site, and the FreeBSD
site have no information regarding this adaptor's compatibili
After a long absence, I was just about to get into my new joystick drivers
when it now fails to compile. What's the recommended change?
Stephen
--
The views expressed above are not those of PGS Tensor.
"We've heard that a million monkeys at a million keyboards could produce
> 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'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
[ 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 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
[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
> 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
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 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
Sheldon Hearn wrote:
>
> 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/boo
On Sat, 26 Jun 1999 01:05:31 MST, Doug wrote:
> Well that certainly looks like the right answer. Are you
> uncertain about it, or just being rhetorical?
The expanded version was
Try src/sys/boot, which is where I found what looked very much
like the new boot loader.
I'v
And to follow up on this topic: the german magazine c't has an article in
their current issue, where they compare a real-world setup measuring
web-server performance for NT an Linux both for an SMP and non-SMP setup.
Linux was - depending on the setup and application - a bit to much faster ...
1 - 100 of 214 matches
Mail list logo
