SCIENTIFIC-LINUX-USERS Archives

April 2006

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lars Wilke <[log in to unmask]>
Reply To:
Lars Wilke <[log in to unmask]>
Date:
Fri, 28 Apr 2006 18:12:52 +0200
Content-Type:
multipart/mixed
Parts/Attachments:
text/plain (2133 bytes) , p1 (15 kB) , p2 (11 kB)
Hi,

thanks for the fast reply :)

* Connie Sieh wrote:
> On Fri, 28 Apr 2006, Lars Wilke wrote:
> > * Lars Wilke wrote:
> > > The setup and customization was straight forward but after generating
> > > ISO images and booting from these i get the normal behaviour of booting
> > > scientific linux. My customization in the isolinux directory under
> > > sites/<mysite>/build/ are ignored. Though the README states that i should
> >
> > I found the problem. The cd generating script references files which i
> > named different. isolinux.cfg.iso but mine is isolinux.cfg etc.
>
> This is to allow for a different isolinux.cfg.iso for the full cd set.
>
> I will revisit the documentation to make this clearer.

No problem. Was not to hard to find. More irritating was the that some
part search for things under <mysite>/ARCH/... and some parts directly
under <mysite>/... though i gues to stream line all scripts is not an easy
task.

> > > While we are at it. I'd like to use only one cd for the iso images.
> > > Is it enough to change the make.cdisos.sh script?
>
> I will get back with on this one as it is more complicated than just
> changing the make.cdisos.sh script.

Hm, i just did it a few hours ago. Needed an hour or so. Ok, i have absolutly
no clue if i did break anything. Sadly the error described further down comes
if i use the original script or my version :(

If you want i can send you my version. It is just a trimmed down version of
your script. BTW i am using only disk 1 from SL, so i am pretty sure i doesn't
need more space than one finds normally on a cdr :) 

> > But now i have a new problem. The CD boots fine and everything but when the
> > loader (?) is trying to load my kickstart config it complains that the
> > used cdrom is not a Scientific Linux CD?
> > Hmpf, i really have no clue atm where to fix that.
>
> Where does your kickstart expect to find the release at?

As far as i can see the ks.cfg is found and anaconda tries to mount and access
/mnt/source/site/<mysite>.
IIUC this is an anaconda problem.

I am attaching a screenshot of the boot messages. Both are in png format.
I use a vmware exp installation to test the isos.

regards

   --lars


ATOM RSS1 RSS2