Today (Saturday) We will make some minor tuning adjustments to MySQL.

You may experience 2 up to 10 seconds "glitch time" when we restart MySQL. We expect to make these adjustments around 1AM Eastern Daylight Saving Time (EDT) US.


Is Unetbootin capable of making any iso file bootable

Login or Register to Reply

 
Thread Tools Search this Thread
# 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 to Reply

|
Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
RHEL Linux 6.2 to 7.3 - Bootable iso
videsh77
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...... Red Hat
1
Red Hat
how to re-create kick start bootable ISO
kalpeer
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. ...... Red Hat
0
Red Hat
make bootable usb from iso
locoroco
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?... Fedora
4
Fedora
Running bootable iso image with kexec
locoroco
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?... Linux
2
Linux
making an iso file...
asafronit
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...... SCO
5
SCO
LIVEMEDIA-CREATOR(1)					      General Commands Manual					      LIVEMEDIA-CREATOR(1)

NAME
livemedia-creator - Create live install media
SYNOPSIS
livemedia-creator [-h] (--make-iso | --make-disk | --make-fsimage | --make-appliance | --make-ami) [--iso ISO] [--disk-image DISK_IMAGE] [--fs-image FS_IMAGE] [--ks KS] [--image-name IMAGE_NAME] [--image-only] [--keep-image] [--no-virt] [--proxy PROXY] [--anaconda-arg ANACONDA_ARGS] [--armplatform ARMPLATFORM] [--location LOCATION] [--logfile LOGFILE] [--lorax-templates LORAX_TEMPLATES] [--tmp TMP] [--resultdir RESULT_DIR] [--app-name APP_NAME] [--app-template APP_TEMPLATE] [--app-file APP_FILE] [--ram MEMORY] [--vcpus VCPUS] [--vnc VNC] [--arch ARCH] [--kernel-args KERNEL_ARGS] [--dracut-arg DRACUT_ARGS] [--title TITLE] [--project PROJECT] [--releasever RELEASEVER] [--volid VOLID] [--squashfs_args SQUASHFS_ARGS]
DESCRIPTION
livemedia-creator uses Anaconda, kickstart and Lorax to create bootable media that use the same install path as a normal system install. It can be used to make live isos, bootable (partitioned) disk images and filesystem images for use with virtualization. The general idea is to use virt-install to install into a disk image and then use the disk image to create the bootable media. livemedia-creator --help will describe all of the options available. At the minimum you need: --make-iso to create a final bootable .iso --iso to specify the Anaconda install media to use with virt-install --ks is the kickstart to use to install the system
OPTIONAL ARGUMENTS
: -h, --help show this help message and exit --make-iso Build a live iso --make-disk Build a partitioned disk image --make-fsimage Build a filesystem image --make-appliance Build an appliance image and XML description --make-ami Build an ami image --iso ISO Anaconda installation .iso path to use for virt-install --disk-image DISK_IMAGE Path to disk image to use for creating final image --fs-image FS_IMAGE Path to filesystem image to use for creating final image --ks KS Kickstart file defining the install. --image-name IMAGE_NAME Name of fs/disk image to create. Default is a random name. --image-only Exit after creating fs/disk image. --keep-image Keep raw disk image after .iso creation --no-virt Use Anaconda's image install instead of virt-install --proxy PROXY proxy URL to use for the install --anaconda-arg ANACONDA_ARGS Additional argument to pass to anaconda (no-virt mode). Pass once for eachargument --armplatform ARMPLATFORM the platform to use when creating images for ARM, i.e., highbank, mvebu, omap,tegra, etc. --location LOCATION location of iso directory tree with initrd.img and vmlinuz. Used to run virt-install with a newer initrd than the iso. --logfile LOGFILE Path to logfile --lorax-templates LORAX_TEMPLATES Path to mako templates for lorax --tmp TMP Top level temporary directory --resultdir RESULT_DIR Directory to copy the resulting images and iso into. Defaults to the temporaryworking directory --title TITLE Substituted for @TITLE@ in bootloader config files --project PROJECT substituted for @PROJECT@ in bootloader config files --releasever RELEASEVER substituted for @VERSION@ in bootloader config files --volid VOLID volume id --squashfs_args SQUASHFS_ARGS additional squashfs args
APPLIANCE ARGUMENTS
: --app-name APP_NAME Name of appliance to pass to template --app-template APP_TEMPLATE Path to template to use for appliance data. --app-file APP_FILE Appliance template results file. VIRT-INSTALL ARGUMENTS: --ram MEMORY Memory to allocate for installer in megabytes. --vcpus VCPUS Passed to --vcpus command --vnc VNC Passed to --graphics command --arch ARCH Passed to --arch command --kernel-args KERNEL_ARGS Additional argument to pass to the installation kernel
DRACUT ARGUMENTS
: --dracut-arg DRACUT_ARGS Argument to pass to dracut when rebuilding the initramfs. Pass this once foreach argument. NOTE: this overrides the default.
SEE ALSO
Documentation in /usr/share/docs/lorax/README.livemedia-creator
AUTHOR
Brian C. Lane 2013-07-26 LIVEMEDIA-CREATOR(1)

Featured Tech Videos