On Sun, Feb 13, 2005 at 10:52:54PM -0500, Mike Jeays wrote:One possibility might be to make the umass driver a module and keep> I have at present two emulated SCSI devices on my system; a USB flash
> drive, and a DVD-writer.
> They get assigned:
> 0,0,0 0) 'SanDisk ' 'Cruzer Micro ' '2033' Removable Disk
> 2,0,0 200) 'HL-DT-ST' 'DVDRAM GSA-4160B' 'A300' Removable CD-ROM
> if the USB device is present at boot time (I think).
atapicam compiled into the kernel, or make them both modules, but always
load atapicam first. This will cause usb storage devices to always come
later since they won't be detected until the umass module is loaded.
P.S. Does freebsd do anything to autoload modules that might interfere?
> So my script for burning CDs, which says:
> mkisofs -J -L -R -o x1.iso "$*"
> cdrecord -v dev=2,0,0 x1.iso
> rm -f x1.iso
> is very fragile.
> How should I do it? Write a script to read the output of cdrecord
> -scanbus and grab the device number? There has to be a "right" way, and
> instinct says this isn't it.
> [email]freebsd-questionsfreebsd.org[/email] mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribefreebsd.org"
I sense much NT in you.
NT leads to Bluescreen.
Bluescreen leads to downtime.
Downtime leads to suffering.
NT is the path to the darkside.
Powerful Unix is.
Public Key: [url]ftp://ftp.tallye.com/pub/lorenl_pubkey.asc[/url]
Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C