Is Unetbootin capable of making any iso file bootable

Login or Register for Dates, Times and to Reply

 
Thread Tools Search this Thread
Special Forums Hardware Boot Loaders Is Unetbootin capable of making any iso file bootable
# 1  
Is Unetbootin capable of making any iso file bootable

1)It is a great experience to achieve what I got today. I had downloaded GParted iso file (135 MB size). Now to make a bootable usb of it, I used unetbootin and to surprise I succeded in entering Gparted application and modified my partitions.
Earlier I was in a notion that it is used only for installing Linux by making bootable usb,etc. so, can it be used for any iso?

2)As I had earlier installed OS, I had to specify where I want to install it. But in this case (point 1) where I made bootable usb of Gparted iso: when I booted my system by doing the appropriate BIOS set up, It didn't ask me where to install Gparted. Directly I entered the Gparted application. So, please clarify me what happened in this case. Did it install in USB drive only?

3) When I entered the gparted application, there I opened a terminal. When I entered command
Code:
shutdown -h now

it asked me for root password. Because while booting from usb, it nowhere asked me for root credentials. so what is root password.
Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #153
Difficulty: Easy
Novell sold their Unix business operations to Microsoft in 1995.
True or False?

9 More Discussions You Might Find Interesting

1. Red Hat

RHEL Linux 6.2 to 7.3 - Bootable iso

Hi All On one of my sandbox machine, I want to replace RHEL 6.2 to RHEL 7.3. I am using both developer editions. rhel-server-7.3-x86_64-dvd.iso ... This is what I have downloaded from Red Hat Enterprise Linux Download | Red Hat Developers My understanding is this file would work as a... (1 Reply)
Discussion started by: videsh77
1 Replies

2. SuSE

How To make bootable USB with multiple ISO Files?

Hi All, I would need your assistance to make a bootable USB with SUSE LINUX Enterprise Server I have already downloaded relevant OS (Trail Version) packages @ 1) SLES-11-SP4-DVD-i586-GM-DVD1 2) SLES-11-SP4-DVD-i586-GM-DVD2 when I tried to open these packages with PowerISO one of the... (7 Replies)
Discussion started by: Leaner_963
7 Replies

3. Red Hat

How to create a bootable ISO from running Linux box?

Hi All, I have one query on creating bootable ISO. I have installed Centos 5.6 and done few configuration changes which is needed for deploying my App. Later I have deployed my app. Now Centos is up and running in a dedicated box along with my app. Now I want to create the... (3 Replies)
Discussion started by: kalpeer
3 Replies

4. Red Hat

how to re-create kick start bootable ISO

Hi All, I want to create kick start bootable ISO file. I have Centos 5.4 ISO and customized ks.cfg file. Now I need to recreate ISO with ks.cfg and content of existing ISO. During installation, it automatically should pick the kick start file and need to proceed with the installation. ... (0 Replies)
Discussion started by: kalpeer
0 Replies

5. Fedora

make bootable usb from iso

I need to boot the ultimate boot cd from an usb stick. Do I just copy the iso image to the usb key? How do I make the usb stick bootable? (4 Replies)
Discussion started by: locoroco
4 Replies

6. Linux

Running bootable iso image with kexec

I just tried to run the command kexec memtest86-4.0.iso To boot into memtest86 using kexec. This is the output: Cannot determine the file type of memtest86-4.0.iso How am I supposed to do this? (2 Replies)
Discussion started by: locoroco
2 Replies

7. Linux

A working bootable Linux XP Desktop 4.0.31 ISO image?

Hi everyone, I want to run on VMWare the Linux XP 2010 Desktop 4.0.31 distro, Iīve downloaded the latest realese from its website (Trustverse Desktop 4.0 RC1 -build 31)-->http://www.linux-xp.com/desktop/download/. Itīs 4.47 GB in size, but when I mount on an ISO software, the size is 2.75GB... (0 Replies)
Discussion started by: cgkmal
0 Replies

8. SCO

making an iso file...

can i make an iso file from my DAT tape? pref .ISO? the thing is .. i have an 5.0.7 and a complete backup of hd (cpio cmd) on to tape (find . -depth -print | cpio -oVcB -C 20480 -O /dev/rStp0) that i made after booting from boot&root floppies now i want to take this backup and dump it on... (5 Replies)
Discussion started by: asafronit
5 Replies

9. Solaris

iso files to make bootable dvd image

Hey all, I'm a newbie to iso files and I just downloaded the 2 iso files for *cough* ms2003 R2 *cough* trial software. After I downloaded the iso files I just dragged them to my burn software gui and sure enough it burned to dvd 2 iso files. When I attempted to boot the image using VMware... (0 Replies)
Discussion started by: bdsffl
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)

Featured Tech Videos