[Voyage-linux] Different PXE Server - SUCCESS!!!

[Gustin Johnson]

You could probably ditch the root=LABEL=ROOT_FS parameter since it
only applies to local disks with that particular label (well
technically it is the partition that has the label).

I am concerned about the nfs user being root, almost every default NFS
config I have seen squashes the root user (and for good reason).

On Fri, Aug 19, 2011 at 6:40 PM, John Schultz <jschultz0614 at gmail.com> wrote:
> I have successfully gotten voyage-linux live ISO to boot from a Windows SBS
> 2003 PXE environment and its a ROYAL pain in the behind.
>
> 1. Create a NFS share on a linux (in my case, this was a debain 0.6.0a
> server)
> 2. Configure /etc/exports with the following information:
>    {NFS/folder/to/Share} *(rw,async,no_root_squash,no_subtree_check)
> 3. Copy the contents of the live CD to this folder
> 4. Copy the {CD}/live/vmlinuz1 to your tftp folder
>    {TFTP Server}/linux/voyage/0.7.5/vmlinuz1
> 5. Copy the {CD}/live/initrd1.img to your tftp folder
>    {TFTP Server}/linux/voyage/0.7.5/initrd1.img
> 6. Configure your default config file with the following information:
>    {This by far is an example, configure this to suit your needs}
>>
>> DEFAULT      vesamenu.c32
>> PROMPT       0
>> NOESCAPE     0
>> ALLOWOPTIONS 0
>> TIMEOUT 30
>> MENU WIDTH 40
>> MENU MARGIN 0
>> MENU ROWS 12
>> MENU TIMEOUTROW 14
>> MENU HSHIFT 5
>> MENU VSHIFT 2
>> MENU COLOR BORDER 30;44       #00000000 #00000000 none
>> MENU COLOR TABMSG 1;36;44     #00000000 #00000000 none
>> MENU COLOR TITLE 1;36;44     #00000000 #00000000 none
>> MENU COLOR SEL   30;47       #40000000 #20ffffff
>> MENU BACKGROUND DeploymentBackground.png
>>
>> MENU TITLE PXE Boot menu
>> MENU WIDTH 80
>> MENU MARGIN 18
>> MENU ROWS 25
>>
>> LABEL    voyage075
>> MENU    DEFAULT
>> MENU    LABEL Voyage Linux 0.7.5
>> KERNEL    linux/voyage/0.7.5/vmlinuz1 root=LABEL=ROOT_FS
>> INITRD    linux/voyage/0.7.5/initrd1.img
>> APPEND    boot=live netboot=nfs
>> nfsroot=10.0.0.17:/export/voyage-one-current username=root
>
> That should do it.
>
> Any questions, let me know.
>
> Thanks,
> John
>
>
> On Fri, Aug 19, 2011 at 12:13, John Schultz <jschultz0614 at gmail.com> wrote:
>>
>> OK,.. I was able to get it to appear to connect to the NFS share and
>> connect to the sysrcd.dat file, however, I get a md5sum checksum is invalid
>> on the root filesystem image error.
>>
>> Just to be sure, I downloaded the iso and extracted the dat file a second
>> time.
>>
>>
>> On Fri, Aug 19, 2011 at 09:30, Gustin Johnson <gustin at meganerd.ca> wrote:
>>>
>>> My PXE config looks like this;
>>>
>>> LABEL System Rescue CD "Live Image"
>>>        LINUX systemrescue/rescuecd
>>>        INITRD systemrescue/initram.igz
>>>        APPEND scandelay=1 docache
>>> netboot=nfs://192.168.1.10:/images/systemrescue setkmap=us toram
>>>        TEXT
>>>        SystemRescueCD network boot image (recovery)
>>>        ENDTEXT
>>>
>>> The 192.168.1.10 is also the PXE server, but it could be any machine.
>>> You can also ignore the TEXT/ENDTEXT bit, it is just for the onscreen
>>> menu (we have a customized FOG install that this is part of).
>>>
>>> The Linux and INITRD options are paths that exist under the root of
>>> the TFTP server.
>>> The relevant line from the /etc/exports file:
>>>
>>> /images/systemrescue
>>>
>>> *(rw,sync,no_wdelay,insecure_locks,no_root_squash,insecure,no_subtree_check)
>>>
>>
>
>