On Tue, 2 Mar 1999, Thomas Dean wrote:
I am running smp, 4.0-current, as of Mon Feb 15 03:34:29 PST 1999.
Printing is very slow. I have a HP LaserJet III attached to lpt0.
Printing in the pcl, text, mode is slower than I expect. Printing in
the postscipt mode is extremely slow. A 30K
On Tue, 2 Mar 1999, Thomas Dean wrote:
I am running smp, 4.0-current, as of Mon Feb 15 03:34:29 PST 1999.
Printing is very slow. I have a HP LaserJet III attached to lpt0.
Printing in the pcl, text, mode is slower than I expect. Printing in
the postscipt mode is extremely slow. A 30K
Alfred Perlstein writes :
Printing is very slow. I have a HP LaserJet III attached to lpt0.
Printing in the pcl, text, mode is slower than I expect. Printing in
the postscipt mode is extremely slow. A 30K postscript file has been
OVER 5 minutes and is not finished!
have you tried:
Brian Feldman said:
The lock manager isn't bright enough to detect that the process
already holds a read lock when it attempts to get the write lock.
Thus, you get the thrd_sleep instead of a panic.
In short, same bug, different symptoms.
Ahh, makes sense.
Quick question: how
On Tue, 2 Mar 1999, Chuck Robey wrote:
On Tue, 2 Mar 1999, Doug Rabson wrote:
That was put in extremely recently. The reason it doesn't build a shared
library by default is to avoid potential conflict with the system
libstdc++.
If you enable it, the port will install the shared lib
It's a long long time since I was working on the lpt driver. This
kind of symptom was a common problem during its development. I
haveen't been able to really appreciate the code for the nltp
driver, so I also can't really see if there is a problem.
Biggest problem when I was hacking on the
ir /usr/info/dir; fi
install-info /usr/info/cpp.info /usr/info/dir
install-info: Undefined error: 0 for /usr/info/dir
*** Error code 1
This is a known problem. Sometimes it occurs, sometimes it doesn't. I
don't use info files, so I know zero about them or what this error is
about.
If
The only thing that bit me was that I used wd0 and wd2 with the older
driver, whereas the newer driver automatically decided to use ad0 and
ad1. This is expected behaviour, but it's something for other weenies
to watch out for. :-)
This breakage was announced :-).
Besides, it is not even
Hello,
I would like to know if there exist CJK code for freebsd-current. If so,
please show me the ftp or url. Thanks.
Clarence
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
On Wed, 03 Mar 1999 13:13:10 +0100, Cejka Rudolf wrote:
It's really frustrating if I add new drive (anywhere on the busses) and
other drives change their numbers - it's good base for big troubles
(infinite changing /etc/fstab and so on).
Fair enough. But in real life, you don't add a new
-Original Message-
From: Sheldon Hearn [SMTP:sheld...@iafrica.com]
Sent: Wednesday, March 03, 1999 1:40 PM
To: Cejka Rudolf
Cc: freebsd-current@freebsd.org; s...@freebsd.dk
Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
I'm not sure I understand what
On Wed, 03 Mar 1999 14:07:22 +0100, Ladavac Marino wrote:
[ML] Well, it's for those people who plug a drive occasionally
into a computer. They don't want other drives moved around.
Thanks for the feedback. Jeremy Lea also provided in private mail
quite a detailed example of why
On Wed, 3 Mar 1999, Geoff Rehmet wrote:
Alfred Perlstein writes :
Printing is very slow. I have a HP LaserJet III attached to lpt0.
Printing in the pcl, text, mode is slower than I expect. Printing in
the postscipt mode is extremely slow. A 30K postscript file has been
OVER 5
It seems Sheldon Hearn wrote:
Guess the answer for now is that people who can't live without
statically numbered drives continue to use the older IDE driver or mail
Soren diffs for adding device wiring support. :-)
Well, well, don't panic :)
I'll provide an option in the next commit round
This is results of testing my machine (Toshiba Satellite Pro 445CDX
notebook). Shows not very huge improvement yet ;)
wd driver:
? ---Sequential Output ---Sequential Input--
--Random--
? -Per Char- --Block--- -Rewrite-- -Per Char- --Block---
--Seeks---
On Wed, 3 Mar 1999, SXren Schmidt wrote:
It seems Daniel O'Connor wrote:
On 02-Mar-99 SXren Schmidt wrote:
Its in the works, together with the tagged queuing some of the
newer drives supports.
Wow! :)
Is there any chance od adding the ability to 'wire' devices a la SCSI? :)
Do you have any plans to support OPTICAL device?
I want to use my PD drive (NEC ODX654P), and some other people
want to use ATAPI MO.
I've already made patch for PD/CD drive, and registered it as
PR kern/10116. But it's not so good patch, because my PD drive has
2 LUN's. LUN0 is CD-ROM and LUN1
On Tue, 2 Mar 1999, Lee Cremeans wrote:
Will this new ATA driver finally support DMA correctly on ATAPI devices (as
opposed to pure ATA disk devices)? This is a feature that could really come
in handy for me (as well as a reason to migrate back to -current from 3.1 :)
Which brings up a
My machine is a DEC Celebris 5133DP. The only device added since
purchase was de0.
This is a recent problem, within the past few months. Or, was I
running polled before that? I used the default. From an old config,
I see:
device lpt0at isa? port? tty irq 7 vector lptintr
On Wed, 3 Mar 1999, S?ren Schmidt wrote:
It seems Sheldon Hearn wrote:
Guess the answer for now is that people who can't live without
statically numbered drives continue to use the older IDE driver or mail
Soren diffs for adding device wiring support. :-)
Well, well, don't panic :)
Its in the works, together with the tagged queuing some of the
newer drives supports.
Whoa! What drives?!?! I want a dozen!
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Changing to polled improved things, somewhat.
Printing a 30k postscript file takes 2 minutes.
Sending an 9368 byte binary, printer control and setup file takes
approximately 1 minute.
This is very slow. I will try to setup a DOS or WINNT machine to
duplicate this.
tomdean
To Unsubscribe:
I'm curious how the new driver handles numbering.
You said in your first mail that drives are numbered by
probe order? I have two 4 gig IDE drives, both
single masters on separate channels. I'm only booting
from the first one, so that's not a problem, but the first
is called wd0 and the second
Sorry, but I just could not track down the problem myself :(
With 2.2 box you get:
shell6: {104} lock -np
lock: /dev/ttyp8 on shell6.ba.best.com. no timeout
time now is Wed Mar 3 08:52:55 PST 1999
Key:
And on 3.x/4.x you get:
nautilus% ls -l /usr/bin/lock
-r-sr-xr-x
On Wed, 03 Mar 1999 08:57:05 PST, Jan B. Koum wrote:
nautilus% ls -l /usr/bin/lock
-r-sr-xr-x 1 root wheel 5636 Feb 3 21:06 /usr/bin/lock
nautilus% lock -np
nautilus%
Can someone tell me what is going on?
Works for me.
$ uname -a
FreeBSD axl.noc.iafrica.com 4.0-CURRENT
On Wed, Mar 3, 1999, Jan B. Koum put this into my mailbox:
Sorry, but I just could not track down the problem myself :(
With 2.2 box you get:
shell6: {104} lock -np
lock: /dev/ttyp8 on shell6.ba.best.com. no timeout
time now is Wed Mar 3 08:52:55 PST 1999
Key:
And
On Wed, 03 Mar 1999 19:06:25 +0200, Sheldon Hearn wrote:
You're not using PAM, perhaps?
I'd greatly appreciate it if everyone would ignore that comment.
Thanks,
Sheldon.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Cejka Rudolf wrote:
What was bad with old static drive numbering?
Irrespective of all the valid reasons to allow for wiring (but not
mandate), static drive numbering is not BIOS compatible (thus, not
DOS compatible). This violates POLA.
--
Daniel C. Sobral(8-DCS)
On Wed, 3 Mar 1999, Thomas Dean wrote:
Changing to polled improved things, somewhat.
Printing a 30k postscript file takes 2 minutes.
Sending an 9368 byte binary, printer control and setup file takes
approximately 1 minute.
This is very slow. I will try to setup a DOS or WINNT machine
John S. Dyson wrote:
Brian Feldman said:
Quick question: how in the heck did you learn this whole VM system?
Alan has had a history helping on the VM code for quite a while, and
has contributed some really good ideas. Frankly, he appears to
understand the code as well as anyone does.
David O'Brien wrote:
I've put the bmake contrib framework for EGCS at
ftp://ftp.nuxi.com/pub/FreeBSD/egcs
(ftp://ftp.nuxi.com/pub/FreeBSD/egcs/cvs is all you really need)
This is very rough work, but should help us towards our goal.
In there you will find a CVS tree under ``cvs''. This
David O'Brien wrote:
ir /usr/info/dir; fi
install-info /usr/info/cpp.info /usr/info/dir
install-info: Undefined error: 0 for /usr/info/dir
*** Error code 1
This is a known problem. Sometimes it occurs, sometimes it doesn't. I
don't use info files, so I know zero about them or
Date: Thu, 04 Mar 1999 02:53:09 +0900
From: Daniel C. Sobral d...@newsguy.com
Irrespective of all the valid reasons to allow for wiring (but not
mandate), static drive numbering is not BIOS compatible (thus, not
DOS compatible). This violates POLA.
I'm at least as much against POLA violations as
On Thu, Mar 04, 1999 at 02:40:14AM +0900, Daniel C. Sobral wrote:
And the question is how he managed to. :-)
I graduated from CMU in 1986. While there, I worked part-time
on the Mach project. Later, I used the Mach VM code as infrastructure
for my Ph.D. thesis on automatic data placement
What's the chance the Adaptec-152x controller (aic0) will soon work
with 3.1-STABLE?
It has pretty horrible performance problems on 2.2.8-STABLE, even when
using DMA:
[...]
4.4%Sys 91.9%Intr 3.7%User 0.0%Nice 0.0%Idl 4244 inact 204 pci irq9
|||||||||
In article 18961.920316...@critter.freebsd.dk,
Poul-Henning Kamp p...@critter.freebsd.dk wrote:
It should have been done with a simple ascii string instead. The
drivers are much better at chewing on it than the generic code,
it would be simpler to understand, simpler to implement, you
Hi,
We are attempting to load 4.0-19990303-SNAP on a Dell machine:
Optiplex XMT 5120 (120Mhz,48Meg)
w/ adaptec 2940 controller 1gig drive.
The dual floppy boot process works fine until it changes to
the root device. This occurs even after going into config and
deleting all
Amen, brother! Get it said! People who claim that strings are
too slow would benefit greatly from spending a few days with the
profiler.
Now I'll stir the other pot and say that performance isn't the issue- the
issue is that there's nothing that says that strings and identifiers are
always
In message pine.lnx.4.04.9903031215150.25376-100...@feral-gw, Matthew Jacob w
rites:
Amen, brother! Get it said! People who claim that strings are
too slow would benefit greatly from spending a few days with the
profiler.
Now I'll stir the other pot and say that performance isn't the
Matthew Jacob wrote:
Now I'll stir the other pot and say that performance isn't the
issue- the issue is that there's nothing that says that strings and
identifiers are always easier to use and/or understand than numbers.
They are a lot more extensible, though. With strings, you generally
Now I'll stir the other pot and say that performance isn't the
issue- the issue is that there's nothing that says that strings and
identifiers are always easier to use and/or understand than numbers.
They are a lot more extensible, though. With strings, you generally
have to modify and
I deleted the annoucement email, but looking over LINT, the
following lines seemed appropiate for my 486:
controller ata0at isa? port IO_WD1 bio irq 14
device atadisk0
First problem I had was that the kernel would not link without
defining:
controller pci0
On Wed, 3 Mar 1999, John Polstra wrote:
In article 18961.920316...@critter.freebsd.dk,
Poul-Henning Kamp p...@critter.freebsd.dk wrote:
GRUMBLE
For some reason, some people around our camp-fire, have a hard time
understanding that compiletime enumeration of potential options
is a
Mikhail Teterin wrote...
What's the chance the Adaptec-152x controller (aic0) will soon work
with 3.1-STABLE?
I think the chances are very slim that it will work soon with 3.x or 4.x.
It may get done at some point, but I don't think anyone is actively working
on it at the moment.
It has
It seems Bob K wrote:
On Tue, 2 Mar 1999, Lee Cremeans wrote:
Will this new ATA driver finally support DMA correctly on ATAPI devices (as
opposed to pure ATA disk devices)? This is a feature that could really come
in handy for me (as well as a reason to migrate back to -current from 3.1
It seems Tugrul wrote:
I deleted the annoucement email, but looking over LINT, the
following lines seemed appropiate for my 486:
controllerata0at isa? port IO_WD1 bio irq 14
deviceatadisk0
Correct.
First problem I had was that the kernel would not link
On Wed, 3 Mar 1999, Mikhail Teterin wrote:
What's the chance the Adaptec-152x controller (aic0) will soon work
with 3.1-STABLE?
It has pretty horrible performance problems on 2.2.8-STABLE, even when
using DMA:
[...]
4.4%Sys 91.9%Intr 3.7%User 0.0%Nice 0.0%Idl 4244 inact 204
First update to the new ATA/ATAPI driver:
Added driver to support ATAPI floppies ie LS-120 ZIP drives.
I'm not too sure of this 2 hour job, I cannot get writeprotect
disabled on the only ZIP medium I just got, but I can read the
disk. Reports are welcome on LS-120 drives too, they are very
hard
Leif Neland le...@neland.dk wrote:
Is there a way to test if interrupts are getting serviced? A counter of
interrupts?
vmstat -i
Peter
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
It has pretty horrible performance problems on 2.2.8-STABLE, even when
using DMA:
[...]
4.4%Sys 91.9%Intr 3.7%User 0.0%Nice 0.0%Idl 4244 inact 204 pci irq9
|||||||||| 5288 cache 105 aic0 irq11
==++
On Mon, Mar 01, 1999 at 10:21:05PM +0100, Søren Schmidt wrote:
Finally!!
The much roumored replacement for our current IDE/ATA/ATAPI is
materialising in the CVS repositories around the globe.
So what does this bring us:
A new reengineered ATA/ATAPI subsystem, that tries to overcome
most of
On Tue, Mar 02, 1999 at 11:32:51PM -0800, Thomas Dean wrote:
I am running smp, 4.0-current, as of Mon Feb 15 03:34:29 PST 1999.
Printing is very slow. I have a HP LaserJet III attached to lpt0.
Printing in the pcl, text, mode is slower than I expect. Printing in
the postscipt mode is extremely
Just to be clear, when I said the values from dmesg and config covered
everything, I mean all the physical and/or BIOS devices are included
in the list.
There are TWO cards plugged into the MB, other than the CPU's. These
are de0 and the vga. The on-mother-board devices are all in dmesg.
There
It seems Nicolas Souchu wrote:
What would you think of parallel port devices? Would it be easy
to make the new ATAPI stuff work with ppbus? I especially think
about the HP7200 CD-RW which has certainly hard real-time constraints
to burn a CD.
Hmm, you have any docs on how to talk to such a
After having CVSupped to the latest 4.0-CURRENT tree
(just now), I noticed the amazing speed of the new ATA driver.
BUT
I noticed something in dmesg...
ata1: unwanted interrupt
ad0: SAMSUNG WU33205A (3.2GB)/HF103-15 ATA-3 disk at ata0 as master
ad0: 3090MB (6330240 sectors), 6280 cyls, 16
Matthew Jacob writes:
Amen, brother! Get it said! People who claim that strings are
too slow would benefit greatly from spending a few days with the
profiler.
Now I'll stir the other pot and say that performance isn't the issue- the
issue is that there's nothing that says that strings
On Wed, 03 Mar 1999 16:06:19 CST, Chris Costello wrote:
After having CVSupped to the latest 4.0-CURRENT tree
(just now), I noticed the amazing speed of the new ATA driver.
The amazing speed of the new ATA driver? Were you using 32 bit transfers
and multi-sector IO with the older driver?
On Wed, Mar 3, 1999, Sheldon Hearn put this into my mailbox:
On Wed, 03 Mar 1999 16:06:19 CST, Chris Costello wrote:
After having CVSupped to the latest 4.0-CURRENT tree
(just now), I noticed the amazing speed of the new ATA driver.
The amazing speed of the new ATA driver? Were
Geoff Rehmet wrote:
Alfred Perlstein writes :
Printing is very slow. I have a HP LaserJet III attached to lpt0.
Printing in the pcl, text, mode is slower than I expect. Printing in
the postscipt mode is extremely slow. A 30K postscript file has been
OVER 5 minutes and is not
David Wolfskill wrote:
Irrespective of all the valid reasons to allow for wiring (but not
mandate), static drive numbering is not BIOS compatible (thus, not
DOS compatible). This violates POLA.
I'm at least as much against POLA violations as anyone... but the real
POLA violation I see is
Mikhail Teterin wrote:
What's the chance the Adaptec-152x controller (aic0) will soon work
with 3.1-STABLE?
I just wish it was soon. I *so* wanted to be able to access external
hd on my notebook and keep a local CVS tree (not to mention install
X)...
It has pretty horrible performance
Thomas Dean wrote:
My machine is a DEC Celebris 5133DP. The only device added since
purchase was de0.
Regardless of the devices configured in the kernel, does the
*computer* have other *physical* devices, such as sound cards
(builtin or not)?
Also, I seem recall discussions suggesting that
Leif Neland wrote:
Is it printer, cable, port, or freebsd-config, which is to blame? I don't
know how to proceed either...
BIOS settings? Have you tried changing BIOS settings such as EPP?
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.org
FreeBSD
On Wed, 3 Mar 1999, Chris Costello wrote:
After having CVSupped to the latest 4.0-CURRENT tree
(just now), I noticed the amazing speed of the new ATA driver.
BUT
I noticed something in dmesg...
ata1: unwanted interrupt
ad0: SAMSUNG WU33205A (3.2GB)/HF103-15 ATA-3 disk at ata0 as
First update to the new ATA/ATAPI driver:
Added driver to support ATAPI floppies ie LS-120 ZIP drives.
I'm not too sure of this 2 hour job, I cannot get writeprotect
disabled on the only ZIP medium I just got, but I can read the
disk. Reports are welcome on LS-120 drives too, they are
On Tue, 2 Mar 1999, Geoff Rehmet wrote:
Just some results of testing the comparison of wd and ata:
Both bonnie tests were run on a freshly booted machine, P133,
64M RAM, running X and netscape, but only Bonnie active:
Odd. My (crapy?) WD drive is much faster with DMA (not UDMA AFAIK), so
On Wed, Mar 3, 1999, oZZ!!! put this into my mailbox:
i think it tell you about not used 2nd IDE controller...
Nope, my CD ROM is on the second IDE controller ...
-Chris
--
Powered by FreeBSD 4.0-CURRENT. The Power to Serve!
int main(int m){main(!main(0));}
To
On Thu, 4 Mar 1999, oZZ!!! wrote:
What exactly is 'unwanted interrupt' supposed to mean, and is it
likely to be a problem in my kernel configuration? (I can send a copy
of it on request...)
i think it tell you about not used 2nd IDE controller...
Nope. I've got three IDE/ATAPI
Kenneth D. Merry wrote:
I think the chances are very slim that it will work soon with 3.x or 4.x.
It may get done at some point, but I don't think anyone is actively working
on it at the moment.
Someone is reportedly working on it. Whether that is actively or
not, I don't know... :-(
If
* From: Robert Watson rob...@cyrus.watson.org
* away logged in via the network performing this recovery. Having the
* drives automatically renumber themselves on the complete failure of one
* drive (and it was fairly complete) would have been a disaster. This is
Or just think ccd. There
Matthew Jacob wrote:
Amen, brother! Get it said! People who claim that strings are
too slow would benefit greatly from spending a few days with the
profiler.
Now I'll stir the other pot and say that performance isn't the issue- the
issue is that there's nothing that says that
After having CVSupped to the latest 4.0-CURRENT tree
(just now), I noticed the amazing speed of the new ATA driver.
The amazing speed of the new ATA driver? Were you using 32 bit transfers
and multi-sector IO with the older driver?
I assumed from the benchmarks posted that I had no
Am I confused (yet again)?
Yes ;-)
I mean the time it takes to actually detect the drive.
I recently added
options IDE_DELAY=2000
on all IDE kernels I managed. The only problem with this short delay
so far was an undetected drive in an unusual configuration:
The jumper block
On Wed, Mar 03, 1999 at 12:16:20PM -0800, Matthew Jacob wrote:
Now I'll stir the other pot and say that performance isn't the issue- the
issue is that there's nothing that says that strings and identifiers are
always easier to use and/or understand than numbers.
I was not responding to this for a while because Poul quite correctly
thwapped me for not being on point, but I couldn't let this go.
The point should be clear, using proper string identifiers would
make your program easier to understand and modify, as well as
allow for greater extensibility.
On 03-Mar-99 Sheldon Hearn wrote:
I'm not sure I understand what real-world frustrations people are having
here. Is this thread the product of reactionary criticism, or are there
real examples of situations in which there are serious disadvantages to
the way Soren has things working?
I
Great job, Soren! The ATA drivers work great for me. I see no speed change
in transfer rate, and an increase in interrupts, but I expect better
performance when DMA has been implemented. Boot time has decreased from about
40 seconds to about 7 seconds as well, something I've long wanted!
You
John Dyson extemporised:
%Julian Elischer said:
%
%
% On Tue, 16 Feb 1999, Luoqi Chen wrote:
% You may try my patch at http://www.freebsd.org/~luoqi, which would allow
% linux threads to run on SMP.
%
% I've gone through these patches and I can see that they are really needed
% for SMP
On Wednesday, 3 March 1999 at 14:59:49 -0800, Satoshi Asami wrote:
* From: Robert Watson rob...@cyrus.watson.org
* away logged in via the network performing this recovery. Having the
* drives automatically renumber themselves on the complete failure of one
* drive (and it was fairly
Not that I have one of these controllers, but I just received my 3.1
cd set in the mail today, and happened to notice that the Adaptec
152x controller is listed on the back as supported, along with the
Tekram DC390 (and other AMD 53c974 based boards). I was sure that
these were both still
After testing out the new ATA drivers, I've only got a single problem. My
box locked up while accessing the LS-120 (and, seemingly, swapping):
Mar 4 00:20:02 green /kernel: atapi_transfer: bad command phase
Mar 4 00:20:33 green /kernel: swap_pager: indefinite wait buffer: device:
0x20019,
Neal Westfall wrote...
Not that I have one of these controllers, but I just received my 3.1
cd set in the mail today, and happened to notice that the Adaptec
152x controller is listed on the back as supported, along with the
Tekram DC390 (and other AMD 53c974 based boards). I was sure that
On Wed, 3 Mar 1999, Mikhail Teterin wrote:
It has pretty horrible performance problems on 2.2.8-STABLE, even when
using DMA:
[...]
4.4%Sys 91.9%Intr 3.7%User 0.0%Nice 0.0%Idl 4244 inact 204 pci irq9
|||||||||| 5288 cache 105 aic0 irq11
In message 199903032050.naa86...@panzer.plutotech.com Kenneth D. Merry
writes:
: The 152x boards are programmed I/O only, I believe. They don't do DMA.
: So it won't matter if the driver is rewritten for CAM, you'll still get
: lousy performance from the board.
They can do DMA, but I don't
In the last episode (Mar 03), S?ren Schmidt said:
It seems Tugrul wrote:
Second, at boot:
[...]
ata0 at 0x1f0-0x1f7 irq 14 on isa
[...]
ad0: QUANTUM LP240A GM240A01X/4.0 ATA-? disk at ata0 as master
ad0: 0MB (0 sectors), 723 cyls, 13 heads, 51 S/T, 512 B/S
ad0: 16 secs/int, 0
There is an SMP-specific bug in pmap_remove_all. Specifically, it may
fail to perform a TLB invalidation on the other processor(s) when one is
in fact necessary.
I don't have an SMP to test this, so would some of you with SMPs
please do a sanity test on this patch? In effect, the patch disables
I heard (or thought so) a long time ago that FreeBSD
had a devfs like filesystem.
Now I remember, here's where I found it mentioned in
respect to FreeBeasty...
http://www.cs.uml.edu/~acahalan/linux/devfs.html
Is this still experimental? Oh, and has anyone heard
of any LFS projects on freebsd,
Satoshi Asami wrote:
* From: Robert Watson rob...@cyrus.watson.org
* away logged in via the network performing this recovery. Having the
* drives automatically renumber themselves on the complete failure of one
* drive (and it was fairly complete) would have been a disaster. This is
On Thu, Mar 04, 1999 at 01:13:08AM -0600, Shawn Leas wrote:
I heard (or thought so) a long time ago that FreeBSD
had a devfs like filesystem.
Now I remember, here's where I found it mentioned in
respect to FreeBeasty...
http://www.cs.uml.edu/~acahalan/linux/devfs.html
Forget this question,
It would help a lot if you could make it CVSUPpable :-). Those of us
in the third world would greatly appreciate that!
You talked me into it :-)
distributions are egcs (or broken into bmake-egcs and contrib-egcs)
*default host=relay.nuxi.com
*default base=.
*default release=cvs
*default delete
Oi! If you have softupdates on the LS120 drive, be aware that soft updates
has been known to have odd behaviour with some drive types (e.g. IDE
drives in 1-(non-multiblock) block mode, and floppy drives. I wouldn't be
surprised if LS120 drives had the capacity to confuse softupdates..
julian
On
FreeBSD has had a devfs that is not genrally useful for over 2 years.
The code to make it useful was removed from the tree due to various
reasons that can be argued ither way. I haven't had the inspiration to
re-write it as it needs to be changed to take into account some new
developments in
93 matches
Mail list logo
