Thank you.
> How can I make a bootable - restore CD on an Alpha Personal Workstation 500
> (SRM Miata) running Redhat 7.2.
You need to use a program called isomarkboot. I don't know how it
works.
--
Måns Rullgård
m...@users.sf.net
Pretty well, actually. :-)
If you will type 'isomarkboot' then you will see
isomarkboot filesys path [root.bin]
which admitedly is somewhat cryptic. But
"filesys" refers to an iso9660 file system image you are going
to write to CD. Because it has to be writeable I normally
mount it over a loop device and pass that device as an
argument
"path" is a path to a boot block image; 'aboot' comes with one.
IIRC this is path relative to "filesys". I was not doing
that for a while but once you try for real it is pretty
obvious what it wants.
Don't worry for now about optional "root.bin" (for multi-volume
situations). If you want details read source. It is not very long.
This makes an image bootable from SRM. If you have milo already
loaded (from a hard disk or a floopy) you can boot from it a CD
with a suitable file system on it the same way as you are booting
hard disk. There is no need for further arrangements.
OTOH you really do not need to make any special "restore CD" if you have
7.2 iso installation images. The first disk from this set works very
well in this role. Do not install anything. Just switch to a text
console with a shell prompt (Alt-Ctrl-F2, I think) the moment it is
available and you are in pretty capable Linux environment running from a
ramdisk. Starting a network connection from there, if not already
started, is not that complicated and then you have all you may want
but even without that there is a wide complement of tools.
Michal
"Michal Jaegermann" <mic...@gortel.phys.ualberta.ca> a écrit dans le message
news: b7g0f9$9jg$1...@pulp.srv.ualberta.ca...
If you loaded a corresponding driver then you can use tape.
> There are no /dev/st0 !
/dev indeed has only a small subset of various "special files" but there
is 'mknod' available and nothing prevents you from creating extra ones
when needed. This version of 'mknod' is "smart" enough to know required
majors and minors for many devices. For example 'mknod sdb5' will do
the job so you do not have to remember that this is "8 21". If it is
"st0 aware" then I do not know, as I never tried, but even if not you
can give these numbers explicitely (9 and 0 - BTW).
Device nodes do not have to be in /dev. This is just a convention.
I would probably create is such situation rather /tmp/st0. I do not
remember now if /dev is writable there.
If you have a network connection using a tape mounted on a "remote" may
be even easier depending on circumstances. But there is 'dd', 'tar',
'cpio', various other tools and you can load more (say, via floppies, or
- if this is still "alive" - you can give an explicit path to variety of
"grown-up" tools on your disk) so a tape access should be a no-brainer.
There is still space on this ramdisk and you can really use many things. :-)
Michal