public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* making custom iso images
@  brian Moore
   ` brian Moore
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: brian Moore @  UTC (permalink / raw)
  To: speakup

Greetings all.  Actually, I am following up on my thread from the other
day about putting speakup into a server distro of linux.  I have an iso
image of the sme server distribution I want to use.  thanks to Bill, I
have the identical kernel version rpms for redhat to match the
installation cd for this distro.  I have never attempted to build an
iso image before.  basically, on my test box, I want to modify the sme
isoimage by replacing the kernel rpms included with the ones I got from
octothorp and then make an iso image I can burn to cd and do an
installation on to another machine to see if ti works before i do this
to the machine which is running my mail ftp, etc.

wonder if this will work or break all kinds of things.  I will also
have to modify their ks.cfg file to change the boot prompt default
label to pass speakup parameters.

Have never created a cd inlinux before having always cheated and used
easy cd creator 5

will just replacing the kernel rpms on a cd and then doing an
installation give me the new kernel or the original one on the cd which
the machine will boot from?

guess it will be an opportunity to learn some new stuff.  any pointers
to creating iso images under linux would be cool  I can always copy the
image to my windows box and burn it there but that is less of a
challenge.

will see what happens.

thanks.  Brian.




^ permalink raw reply	[flat|nested] 5+ messages in thread
* making custom iso images
@  brian Moore
  0 siblings, 0 replies; 5+ messages in thread
From: brian Moore @  UTC (permalink / raw)
  To: speakup

greetings, well, didn't think of all that.  thanks.  will give it a
shot and se what I can do.

Brian.


>
>      Since you're using ks.cfg, I'll guess that your distro uses
> Anaconda.
> Install the anaconda and anaconda-runtime RPMs.  mount the CD and use
cp
> -a to copy the contents to your HDD.  Replace the RPM packages you
find
> there with the modified ones.  You speak of CD in the singular.  RH7
had
> two.  If you only have one, cd to /usr/lib/anaconda-runtime type:
> "./genhdlist <path_to_installation_tree>".  If you have two Cd's
you'll
> need to copy both of them to the HDD.  The genhdlist command would
> look like
> this: "./genhdlist <path1> <path2> --withnumbers".  If you really
want to
> go all the way, and you're sure that the version of Anaconda is the
same
> for SME and RH7.0, you could download the Anaconda packages from the
same
> place you got the kernel packages.  They have the Speakup keymap
built in.
> The buildinstall command in the /usr/lib/\anaconda-runtime directory
will
> make a completely new installation tree.  Since you use kickstart,
this
> might not be very important to you.  Now for the CD.  You can use the
> strings command on the raw CD image to extract the commandline of the
> mkisofs command that was used to create them.  Pipe to grep mkisofs.
> You'll want to edit out the version number such as 1.13.  If you have
any
> questions, call or write.
>
>
>
>
>           HTH.



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 making custom iso images brian Moore
 ` brian Moore
 ` Geoff Shang
 ` William F. Acker WB2FLW +1-303-777-8123
 brian Moore

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).