duplicating different filesystem

[satimis]

Hi folks,

I have DSL 2.2b running on /dev/hda5 on ext 2 with grub as bootloader. I have /dev/sda1 of a pendrive running on FAT16 which is a MUST otherwise the BIOS unable to boot it. I'm testing to run DSL on the pendrive using grub as bootload.

Would it be possible to duplicate /dev/hda5 on /dev/sda1 the later having 800M in capacity sufficient for DSL 2.2b to run. They are of different filesystem.

I tried follows without success;

1)
# cp -aRx /mnt/hda5/* /mnt/sda1/

....
....
cp: cannot create symbolic link `/mnt/sda1/etc/rc5.d/S49dsl_restore': Operation not permitted
cp: cannot create symbolic link `/mnt/sda1/etc/rc5.d/S99bootlocal': Operation not permitted
cp: cannot create symbolic link `/mnt/sda1/etc/rc6.d/K20pcmcia': Operation not permitted
cp: cannot create symbolic link `/mnt/sda1/etc/rc6.d/K79nfs-common': Operation not permitted
cp: cannot create symbolic link `/mnt/sda1/etc/rc6.d/S90knoppix-reboot': Operation not permitted
cp: cannot create symbolic link `/mnt/sda1/etc/rcS.d/S00knoppix-autoconfig': Operation not permitted
cp: cannot create symbolic link `/mnt/sda1/etc/rcS.d/S01dsl-config': Operation not permitted
cp: cannot create symbolic link `/mnt/sda1/etc/rcS.d/S35devpts.sh': Operation not permitted
cp: cannot create symbolic link `/mnt/sda1/etc/resolv.conf': Operation not permitted
cp: cannot create symbolic link `/mnt/sda1/etc/samba': Operation not permitted
cp: failed to preserve ownership for `/mnt/sda1/etc/shadow': Operation not permitted

I have to stop it manually.


2)
# (cd /mnt/hda5 && tar -clpsf- *) | (cd /mnt/sda1 && tar -xpsf -)

...
...
tar: dev/tty25: Cannot mknod: Operation not permitted
tar: dev/tty26: Cannot mknod: Operation not permitted
tar: dev/tty27: Cannot mknod: Operation not permitted
tar: dev/tty28: Cannot mknod: Operation not permitted
tar: dev/tty29: Cannot mknod: Operation not permitted
tar: dev/tty3: Cannot mknod: Operation not permitted
tar: dev/tty30: Cannot mknod: Operation not permitted
tar: dev/tty31: Cannot mknod: Operation not permitted
tar: dev/tty32: Cannot mknod: Operation not permitted
tar: dev/tty33: Cannot mknod: Operation not permitted
tar: dev/tty34: Cannot mknod: Operation not permitted
tar: dev/tty35: Cannot mknod: Operation not permitted
tar: dev/tty36: Cannot mknod: Operation not permitted
tar: dev/tty37: Cannot mknod: Operation not permitted
tar: dev/tty38: Cannot mknod: Operation not permitted
tar: dev/tty39: Cannot mknod: Operation not permitted

I have to stop it manually.


3)
# (cd /mnt/hda5 && tar -cpsf- *) | (cd /mnt/sda1 && tar -xpsf -)

...
......
tar: dev/sdb8: Cannot mknod: Operation not permitted
tar: dev/sdb9: Cannot mknod: Operation not permitted
tar: dev/sdc: Cannot mknod: Operation not permitted
tar: dev/sdc1: Cannot mknod: Operation not permitted
tar: dev/sdc10: Cannot mknod: Operation not permitted
tar: dev/sdc11: Cannot mknod: Operation not permitted
tar: dev/sdc12: Cannot mknod: Operation not permitted
tar: dev/sdc13: Cannot mknod: Operation not permitted
tar: dev/sdc14: Cannot mknod: Operation not permitted
tar: dev/sdc15: Cannot mknod: Operation not permitted
tar: dev/sdc2: Cannot mknod: Operation not permitted
tar: dev/sdc3: Cannot mknod: Operation not permitted
tar: dev/sdc4: Cannot mknod: Operation not permitted
tar: dev/sdc5: Cannot mknod: Operation not permitted
tar: dev/sdc6: Cannot mknod: Operation not permitted

I have to stop it manually.

Advice would be appreciated. TIA

B.R.
satimis

[Game master pro]

Stupid question maybe...are you doing this as root?

Edit: why not just install DSL to /dev/sda1 instead of copying the contents of the partition that it is installed on, somehow i doubt that will work

[satimis]

Hi Game master pro,

I did them as root

Edit: why not just install DSL to /dev/sda1 instead of copying the contents of the partition that it is installed on, somehow i doubt that will work

I'm trying making the pendrive as HD with Grub as bootloader. The HD of the PC has a partition running DSL with Grub as bootloader.

I have no problem to install DSL on a pendrive on FS FAT16, ZIP geometry using syslinux to boot.

B.R.
satimis

[Cabhan]

Hey. You might look into the dd utility, which is designed for block device copying. I have used it successfully before to backup a partition to a file, then rewrite the partition elsewhere using that file. The syntax for you would be:

dd if=/dev/hda5 of=/dev/sda1 conv=notrunc

That is:
dd - invoke 'dd', obviously
if - input from
of - output to
conv - special conversion options (in this case, don't try to truncate the output location, as it's a block device, not a file)

Also, this may be stupid, but I assume that sda1 is mounted to allow read/write permissions? Even if you're root, if the mount doesn't allow rw, you cannot write to the device.

[CodeRoot]

It appears that FAT16 simply cannot handle symbolic links or special files...

[satimis]

Hi folks,

Tks for your advice.

The problem is FAT16 does not hanlle symbolic link and device nodes. I have been searching intensively on Interent. Some links suggest to have 3 partitions;


partition-1 FAT 32 - empty
partition-2 ext2 for OS
partition-3 ext2 bootable for grub bootloader

I haven't figured how to make my pendrive to work according to such arrangement. But the folks there said such arrangement is possible making the pendrive to boot with grub bootloader.

Now I begin to suspect whether my pendrive, Avixe Platinum Drive, does not support such building. However it works nicely on zip-geometry with syslinux as bootloader.

B.R.
satimis

[Cabhan]

I'm curious as to why you can't make the pen drive conform to such a partition scheme. I've partitioned my own pen drive numerous times (when I first got it, it had some freaky scheme), and I've been able to have multiple partitions at once.

What's preventing you from doing the partitioning?