Dan Nelson <[EMAIL PROTECTED]> writes:
Hi,
> No patching needed. You can wire down the unit number of your scsi bus
> and drive with boot hints as described in the scsi(4) manpage. Wire
> the adaptec card down as scbus0, and wire the device at scbus0.0 down
> as da0.
Nice. I've never used scsi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nelson wrote:
> In the last episode (Oct 16), Eric Masson said:
>> "Svein Skogen (List Mail Account)" <[EMAIL PROTECTED]> writes:
>>> With all due respect, if sysinstall isn't able to write those labels,
>>> this is hardly the solution to the probl
In the last episode (Oct 16), Eric Masson said:
> "Svein Skogen (List Mail Account)" <[EMAIL PROTECTED]> writes:
> > With all due respect, if sysinstall isn't able to write those labels,
> > this is hardly the solution to the problem... ;)
>
> Sysinstall, even if it has proven to be useful, is ou
"Svein Skogen (List Mail Account)" <[EMAIL PROTECTED]>
writes:
Hi,
> With all due respect, if sysinstall isn't able to write those labels,
> this is hardly the solution to the problem... ;)
Sysinstall, even if it has proven to be useful, is outdated in many
respects, it doesn't cope really well
"Svein Skogen (List Mail Account)" <[EMAIL PROTECTED]>
writes:
Hi,
> Is there any way to tell FreeBSD permanently "I want my adaptec
> controller's scsi chain to be the first, no matter what USB devices you
> find"?
You can circumvent this behaviour by using GEOM labels :
http://www.freebsd.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm writing this, in hope that someone has a quick-and-dirty trick to
solve a minor problem I have.
My home server, running RELENG_7 is booting off a 10Krpm scsi drive,
connected to an adaptec controller. This device is /dev/da0. However,
should I acc
