Sponsored Content
Full Discussion: .usb file
Operating Systems Solaris .usb file Post 302984005 by Corona688 on Wednesday 19th of October 2016 04:27:05 PM
Old 10-19-2016
There's not a "usb" kind of file, I think they named it "usb" just to differentiate it from their ISO image. UNIX plays fast and loose with file extensions since they have zero meaning to it.

I think it's a disk image, which would need to be dumped raw onto the USB device. This is similar to how a CDROM containing "disk image.iso" isn't the same thing as the cdrom that burning "disk image.iso" to disk would create.

Fair warning, this would wipe out your USB drive's existing contents and partition information!

How to do so depends on your system.
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

Usb??????????????

it's true that USB port has no security?? (0 Replies)
Discussion started by: lolo_vang
0 Replies

2. Programming

Development for USB

Hi, I am working with Sun Solaris 9(Generic_112233-07 sun4u sparc SUNW,Sun-Blade-100)and I need to develop the USB part in our application using C/C++.In our application,we are monitoring the UPS by Serial port and now I have to develop the USB part to mointor the UPS. So I need your help to... (0 Replies)
Discussion started by: smartgupta
0 Replies

3. UNIX for Dummies Questions & Answers

USB-USB cable between linux and windows computers

Is there an easy way to setup a cross-over cable (USB-USB) between a linux box and a windows PC? My 2 machines are next to each other but I really do not want to keep transfering my files using my USB drive. Thanks! (4 Replies)
Discussion started by: Xterra
4 Replies

4. Shell Programming and Scripting

script to detect a file from inserted usb and puts into a Variable

There is a same named log file that I have on my 2 different android phones. When I plug it into my computer, it appears in the media folder, For example the first android phone: /media/F6BA-0AF5/folder/A.log I want to put that into a variable to be manipulated.... (3 Replies)
Discussion started by: tobenguyen
3 Replies

5. OS X (Apple)

USB File Transfer MacOS 10.6.5 to Android 2.2?

I'm trying to get a MacBook Air (MBA) running 10.6.5 to recognize a Samsung Galaxy S (Android 2.2) vis the USB interface for simple file transfers back and forth. Nothing works so far. I've tried many things! :wall: I noticed when I connect my phone to the MBA, there is a message in system.log... (2 Replies)
Discussion started by: Neo
2 Replies

6. Solaris

Saving to usb

Greetings. I am trying to save a file to a usb from solaris 10. If I do rmformat, I see my usb, but can't find a location to tell things to save to or figure out how to save/view the files on the disk. Any help/thoughts/etc would be appreciated. Thanks! ~K (20 Replies)
Discussion started by: kuriosity_prime
20 Replies

7. UNIX for Advanced & Expert Users

USB-Ethernet/Ethernet-USB

Hi, I have posted several times regarding my application. In a nutshell, I have a server application that logs attached instrument data over USB and Ethernet. My restriction here is having two wires or more to plug all instrumentation in - at least one for USB and at least one for ethernet. ... (16 Replies)
Discussion started by: fedora18
16 Replies

8. UNIX for Advanced & Expert Users

Waking Up USB External Hard Drive for file archiving

Hello Experts, I hope I'm writing to the correct category for my question. I have a very basic shell script for doing file archiving to the external usb hard drive (WD studio edition II 2TB formatted as FAT32 for compatibility). The shell script only needs to run once per day. It basically... (8 Replies)
Discussion started by: johankor
8 Replies

9. AIX

Has anyone created JFS2 file system on a USB drive attached to AIX server?

We have an IBM Power 710. It has a USB port on the front. I have done some searching and see that there is information out there on how to create a JFS2 file system on USB drives. A few have commented that they would not recommend it, if the server is important, may crash the server... Just... (0 Replies)
Discussion started by: mbenedi
0 Replies
MKRESCUE(8)                                                   System Manager's Manual                                                  MKRESCUE(8)

NAME
mkrescue - make rescue floppy or CD SYNOPSIS
/sbin/mkrescue makes a bootable rescue floppy or CD using the default kernel specified in lilo.conf. DESCRIPTION
mkrescue takes its specifation for the kernel from the default image specified in /etc/lilo.conf. If the actual default is an other= spec- ification, then use the first image= specification. Any associated initial ramdisk (initrd=), and append= options will also be used. The root directory will be taken to be the current root. A bootable floppy or CD-image will be created using LILO version 22.5.5 or later. mkrescue normally requires no options, unless a CD-image is desired (--iso). OPTIONS
--append <string> Override any append= options taken from the default image. If there is any doubt about whether the lilo.conf options are correct, then specify no kernel parameters by providing the null string (--append ""). --debug Provide verbose output of the operation of mkrescue, pausing to allow the setting of internal operating parameters to be viewed. <CR> must be hit to proceed from these pauses. --device <device> Make the floppy on a device other than /dev/fd0. The floppy disk will always be made to boot on BIOS device code 0x00 (A: drive), without regard to the drive on which it is created. --fast Use a faster method of creating the boot floppy. This involves first creating a file of --size 1k blocks (default is 1440) mounted using a loopback device, creating the bootable floppy, then copying the entire file to the disk. --fs [ ext2 | msdos | minix ] Specify the type of filesystem to create on the drive. ext2 is the default, but msdos and minix allow slightly more disk sectors for really big kernels. --help Print a short usage synopsis, including a list of command options. --image <label> Specifies the label or alias of the particular image from which the append, initial ramdisk, root, keytable, and kernel information is to be taken. --initrd <filepath> and --kernel <filepath> These options, which must be used together, allow specification of an arbitrary kernel file and initial ramdisk file to be used on the created boot floppy. Be sure you know what you are doing before you use these options. If no inital ramdisk is needed with a particular kernel, then you MUST specify --initrd "", meaning a null pathname. --install [ text | menu ] Allows overriding the default human interface used with the rescue bootloader (configuration file "install=" option). text is the default on 1.2MB and 1.44MB floppy disks, and menu is the default on 2.88MB floppies and HD emulation on CD-R media. --iso Create an ISO-9660 bootable CD image (El Torito Format) suitable for burning to a CD-R or CD-RW. The --device specification defaults to the filename rescue.iso, and the --size defaults to 2880. A utility such as "wodim" may be used to burn the ISO file to a recordable CD medium. With this ISO option, the --size HD option is allowed. --nocompact For faster kernel loading from a floppy, LILO map compaction is normally enabled. This option will disable map compaction by omit- ting the lilo -c switch. --noformat Suppresses creation of a new filesystem on the boot floppy. This option may be used ONLY when you know that the floppy you will be writing upon is formatted with the same filesystem as specified by --fs XXX (default is ext2). --root <device> Specify the root filesystem for the kernel on the boot floppy. The currently mounted root is taken as the default specification. --size [ 1440 | 1200 | 2880 | HD ] The default floppy disk size is 1440, meaning a 1.44MB floppy. When --iso is specified, the default size is 2880. Allowed specifi- cations are 1200, 1440, or 2880, meaning a 1.2MB, 1.44MB or 2.88MB floppy, respectively. No other floppy disk sizes are supported. The HD specification, meaning "hard disk", may only be used with the --iso option, to indicate a 16MB hard disk is to be generated for emulation. This allows for very large kernel/initial ramdisk combinations on CD-R. The hard disk image is created using loop- back devices /dev/loop0 and /dev/loop1, which must be free to utilize this size option. --version Print the version number of mkrescue, then terminate. SEE ALSO
cdrecord(1), dd(1), wodim(1), lilo.conf(5), lilo(8), mkfs(8), mkinitrd(8), mkisofs(8), mount(8) 6 Mar 2011 MKRESCUE(8)
All times are GMT -4. The time now is 03:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy