Subj : copy images under OpenBSD To : Francois Thunus From : Jasen Betts Date : Mon Nov 27 2000 10:07 pm Hi Francois. 26-Nov-00 11:34:00, Francois Thunus wrote to Jasen Betts FT> Hello ! FT> 25 Nov 00 16:05, Jasen Betts wrote to Francois Thunus: FT>>> I mean obviously this is a device driver. JB>> Is there another way to access the image of the volume? with a JB>> floppy drive you just copy to/from /dev/fd0 (etc) FT> normally you mount it first, hence you use your mounting point. When most people say "image of [a volume]" they mean a raw binary copy of the volume, starting at the first sector and continuing on to the last, for example rawwrite is a dos prog (distributed with linux CDs etc) for manipulating floppy images under dos.... under unix IME and AFAIK you can usually access the image by going straight to the special file (/dev/ entry) associated with the volume. FT> I am not aware (unless specific cases) that you can just copy to FT> /dev/fd0. normally you first mount /dev/fd0 somewhere (usually FT> /mnt/floppy or /floppy and operate on those. people use tar like that sometimes... FT> If you are trying to look at the content of a cd by looking at the FT> driver without mounting it first, I am not surprized it does not work The file in /dev/ is not the driver, it's just a name attached to two special numbers and some file permissions etc. he kernal uses those numbers to identify the physical, or virtual, hardware you're accessing. The driver is either built into, or loaded by, the kernel and is stored at some other location. -=> Bye <=- --- * Origin: (3:640/531.42) .