I have been trying to integrate LTSP-5 in fedora/ RHEL for the exactly
same reasons. I have given up.
Basically, the boot process is as you described it - the best way how to
learn it is to unpack/mount the initrd file from Ubuntu to see how are
things managed.
You will see that standard Fedora/RHEL initrd file is a way simpler than
the one found in Ubuntu.
If you really want to spend a few days integrating this you have
basically 3 options:
1. write your own initrd for RHEL that will do all the network/NFS
initializations
2. take the scripts found in Ubuntus initrd to build something similar
for RHEL
3. RHEL/Fedora has its own stateless Linux project - diskless
Workstation - which does something similar. You could download the
system-config-netboot package which does all the initrd/NFS/image things
and amend it to do LTSP instead of diskless workstation.

I personally would go with the third option as it is most promising
(least time spent to get things working).
Ondrej

David A. Kennel wrote:
> Inline . . .
> Jim McQuillan wrote:
>   
>> David A. Kennel wrote:
>>   
>>     
>>> So I've been through the LTSP source tree and I have an Ubuntu 
>>> installation to examine and compare to. I'm however a little fuzzy on 
>>> exactly what I need in the initramfs and kernel. On LTSP <= 4.2 the 
>>> kernel required the IPautoconfig, DHCP and NFS root options and the 
>>>     
>>>       
>> LTSP hasn't used IPautoconfig for many years.  before LTSP-3 I think.
>>
>> We do the dhcp and nfs requests in userspace in the initrd/initramfs.
>>   
>>     
> OK, that's helpful to know. I must have missed that change I thought I 
> remembered those options as being required in the LTSP 4 Kernel Kit. So 
> what needs to be in the initrd to do the DHCP and NFS requests? (Aside 
> from the obvious, dhcpcd and nfs utilities.)
>   
>>   
>>     
>>> initramfs image had to contain a number of packages from the LTSP kernel 
>>> kit. The documentation references using an unmodified kernel but then 
>>> using a modified initramfs with NFS root support. Can someone elaborate 
>>> on what is needed here?
>>>     
>>>       
>> "needed" ?   I don't know what you are trying to accomplish, so I can't 
>> comment on what's needed.
>>   
>>     
> I'm trying to package/integrate LTSP v 5 for RHEL 4, and eventually, 
> RHEL 5. ( RHEL is our standard for most deployments and we cannot easily 
> move to using Debian/Ubuntu for our LTSP servers . . .). So my 
> requirements are similar to the work being done on the Debian/Ubuntu 
> integration of LTSP with modifications for the Red Hat way of doing 
> things (Red Hat Update Servers, etc.).
>
> So as I understand the boot process we need to boot a kernel and 
> associated initrd via PXE. Then we will do a DHCP request in user space 
> using dhcpcd in the initrd. After network configuration we do a NFS 
> mount request for the client root on the server. How is the pivot root 
> handled in LTSP 5, or is that no longer needed as well?
>   
>> Jim McQuillan
>> [EMAIL PROTECTED]
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems?  Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >>  http://get.splunk.com/
>> _____________________________________________________________________
>> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
>> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>>   
>>     
>
>   


The information contained in this e-mail and in any attachments is confidential 
and is designated solely for the attention of the intended recipient(s). If you 
are not an intended recipient, you must not use, disclose, copy, distribute or 
retain this e-mail or any part thereof. If you have received this e-mail in 
error, please notify the sender by return e-mail and delete all copies of this 
e-mail from your computer system(s).
Please direct any additional queries to: [EMAIL PROTECTED]
Thank You.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to