[Voyage-linux] Different PXE Server

John Schultz (spam-protected)
Wed Aug 17 09:24:16 HKT 2011 

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.

So where do I stand with DSL...

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).

So lets see if the SystemRescueCD can do the trick.

Thanks guys,
John

On Tue, Aug 16, 2011 at 11:26, Gustin Johnson <gustin at meganerd.ca> wrote:

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

More information about the Voyage-linux mailing list