Title: Re: [Sisuite-users] livecd problems
Right, but I think there's an even simplier way:

--append "STRING"  A string of options that will be passed to the autoinstall
                   kernel.
 
(from si_mkautoinstallcd --help)

Just append the string during AutoInstallCD creation - voila.
 
Cheers,
 
Bernard


From: [EMAIL PROTECTED] on behalf of Andrea Righi
Sent: Thu 13/04/2006 00:35
To: [email protected]
Subject: Re: [Sisuite-users] livecd problems

IMHO changing the kernel boot parameters is a simpler way... you have
only to edit the syslinux.cfg file... it's the same thing to edit a
local.cfg file... or am I missing something?

Regards,
-Andrea

scott gamble wrote:
> Hi um, that sounds insane.  Reconfigure your DHCP server or add kernel
> boot arguments.  Or have an additional floppy.  Theres no way to put a
> simple local.cfg text file in a location that the livecd iso tool will
> include when building the iso?
>
> I mean Boot CD's are by far the most common medium to address this kind
> of issue.  Nobodys run across this and found a real fix?  All three of
> those suggestions sound like an akward hack (no offense) to what should
> be in my minds eye a simple and fundamental function of SI.  Do you not
> agree?
>
> S
>
> Andrea Righi wrote:
>> scott gamble wrote:
>>> When booting from the livecd it runs through its checks fine and locates
>>> the DHCP server and pulls an address like its suppose to (DHCP is being
>>> handled by my IPCOP router) but then (me looking at the logs) it appears
>>> the LiveCD assumes the DHCP server is also the image server.  In the
>>> instructions it recommends putting your image server on the same box as
>>> your dhcp server but it does not say its required to do so.  The LiveCD
>>> does a ping verification against the dhcp server, says congrats you have
>>> network connectivity to the image server and tries to establish an rsync
>>> connection and - psht, craps out (because its trying to pull an image
>>> from the router/dhcp server and not the image server).
>>> DHCP is on .1 and the image server is on like .225 on a /24 so nowhere
>>> near each other.
>>
>> If you can configure your dhcp server, simply add these options to
>> dhcpd.conf:
>>
>> # Imageserver
>> option option-140 code 140 = text;
>> # option-140 is the IP address of your SystemImager image server
>> option option-140 "<IP_of_your_image_server>";
>>
>> Otherwise you can override the ip of the image server adding
>> IMAGESERVER=<ip_of_you_image_server> to the kernel boot parameters,
>> usually changing the /etc/systemimager/pxelinux.cfg/syslinux.cfg and run
>> si_mkautoinstallcd again...
>>
>> Regards,
>> -Andrea
>>


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to