Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
And you never, ever use dd (or any other command, for that matter) to write directly to a device that contains a currently mounted filesystem. Apparently the Puppy Linux ISOs are not designed to be simply copied as an image to a USB drive. That works only for specially designed hybrid ISO images. The web site http://puppylinux.org/wikka/InstallationFrugal has complete instructions for doing that.
That's strange. I was about to take back everything I said, because I downloaded tahr-6.0-CE_PAE.iso, copied it to a USB flash drive with "dd if=tahr-6.0-CE_PAE.iso of=/dev/sde bs=32k", and tahrpup 6.0 booted just fine from that drive, both in a VM and in my laptop. Looking at that drive with fdisk on another machine, I see
Code:
Disk /dev/sde: 16.0 GB, 16039018496 bytes
64 heads, 32 sectors/track, 15296 cylinders, total 31326208 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x22fb6a74
Device Boot Start End Blocks Id System
/dev/sde1 * 0 407551 203776 17 Hidden HPFS/NTFS
I'm not sure what is wrong if it's not working for you.
The block size should make no difference whatsoever. That's just an arbitrary number, big enough to give better I/O efficiency than the dd's default block size of 512 bytes. You could use "bs=143" and still get the same result, just with the kernel doing a lot more work.
so what did you want to achieve exactly? A bootable iso may or may not work on an usb (that means you will not be able to boot the iso image - of a cd/dvd from an usb stick). That depends on how do you write it on the usb stick.
Also dd to /dev/sdb1 and /dev/sdb are different.
windows is not able to do that, you can find programs written for windows which will do things, but also you may find similar programs for linux too.
You still did not answer what do you need....
Hey,
I went into similar problems and finally I found this: https://wiki.ubuntuusers.de/MultiSystem/
You can easily add isos, as many as you want reboot and have a boot loader with all your isos. Links to common live cds are included as well. This tutorial is in german and I didn't find the english version.
You have to download the multisystem.sh plus installing some other packages and then just execute it and it asks you what isos you want to add.
official homepage (french): http://liveusb.info/
windows is not able to do that, you can find programs written for windows which will do things, but also you may find similar programs for linux too.
You still did not answer what do you need....
Sure it does. Been doing it for at least 2 years.
I will use an actual example.
Using Universal USB Installer in Windows XP, I installed tahr-6.0.5_PAE.iso to a 4 Gb Verbatim flash drive.
It is a fully bootable Puppy installation that runs in RAM.
you do not understand what I wrote: windows itself does not do that, just a program named Universal USB Installer. And you will be able to find similar tools for unix too, just you need to explain what do you really want to achieve. dd is not the right one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.