In all honesty, all I need is a PXE environment to "deploy" voyage from. If its a rescue CD, so be it. At this point in time, this issue has been going on since 7-19-2011 and in all seriousness, seriously NEEDS to be resolved so I can get on to other issues.<br>
<br>So where do I stand with DSL...<br><br>I need to mount a ISO from a remote system or mount a remote file resource. then THATS it. The other option is to make a 200MB voyage PXE boot install image (which at this point is not a viable option IMHO).<br>
<br>So lets see if the SystemRescueCD can do the trick.<br><br>Thanks guys,<br>John<br><br><div class="gmail_quote">On Tue, Aug 16, 2011 at 11:26, Gustin Johnson <span dir="ltr"><<a href="mailto:gustin@meganerd.ca">gustin@meganerd.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I have the systemrescuecd distro booting from my PXE environment (both<br>
at home and at the office) which is a heavily customized FOG install.<br>
<br>
Systemrescuecd provides SMB/CIFS and various other protocols (NFS, and<br>
I think sshfs). DSL is really too lightweight to be useful IMO.<br>
<div><div></div><div class="h5"><br>
On Mon, Aug 15, 2011 at 12:28 PM, John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>> wrote:<br>
> Got an answer from Experts-Exchange:<br>
><br>
>> it looks like I should be doing a NFS mapping instead<br>
>> we said this 50 posts ago...<br>
>><br>
>> NFS is in everywhere but you dedided to go with DSL that its no much more<br>
>> than a kernel and 2 commands then what do you expect..<br>
>> mounting a remote iso, as an ISO? well for those things you have NFS...<br>
><br>
> My reply is as follows:<br>
>><br>
>> I know about the NFS mounting from awhile back, at the time, some of the<br>
>> things I learned by this process hadn't come to light yet.<br>
>><br>
>> Also, Im still not aware of doing an NFS mapping via the actual PXE<br>
>> environment. Im only aware of the mapping after you have a prompt up and<br>
>> running. If this is not the case, sorry I did not realize that before. If it<br>
>> IS possible with out having to have to go through the trouble of specifying<br>
>> a rootfs, kernel and/or initrd, I have no idea how to do that. So for now,<br>
>> the DSL environment is the closest Ive come to a solution.<br>
>><br>
>> Anyway, at least I learned a few things along the way.<br>
><br>
><br>
> On Mon, Aug 15, 2011 at 08:16, John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>> wrote:<br>
>><br>
>> OK,... slight setback... Looks like samba is not the best idea for linux<br>
>> to linux (who knew ;p). Anyway, it looks like I should be doing a NFS<br>
>> mapping instead, however it also looks like an nfs client is not installed<br>
>> on DSL vs 2, 3 or 4. Unless I am missing something. Anyway, when I issue<br>
>> "mount -t nfs4 -o proto=tcp,port=2049 debian:/voyage-one-current<br>
>> /mnt/voyage", I get an error message stating that the module nfs4 is missing<br>
>> (also tried nfs2 and nfs3).<br>
>><br>
>> Is there an easy way to mount a remote share, nfs or samba (at this point<br>
>> I will take ANYTHING), where I can "mount" a resource in order to run some<br>
>> scripts?<br>
>><br>
>> For that matter, is it possible to mount a remote ISO?<br>
>><br>
>> Thanks guys,<br>
>> John<br>
>><br>
>><br>
>> On Sun, Aug 14, 2011 at 20:00, John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> WHOOOO HOOOOO!!!!!<br>
>>><br>
>>> Alright.... Here is where I stand....<br>
>>><br>
>>> 1. I have DamnSmallLinux PXE loading and I am able to get a bash shell.<br>
>>><br>
>>> 2. I have a 212MB squash (Voyage One Current v0.7.5) file that I need<br>
>>> access to and can not package the DSL image with, so I am going to need to<br>
>>> Samba share it from my Debian Server<br>
>>><br>
>>> 3. Install Voyage from the Samba share to the CF card on the Alex 3D3<br>
>>> running DSL PXE.<br>
>>><br>
>>> 4. Reboot and in theory, this issue can FINALLY be closed.<br>
>>><br>
>>> :)<br>
>>><br>
>>> And that will be worked on tomorrow.<br>
>>><br>
>>><br>
>>><br>
>>> On Sat, Aug 13, 2011 at 08:45, John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> OK, Michael....<br>
>>>><br>
>>>> Thanks for the sample boot files, however those did not work for me<br>
>>>> either. I also tried to use the parameters with those initrd and vmlinuz<br>
>>>> files from 0.6.5 stable from you with 0.7.5 release.<br>
>>>><br>
>>>> Ive noticed all along that the error message is "can't access tty; job<br>
>>>> control turned off" Does this mean that the live setup is in fact meant for<br>
>>>> a serial connection? If so, I am up the creek as I do not have a serial<br>
>>>> cable (nul modem cable) to connect to this board, hence the reason Ive been<br>
>>>> using console all along.<br>
>>>><br>
>>>> Is there a way to compile my existing debian box setup in a network boot<br>
>>>> image?<br>
>>>><br>
>>>> Thanks again,<br>
>>>> John<br>
>>>><br>
>>>> On Fri, Aug 5, 2011 at 20:12, John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> Unfortunately, I am using a Windows SBS 2003 Server with WDS installed<br>
>>>>> for my PXE Server.<br>
>>>>><br>
>>>>> An Idea that just occurred to me is to create a custom Debian Live ISO<br>
>>>>> with the voyage source package built in and then install from there.<br>
>>>>><br>
>>>>> I will have to play with some ideas and then report back my findings.<br>
>>>>><br>
>>>>> Thanks,<br>
>>>>> John<br>
>>>>><br>
>>>>> On Wed, Aug 3, 2011 at 13:12, Michael Steinmann<br>
>>>>> <<a href="mailto:mike.steinmann@gmail.com">mike.steinmann@gmail.com</a>> wrote:<br>
>>>>>><br>
>>>>>> if I remember correct this is the error message I got with newer<br>
>>>>>> Voyage versions (even with some newer daily v0.6.5):<br>
>>>>>> /bin/sh: can't access tty; job control turned off<br>
>>>>>> (initramfs)<br>
>>>>>><br>
>>>>>> the correct setting should be:<br>
>>>>>> console=tty1<br>
>>>>>> but I don't think this helps.<br>
>>>>>><br>
>>>>>> I don't know why it's not working with newer versions anymore...<br>
>>>>>> have you really tried with all the files I provided in the rar with<br>
>>>>>> the same folder structure?<br>
>>>>>> don't put filesystem.squashfs in a subfolder like /pxe/voyage/. Try<br>
>>>>>> putting the Voyage files vmlinuz1, initrd1.img and filesystem.squashfs in<br>
>>>>>> the tftp root folder.<br>
>>>>>><br>
>>>>>> I have this setup on a pfSense for some reasons, but as Punky said PXE<br>
>>>>>> server should work straight forward on a Voyage installation.<br>
>>>>>><br>
>>>>>> /michael<br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> 2011/8/3 John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>>>>>>><br>
>>>>>>> OK,.. I have tried the suggestions you suggested in your first email<br>
>>>>>>> today and I get the following:<br>
>>>>>>>><br>
>>>>>>>> Loading linux/voyage/vmlinuz1<br>
>>>>>>>> Loading linux/voyage/initrd1.img<br>
>>>>>>>> early console in setup code<br>
>>>>>>>> early console in decompress_kernel<br>
>>>>>>>><br>
>>>>>>>> Decompressing Linux... Parsing ELF... done.<br>
>>>>>>>> Booting the kernel.<br>
>>>>>>><br>
>>>>>>> and then nothing - no network activity whatsoever.<br>
>>>>>>><br>
>>>>>>> Here is my menu section config:<br>
>>>>>>>><br>
>>>>>>>> LABEL Voyage<br>
>>>>>>>> MENU DEFAULT<br>
>>>>>>>> MENU LABEL Voyage<br>
>>>>>>>> KERNEL linux/voyage/vmlinuz1<br>
>>>>>>>> APPEND initrd=linux/voyage/initrd1.img boot=live<br>
>>>>>>>> fetch=<a href="http://jsch-svr-01/linux/pxe/voyage/filesystem.squashfs" target="_blank">http://jsch-svr-01/linux/pxe/voyage/filesystem.squashfs</a> live-getty<br>
>>>>>>>> noautologin all_generic_ide debug console=ttyS0,38400n8<br>
>>>>>>><br>
>>>>>>> I then tried taking off the ttyS0 param, rebooted and I got the<br>
>>>>>>> following output:<br>
>>>>>>>><br>
>>>>>>>> Bunch of linux load crap<br>
>>>>>>>><br>
>>>>>>>> BusyBox v1.17.1 (Debian 1:1.17.1.-8) Built-in shell (ash)<br>
>>>>>>>> Enter 'help' for a list of built-in commands.<br>
>>>>>>>><br>
>>>>>>>> /bin/sh: can't access tty; job control turned off<br>
>>>>>>>> (initranfs)<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> That became evident that my console settings are not correct. What is<br>
>>>>>>> the correct tty console setting for a regular console setup (no serial<br>
>>>>>>> connectivity)?<br>
>>>>>>><br>
>>>>>>> This is by far the closest Ive been to a solution in 3 weeks then I<br>
>>>>>>> ever have been.<br>
>>>>>>><br>
>>>>>>> If this works, I owe you a pizza from the pie (:p)<br>
>>>>>>><br>
>>>>>>> On Wed, Aug 3, 2011 at 07:57, Michael Steinmann<br>
>>>>>>> <<a href="mailto:mike.steinmann@gmail.com">mike.steinmann@gmail.com</a>> wrote:<br>
>>>>>>>><br>
>>>>>>>> that probably was version 0.6.5 stable, actually I just tried it and<br>
>>>>>>>> it still works :-)<br>
>>>>>>>> this is the PXE menu entry:<br>
>>>>>>>><br>
>>>>>>>> LABEL Voyage<br>
>>>>>>>> MENU LABEL ^Voyage 0.6.5<br>
>>>>>>>> KERNEL voyage-0.6.5.stable/vmlinuz1<br>
>>>>>>>> APPEND initrd=voyage-0.6.5.stable/initrd1.img boot=live<br>
>>>>>>>> fetch=tftp://<a href="http://192.168.100.1/voyage-0.6.5.stable.filesystem.squashfs" target="_blank">192.168.100.1/voyage-0.6.5.stable.filesystem.squashfs</a><br>
>>>>>>>> live-getty noautologin all_generic_ide debug console=ttyS0,38400n8<br>
>>>>>>>><br>
>>>>>>>> and here is uname -a output:<br>
>>>>>>>> Linux voyage 2.6.30-voyage #1 PREEMPT Wed Dec 30 18:39:44 GMT 2009<br>
>>>>>>>> i586 GNU/Linux<br>
>>>>>>>><br>
>>>>>>>> I could put the whole thing for download somewhere, if you can't get<br>
>>>>>>>> it working.<br>
>>>>>>>> how far do you get? what's the error message?<br>
>>>>>>>><br>
>>>>>>>> michael<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> 2011/8/3 John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>>>>>>>>><br>
>>>>>>>>> Definitely need to know what version you were able to do this on. I<br>
>>>>>>>>> tried this under 0.7.5 and it totally blew chuncks.<br>
>>>>>>>>><br>
>>>>>>>>> Thanks.,<br>
>>>>>>>>> John<br>
>>>>>>>>><br>
>>>>>>>>> On Wed, Aug 3, 2011 at 07:26, John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>>>>>>>>> wrote:<br>
>>>>>>>>>><br>
>>>>>>>>>> I tried that (unfortunately it did not work), Since, I posted this<br>
>>>>>>>>>> issue on experts exchange and thats where I found the two referenced links.<br>
>>>>>>>>>> Just for sake of argument, I will try this again and see if I can get it to<br>
>>>>>>>>>> work.<br>
>>>>>>>>>><br>
>>>>>>>>>> Do you know off hand what version of Voyage you were using at the<br>
>>>>>>>>>> time this worked for you?<br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> On Wed, Aug 3, 2011 at 06:04, Michael Steinmann<br>
>>>>>>>>>> <<a href="mailto:mike.steinmann@gmail.com">mike.steinmann@gmail.com</a>> wrote:<br>
>>>>>>>>>>><br>
>>>>>>>>>>> Hi John,<br>
>>>>>>>>>>><br>
>>>>>>>>>>> this is from some other thread a while a go...<br>
>>>>>>>>>>> see the attached rar, but the files from the ISO are missing<br>
>>>>>>>>>>> this worked for me, at least it did with older voyage ISOs.<br>
>>>>>>>>>>><br>
>>>>>>>>>>> Best regards,<br>
>>>>>>>>>>><br>
>>>>>>>>>>> Michael Steinmann<br>
>>>>>>>>>>><br>
>>>>>>>>>>><br>
>>>>>>>>>>><br>
>>>>>>>>>>><br>
>>>>>>>>>>> ---------- Forwarded message ----------<br>
>>>>>>>>>>> From: Michael Steinmann <<a href="mailto:mike.steinmann@gmail.com">mike.steinmann@gmail.com</a>><br>
>>>>>>>>>>> Date: 2011/7/16<br>
>>>>>>>>>>> Subject: Re: [Voyage-linux] Different PXE Server<br>
>>>>>>>>>>> To: John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>>>>>>>>>>><br>
>>>>>>>>>>><br>
>>>>>>>>>>> ignore the file mntfs.<br>
>>>>>>>>>>> see the attached rar, but the files from the ISO are missing<br>
>>>>>>>>>>><br>
>>>>>>>>>>> /michael<br>
>>>>>>>>>>><br>
>>>>>>>>>>><br>
>>>>>>>>>>> 2011/7/16 Michael Steinmann <<a href="mailto:mike.steinmann@gmail.com">mike.steinmann@gmail.com</a>>:<br>
>>>>>>>>>>> > no, not the ISO. open the ISO and you will find the files to<br>
>>>>>>>>>>> > copy to<br>
>>>>>>>>>>> > the PXE server. in this case these are the files:<br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > vmlinuz1<br>
>>>>>>>>>>> > initrd1.img<br>
>>>>>>>>>>> > filesystem.squashfs<br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > and according to the following two lines they are all in the<br>
>>>>>>>>>>> > voyage directory:<br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > KERNEL voyage/vmlinuz1 root=LABEL=ROOT_FS<br>
>>>>>>>>>>> > console=ttyS0,38400n8<br>
>>>>>>>>>>> > APPEND initrd=voyage/initrd1.img fs=voyage/filesystem.squashfs<br>
>>>>>>>>>>> > boot=live netboot=fs<br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > this is the tree:<br>
>>>>>>>>>>> > ¦ memdisk<br>
>>>>>>>>>>> > ¦ menu.c32<br>
>>>>>>>>>>> > ¦ mntfs<br>
>>>>>>>>>>> > ¦ pxelinux.0<br>
>>>>>>>>>>> > ¦<br>
>>>>>>>>>>> > +---pxelinux.cfg<br>
>>>>>>>>>>> > ¦ default<br>
>>>>>>>>>>> > ¦<br>
>>>>>>>>>>> > +---voyage<br>
>>>>>>>>>>> > ¦ vmlinuz1<br>
>>>>>>>>>>> > ¦ initrd1.img<br>
>>>>>>>>>>> > ¦ filesystem.squashfs<br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > /michael<br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > <a href="mailto:614@gmail.com">614@gmail.com</a>>:<br>
>>>>>>>>>>> >> OK, so if I understand you correctly, this script goes on my<br>
>>>>>>>>>>> >> PXE Server<br>
>>>>>>>>>>> >> along with the live ISO and that should do it? I thought you<br>
>>>>>>>>>>> >> had to have a<br>
>>>>>>>>>>> >> kernel image and an initrd image.<br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >> FYI,.. my setup is as follows:<br>
>>>>>>>>>>> >> PXE/DHCP Server: Windows SBS 2003 Premium<br>
>>>>>>>>>>> >> Clients: multiple Alix.3D3 SBCs<br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >> PXE Environment has been slightly modified to use isolinux<br>
>>>>>>>>>>> >> derivative.<br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >> Thanks,<br>
>>>>>>>>>>> >> John<br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >> On Sat, Jul 16, 2011 at 07:53, Michael Steinmann<br>
>>>>>>>>>>> >> <<a href="mailto:mike.steinmann@gmail.com">mike.steinmann@gmail.com</a>><br>
>>>>>>>>>>> >> wrote:<br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>> that's true,<br>
>>>>>>>>>>> >>> for vga console change console=ttyS0,38400n8 to console=tty1<br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>> /Michael<br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>> 2011/7/16 John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>>:<br>
>>>>>>>>>>> >>> > This looks like a config file for a serial connection. Is<br>
>>>>>>>>>>> >>> > that intended?<br>
>>>>>>>>>>> >>> > The<br>
>>>>>>>>>>> >>> > systems I am using are the Alix 3D3 which uses a usb port<br>
>>>>>>>>>>> >>> > for a keyboard<br>
>>>>>>>>>>> >>> > and<br>
>>>>>>>>>>> >>> > a vga port for a console instead of a serial connection.<br>
>>>>>>>>>>> >>> ><br>
>>>>>>>>>>> >>> > On the other hand, Ive been at this since 3am so I could be<br>
>>>>>>>>>>> >>> > confused<br>
>>>>>>>>>>> >>> > :-p.<br>
>>>>>>>>>>> >>> ><br>
>>>>>>>>>>> >>> > Thanks again.<br>
>>>>>>>>>>> >>> > John<br>
>>>>>>>>>>> >>> ><br>
>>>>>>>>>>> >>> ><br>
>>>>>>>>>>> >>> > On Sat, Jul 16, 2011 at 07:40, Michael Steinmann<br>
>>>>>>>>>>> >>> > <<a href="mailto:mike.steinmann@gmail.com">mike.steinmann@gmail.com</a>><br>
>>>>>>>>>>> >>> > wrote:<br>
>>>>>>>>>>> >>> >><br>
>>>>>>>>>>> >>> >> this is what my pxelinux.cfg\default looked like for<br>
>>>>>>>>>>> >>> >> v0.6.2,<br>
>>>>>>>>>>> >>> >> indicating the necessary files:<br>
>>>>>>>>>>> >>> >><br>
>>>>>>>>>>> >>> >> SERIAL 0 38400<br>
>>>>>>>>>>> >>> >><br>
>>>>>>>>>>> >>> >> DEFAULT menu.c32<br>
>>>>>>>>>>> >>> >> ALLOWOPTIONS 0<br>
>>>>>>>>>>> >>> >> PROMPT 0<br>
>>>>>>>>>>> >>> >> TIMEOUT 0<br>
>>>>>>>>>>> >>> >><br>
>>>>>>>>>>> >>> >> MENU TITLE Server PXE Boot Menu<br>
>>>>>>>>>>> >>> >><br>
>>>>>>>>>>> >>> >> LABEL Voyage<br>
>>>>>>>>>>> >>> >> MENU LABEL ^Voyage 0.6.2<br>
>>>>>>>>>>> >>> >> KERNEL voyage/vmlinuz1 root=LABEL=ROOT_FS<br>
>>>>>>>>>>> >>> >> console=ttyS0,38400n8<br>
>>>>>>>>>>> >>> >> APPEND initrd=voyage/initrd1.img<br>
>>>>>>>>>>> >>> >> fs=voyage/filesystem.squashfs<br>
>>>>>>>>>>> >>> >> boot=live netboot=fs<br>
>>>>>>>>>>> >>> >><br>
>>>>>>>>>>> >>> >><br>
>>>>>>>>>>> >>> >> #Michael<br>
>>>>>>>>>>> >>> >><br>
>>>>>>>>>>> >>> >><br>
>>>>>>>>>>> >>> >> 2011/7/16 John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>>:<br>
>>>>>>>>>>> >>> >> > What files need to be copied to my PXE Server in order<br>
>>>>>>>>>>> >>> >> > to install<br>
>>>>>>>>>>> >>> >> > Voyage<br>
>>>>>>>>>>> >>> >> > from the network?<br>
>>>>>>>>>>> >>> >> ><br>
>>>>>>>>>>> >>> >> > My PXE Server is not the live CD.<br>
>>>>>>>>>>> >>> >> ><br>
>>>>>>>>>>> >>> >> > Thanks in advance,<br>
>>>>>>>>>>> >>> >> > John<br>
>>>>>>>>>>> >>> >> ><br>
>>>>>>>>>>> >>> >> > _______________________________________________<br>
>>>>>>>>>>> >>> >> > Voyage-linux mailing list<br>
>>>>>>>>>>> >>> >> > <a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>
>>>>>>>>>>> >>> >> > <a href="http://list.voyage.hk/mailman/listinfo/voyage-linux" target="_blank">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
>>>>>>>>>>> >>> >> ><br>
>>>>>>>>>>> >>> >> ><br>
>>>>>>>>>>> >>> ><br>
>>>>>>>>>>> >>> ><br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> ><br>
>>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>><br>
>>>>>>><br>
>>>>>><br>
>>>>><br>
>>>><br>
>>><br>
>><br>
><br>
><br>
</div></div></blockquote></div><br>