Salix OS

Why do you want to reinvent the wheel? You should use the tools that are just there. Though, it is possible to improve them.
I've edited my post about FAI with a quote of the main features. FAI seems to provide support for PXE and other network protocols out-of-the-box.

schlawi54 wrote:Why do you want to reinvent the wheel? You should use the tools that are just there. Though, it is possible to improve them.
I've edited my post about FAI with a quote of the main features. FAI seems to provide support for PXE and other network protocols out-of-the-box.

Now who are you (actually you just sort of gave us another hint ) to tell people what they should do or not do?
At least pwatk is doing something constructive & tinkering away and doing will always beat mere Google copy-pasting.
Keep going pwatk, network install are definitely very useful. If you didn't get much feedback on the ML, it could simply have been that it was at a time when folks had other things on their hand & couldn't tune in or simply because your post was bit succinct or whatever.
Don't let that deter you, if you do come up with something useful & functional, I'm sure you'll get plenty of feedback then.

schlawi54 wrote:Why do you want to reinvent the wheel?

Thats not strictly true, I'm just trying to reinstate functions that already exist but have been disabled during Salix development. Once this is complete *then* we can add the extra functions for NFS, SMB and FTP.
I'm not trying to dismiss FAI for what it is (it actually looks very interesting), it's just not exactly what I wanted!

Akuna wrote:Keep going pwatk, network install are definitely very useful. If you didn't get much feedback on the ML, it could simply have been that it was at a time when folks had other things on their hand & couldn't tune in or simply because your post was bit succinct or whatever. Don't let that deter you, if you do come up with something useful & functional, I'm sure you'll get plenty of feedback then.

Thanks for the encouragement

Well despite my hacking efforts I can get this to work.

I've rebuilt busybox (same version) adding in udhcpc, updated all the libraries in /lib and added lspci because of errors but now I'm stuck with these errors (this also happens on a real system):



I'm not sure how to proceed without rebuilding the whole thing from scratch so I think I'll wait for a 13.2 alpha before I lose my mind on this .

IMO the current Slax/LLS PXE system is really crap anyway. For example, if I'm gonna PXE boot the livecd then I'm more than likely gonna have my own server to do it; I'm not gonna reboot my server box to boot the livecd *just* so I can PXE boot it on another machine. Sure this is a nice *feature* but a simple from={http{,s}://,ftp://,//,}192.168.x.x/path/image.iso would work so much better and based on what I've read is exactly what the Slax community asked for.

pwatk wrote:IMO the current Slax/LLS PXE system is really crap anyway.

This is one of the reason we dropped LLS for the Live CDs to come.

I'll be ready to test it when ever it's done.

sorry to bump and old thread but I just discovered that you can set up a PXE-server using just the install disc of Slackware 13.37
and it's a pretty painless process too http://alien.slackbook.org/blog/out-of- ... ware-13-37
I wonder if the same functionality will be available in future versions of Salix as well?

You can already do this with the 13.37 beta installation discs.

Just boot the kernel and ramdisk from your PXE boot server then point the installer towards an NFS, Samba, HTTP or FTP server where you've put either an ISO image of an installation disc (except for FTP) or it's contents.

I've created a basic README for pre-configuring some of the options if you interested:
http://people.salixos.org/pwatk/initrd- ... unattended

Edit: Forgot to mention, I'll try to take a look at the pxesetup script changes and see if I can work it in to the Salix setup scripts. I doubt I'll get this done by the time 13.37.0 is released though.