03-30-2009
As you have not had a reply yet I will suggest a method (untried!)
1. As you state slice up the new USB stick as per your old one.
2. With Solaris at this point you would run a command to install the boot block into slice 0, for Linux you either go to a desktop system with the same distro in and and select (System -> Administration -> Create a USB startup disk) or you might try this:
Free Utility To Make Your USB Pen Drive Bootable | Megaleecher.Net
3. Mount up each slice in turn from your stick and the new one (e.g. to .mount/source and /mount/target).
4. Copy with:
find /mount/source | cpio -pdmv /mount/target.
Let the forum know how you get on?
HTH
8 More Discussions You Might Find Interesting
1. SCO
SCO 5.07: How do I copy files to a USB memory stick?
The stick is formatted as a hd and has an active Unix partition using the hole stick for Unix.
How do I get acces to the stick? (1 Reply)
Discussion started by: pschnell
1 Replies
2. UNIX for Dummies Questions & Answers
I have a P-Series Machine running AIX 5.3, it has a USB Port on the front of the server, can I use a USB Stick on AIX platforms?? if so how..:rolleyes: (2 Replies)
Discussion started by: BEVAN
2 Replies
3. SCO
SCO Unix ver 5.07
How do I copy files onto an USB memory stick?
Is SCO Unix ver 5.07 able to handle USB memory devices? (2 Replies)
Discussion started by: Schnell
2 Replies
4. Filesystems, Disks and Memory
Dummies questions, perfect for this. I cannot mount my idiotic usb stick on Slackware, I input the following on non-graphic mode as root:
Mount -t vfat /dev/sdc1/usbstick
usbstick is the folder i created for mounting my USB, the file system is FAT, and everytime I input that I get some kind... (2 Replies)
Discussion started by: Dax01
2 Replies
5. BSD
When mounting a USB stick or pen drive on a FreeBSD machine I always issue the following command:
mount -t msdosfs /dev/da0s1 /mnt
Something I have always wondered is what the option msdosfs stands for and more importantly, why it is necessary. (7 Replies)
Discussion started by: figaro
7 Replies
6. Ubuntu
Hey Guys
I have an Ubuntu CD and I was thinking of creating like a bootable hard drive with various OS so that I can just boot OSs with t drive and not require the CDs. I was just wondering is there a way I can do this, like have Ubuntu boot from a USB stick? If yes how is that possible(even if I... (3 Replies)
Discussion started by: rbansal2
3 Replies
7. SCO
hi
Howto mount an USB stick under SCO 5.0.7?
BTW ist it possible to mount USB stick in the command line using 'tools' at the Boot: prompt from OpenServer Release 5.0.7 installation CD? (1 Reply)
Discussion started by: ccc
1 Replies
8. SCO
I am trying to use a USB (Pen?) drive on Unixware 7.1.4.
The USB stick is in the machine and the machine recognises it when I enter usbprobe as follows:
Path - Address Description
-----------------------------
+++++++ BUS #2
0 - 1 - HUB "UHCI Root Hub"
1 - 2 - HID "Chicony Wireless Device"... (1 Reply)
Discussion started by: BernP
1 Replies
LEARN ABOUT OPENSOLARIS
allkmem
mem(7D) Devices mem(7D)
NAME
mem, kmem, allkmem - physical or virtual memory access
SYNOPSIS
/dev/mem
/dev/kmem
/dev/allkmem
DESCRIPTION
The file /dev/mem is a special file that provides access to the physical memory of the computer.
The file /dev/kmem is a special file that provides access to the virtual address space of the operating system kernel, excluding memory
that is associated with an I/O device.
The file /dev/allkmem is a special file that provides access to the virtual address space of the operating system kernel, including memory
that is associated with an I/O device. You can use any of these devices to examine and modify the system.
Byte addresses in /dev/mem are interpreted as physical memory addresses. Byte addresses in /dev/kmem and /dev/allkmem are interpreted as
kernel virtual memory addresses. A reference to a non-existent location returns an error. See ERRORS for more information.
The file /dev/mem accesses physical memory; the size of the file is equal to the amount of physical memory in the computer. This size may
be larger than 4GB on a system running the 32-bit operating environment. In this case, you can access memory beyond 4GB using a series of
read(2) and write(2) calls, a pread64() or pwrite64() call, or a combination of llseek(2) and read(2) or write(2).
ERRORS
EFAULT Occurs when trying to write(2) a read-only location (allkmem), read(2) a write-only location (allkmem), or read(2) or write(2) a
non-existent or unimplemented location (mem, kmem, allkmem).
EIO Occurs when trying to read(2) or write(2) a memory location that is associated with an I/O device using the /dev/kmem special
file.
ENXIO Results from attempting to mmap(2) a non-existent physical (mem) or virtual (kmem, allkmem) memory address.
FILES
/dev/mem Provides access to the computer's physical memory.
/dev/kmem Provides access to the virtual address space of the operating system kernel, excluding memory that is associated with an
I/O device.
/dev/allkmem Provides access to the virtual address space of the operating system kernel, including memory that is associated with an
I/O device.
SEE ALSO
llseek(2), mmap(2), read(2), write(2)
WARNINGS
Using these devices to modify (that is, write to) the address space of a live running operating system or to modify the state of a
hardware device is extremely dangerous and may result in a system panic if kernel data structures are damaged or if device state is
changed.
SunOS 5.11 18 Feb 2002 mem(7D)