PXE boot Puppy 5.0.1

Booting, installing, newbie
Message
Author
ragtag
Posts: 2
Joined: Wed 09 Jun 2010, 10:00

PXE boot Puppy 5.0.1

#1 Post by ragtag »

Hi,

I have a working server that I use to PXE boot CentOS installations and a GParted live cd, but I wanted to add puppy there too. It basically boots into Ubuntu 9.04 grub, and let's me pick stuff from there.

I've gotten as far as puppy starting to boot, but then it stops with the following error.

Code: Select all

Searching for Puppy files in computer disk drives...lupu-501.sfs not found. Droping out to initial-ramdisk console...
/bin/sh: can't access tty; job control turned off
The grub entry I have looks like this

Code: Select all

label Puppy Live
      menu label Puppy Live
      kernel puppy/puppy-5.0.1/vmlinuz
      append initrd=puppy/puppy-5.0.1/initrd.gz boot=live nfsdir=192.168.0.100:/live/puppy-5.0.1/lupu-501.sfs
I've also tried it with fetch= over http.

I've copied vmlinuz and initrd.gz to their own folder, and they seem to be working, while the rest is in the /live/puppy-5.0.1 share. Any idea how to configure grub to do this correctly?

Cheers,

ragtag


p.s. Hmmm....maybe this post shouldn't have gone into Beginners help. :)

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#2 Post by Béèm »

Beginners is also about booting.

I remember having seen posts about PXE boot.

With the puppysearch link in my sig, you probably find them easily.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

raffy
Posts: 4798
Joined: Wed 25 May 2005, 12:20
Location: Manila

pxe boot

#3 Post by raffy »

Puppy does it by using an initrd.gz that contains the usual initrd plus the program sfs. See an example build for 4.12.

It's to be booted via TFTP: the kernel and then the initrd.gz.

I have no idea yet if Woof (Puppy5 builder) includes initrd creation for PXE-booting.
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#4 Post by jamesbond »

Puppy has all the necessary plumbing for a netboot since Barry's announcement of his humongous experiment (can't remember when, perhaps back to 412 days). Woof may or may not support it, but it's very straightforward to get *any* recent puppies and make it net-boot capable.

Basically all you need to do is to embed the SFS files into initrd.gz. I tried it yesterday with puppy stardust 431, I tried again today with Fatdog64, lupu 500, and puppeee rc5 --- by all means, all of them were never intended for netboot. But netbooting did work ! Amazing isn't ! (Thanks Barry !!!)

Of course your infrastructure must support large file transfer, and your workstation must have enough memory to keep these puppies in memory during the boot. I tested mine with gpxelinux, and hosted the files in a webserver. My test workstation has 512MB of RAM.

cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

zo3adams
Posts: 2
Joined: Thu 10 Jun 2010, 20:52

#5 Post by zo3adams »

Hi jamesbond, can you spell out exactly how you embedded the sfs files into initrd.gz ?

I just tried to replicate your success with lupu 500, placing the file lupu-500.sfs in the initrd-tree under pup_ro2. After repacking and downloading over network I'm getting the same message as with the default initrd.gz:

Code: Select all

lupu-500.sfs not found. Droping out to initial-ramdisk console...
I believe I packed initrd.gz correctly, can see lupu-500.sfs under pup_ro2 from terminal on the client. Is that the appropriate place to insert lupu-500.sfs? Are any additional files needed perhaps ?

My pxelinux.cfg file reads as below, perhaps the arguments need adjustment?

Code: Select all


label wdpup01
  kernel puppy/vmlinuz
  append initrd=puppy/initrd.gz pfix=copy nosmp ramdisk_size=7168 root=/dev/ram0 rw  
edit, tried with this pxeconfig append line trimmed down to just below and got same results:

Code: Select all

  append initrd=puppy/initrd.gz pfix=copy nosmp

raffy
Posts: 4798
Joined: Wed 25 May 2005, 12:20
Location: Manila

ramdisksize

#6 Post by raffy »

Yes, jamesbond, how did you do it?

zo3adams, ramdisksize must be large enough to give room to your initrd.gz, I understand that it is in KB, so multiply by 1024 your MB number.

For history, Barry experimented with humongous initrd in Puppy 2.16, see recap of what was started here.
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#7 Post by jamesbond »

1. Create a temporary directory somewhere
2. Copy the initrd.gz and the pup.sfs you want to embed into this temporary directory.
3. Detach this script, gunzip, and chmod +x the script, in the same temporary directory where you have initrd.gz and pup.sfs
4. Open terminal, and then run the script

Code: Select all

./embed_sfs.sh your-sfs-filename
5. Your original initrd.gz will be kept as initrd.gz.old, and the new initrd.gz will have pup.sfs in it.
There you go. BTW - the ramdisk parameter is unnecessary.

cheers!
Attachments
embed_sfs.sh.gz
gunzip, then chmod +x
(339 Bytes) Downloaded 1481 times
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

ragtag
Posts: 2
Joined: Wed 09 Jun 2010, 10:00

#8 Post by ragtag »

Thanks, that worked like a charm. :)

zo3adams
Posts: 2
Joined: Thu 10 Jun 2010, 20:52

#9 Post by zo3adams »

Indeed; thanks jamesbond! And thanks raffy for the pointer about ramdisk. What a great forum!

For reference, my problem earlier seems to be that I was using an sfs file and initrd.gz from a USB stick installation where I'd made some changes already.
Retrying with an unmodified initrd and sfs file from the lupu-500.iso file everything worked great. Suppose some system info specific to booting from USB was present in my first test.


Thanks again!

jujoboro
Posts: 10
Joined: Wed 02 Jun 2010, 22:03

Can do it with less memory?

#10 Post by jujoboro »

I understood that puppy was a linux lite and we search puppy like an choice to our project (200 hp5000t terminals with netbooting) because its have only 128 Mb in RAM.

We try with debian and work but i find any distro more lite. Can i do it with less than 128 Mb and How?.

Sorry for my english but it's not my Mother language

raffy
Posts: 4798
Joined: Wed 25 May 2005, 12:20
Location: Manila

128 MB

#11 Post by raffy »

You must start with a small Puppy version and remaster it to contain only the applications that you need. Try searching for "fatfree" in this forum.

An initrd.gz of 60 MB or less will work given your 128 MB RAM constraint.

(Please PM me if you need more help.)
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].

rolfm
Posts: 4
Joined: Tue 13 Jul 2010, 19:11

PXE boot Puppy 5.0.1

#12 Post by rolfm »

using the embed_sfs script i get error messages:
cpio: dev/mmcblk0: Cannot mknod: Operation not permitted
cpio: dev/loop10: Cannot mknod: Operation not permitted
cpio: dev/sdc12: Cannot mknod: Operation not permitted
etc

---- is this to be expected?

the script still delivers a new initrd.gz

when i try to pxe boot with it, the proces is killed at the root switch
with a 'kernel panic' message.

i have 512mb ram

--- do i need to give special parameters with the append?

supposing these problems can be solved:
-- is it then possible to work with a diskless pxe client?

any help is appreciated,
rolf

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#13 Post by jamesbond »

Temporary directory must be in linux file system (ext2 or ext3). Best do it inside your /tmp directory.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

rolfm
Posts: 4
Joined: Tue 13 Jul 2010, 19:11

PXE boot Puppy 5.0.1

#14 Post by rolfm »

thanks jamesbond

embed script works in ext2/3 system (btw not in ext4 (?))
boot is ok with a 'regular' computer.

my next obstacle is that PXE boot on a diskless system with 256Mb ram
runs out of memory.

rolf

omf
Posts: 2
Joined: Fri 30 Jul 2010, 23:21

#15 Post by omf »

Starting in the iso dir and the embed-sfs.sh setup in /tmp already here is what I did:

cp initrd.gz /tmp/
cp lupu-501.sfs /tmp/
cd /tmp
./embed_sfs.sh lupu-501.sfs

I get the following output

Code: Select all

cpio: dev/mmcblk0: Cannot mknod: Operation not permitted
cpio: dev/loop10: Cannot mknod: Operation not permitted
cpio: dev/sdc12: Cannot mknod: Operation not permitted
cpio: dev/hda1: Cannot mknod: Operation not permitted
cpio: dev/hda9: Cannot mknod: Operation not permitted
cpio: dev/sdc13: Cannot mknod: Operation not permitted
cpio: dev/hdd1: Cannot mknod: Operation not permitted
cpio: dev/loop0: Cannot mknod: Operation not permitted
cpio: dev/sdb3: Cannot mknod: Operation not permitted
cpio: dev/tty3: Cannot mknod: Operation not permitted
cpio: dev/sdb7: Cannot mknod: Operation not permitted
cpio: dev/sde1: Cannot mknod: Operation not permitted
cpio: dev/hdb2: Cannot mknod: Operation not permitted
cpio: dev/sdb13: Cannot mknod: Operation not permitted
cpio: dev/scd3: Cannot mknod: Operation not permitted
cpio: dev/hda2: Cannot mknod: Operation not permitted
cpio: dev/loop4: Cannot mknod: Operation not permitted
cpio: dev/loop1: Cannot mknod: Operation not permitted
cpio: dev/sr1: Cannot mknod: Operation not permitted
cpio: dev/kmsg: Cannot mknod: Operation not permitted
cpio: dev/sdb: Cannot mknod: Operation not permitted
cpio: dev/loop3: Cannot mknod: Operation not permitted
cpio: dev/hda11: Cannot mknod: Operation not permitted
cpio: dev/sde2: Cannot mknod: Operation not permitted
cpio: dev/sda14: Cannot mknod: Operation not permitted
cpio: dev/hdb8: Cannot mknod: Operation not permitted
cpio: dev/hdb3: Cannot mknod: Operation not permitted
cpio: dev/sdd4: Cannot mknod: Operation not permitted
cpio: dev/sdf1: Cannot mknod: Operation not permitted
cpio: dev/sde: Cannot mknod: Operation not permitted
cpio: dev/sda6: Cannot mknod: Operation not permitted
cpio: dev/ram: Cannot mknod: Operation not permitted
cpio: dev/sda9: Cannot mknod: Operation not permitted
cpio: dev/sdf6: Cannot mknod: Operation not permitted
cpio: dev/hda3: Cannot mknod: Operation not permitted
cpio: dev/sda2: Cannot mknod: Operation not permitted
cpio: dev/sdc7: Cannot mknod: Operation not permitted
cpio: dev/sde5: Cannot mknod: Operation not permitted
cpio: dev/hdd6: Cannot mknod: Operation not permitted
cpio: dev/sdi1: Cannot mknod: Operation not permitted
cpio: dev/sdb4: Cannot mknod: Operation not permitted
cpio: dev/hda14: Cannot mknod: Operation not permitted
cpio: dev/sdc2: Cannot mknod: Operation not permitted
cpio: dev/sdc3: Cannot mknod: Operation not permitted
cpio: dev/hdc7: Cannot mknod: Operation not permitted
cpio: dev/sde4: Cannot mknod: Operation not permitted
cpio: dev/sdc11: Cannot mknod: Operation not permitted
cpio: dev/sdb9: Cannot mknod: Operation not permitted
cpio: dev/scd0: Cannot mknod: Operation not permitted
cpio: dev/sdc5: Cannot mknod: Operation not permitted
cpio: dev/sdh1: Cannot mknod: Operation not permitted
cpio: dev/hda13: Cannot mknod: Operation not permitted
cpio: dev/hdd2: Cannot mknod: Operation not permitted
cpio: dev/sdf5: Cannot mknod: Operation not permitted
cpio: dev/sdi: Cannot mknod: Operation not permitted
cpio: dev/sda3: Cannot mknod: Operation not permitted
cpio: dev/sdd6: Cannot mknod: Operation not permitted
cpio: dev/hdb1: Cannot mknod: Operation not permitted
cpio: dev/tty4: Cannot mknod: Operation not permitted
cpio: dev/scd1: Cannot mknod: Operation not permitted
cpio: dev/tty1: Cannot mknod: Operation not permitted
cpio: dev/hdd4: Cannot mknod: Operation not permitted
cpio: dev/sdb6: Cannot mknod: Operation not permitted
cpio: dev/sdc10: Cannot mknod: Operation not permitted
cpio: dev/sde8: Cannot mknod: Operation not permitted
cpio: dev/sdc14: Cannot mknod: Operation not permitted
cpio: dev/mmcblk0p1: Cannot mknod: Operation not permitted
cpio: dev/sdh: Cannot mknod: Operation not permitted
cpio: dev/sdc6: Cannot mknod: Operation not permitted
cpio: dev/sr3: Cannot mknod: Operation not permitted
cpio: dev/fd0: Cannot mknod: Operation not permitted
cpio: dev/hdb4: Cannot mknod: Operation not permitted
cpio: dev/hdc1: Cannot mknod: Operation not permitted
cpio: dev/hdd8: Cannot mknod: Operation not permitted
cpio: dev/sda10: Cannot mknod: Operation not permitted
cpio: dev/sdd3: Cannot mknod: Operation not permitted
cpio: dev/sde7: Cannot mknod: Operation not permitted
cpio: dev/hdd7: Cannot mknod: Operation not permitted
cpio: dev/sdg2: Cannot mknod: Operation not permitted
cpio: dev/sdf8: Cannot mknod: Operation not permitted
cpio: dev/sdc15: Cannot mknod: Operation not permitted
cpio: dev/sdb15: Cannot mknod: Operation not permitted
cpio: dev/sde6: Cannot mknod: Operation not permitted
cpio: dev/hda7: Cannot mknod: Operation not permitted
cpio: dev/sdb8: Cannot mknod: Operation not permitted
cpio: dev/hdb6: Cannot mknod: Operation not permitted
cpio: dev/sdd1: Cannot mknod: Operation not permitted
cpio: dev/hdb7: Cannot mknod: Operation not permitted
cpio: dev/sdc: Cannot mknod: Operation not permitted
cpio: dev/loop2: Cannot mknod: Operation not permitted
cpio: dev/sdb1: Cannot mknod: Operation not permitted
cpio: dev/sdc4: Cannot mknod: Operation not permitted
cpio: dev/sda1: Cannot mknod: Operation not permitted
cpio: dev/sde3: Cannot mknod: Operation not permitted
cpio: dev/hdc: Cannot mknod: Operation not permitted
cpio: dev/loop7: Cannot mknod: Operation not permitted
cpio: dev/hdd5: Cannot mknod: Operation not permitted
cpio: dev/rtc: Cannot mknod: Operation not permitted
cpio: dev/sdf3: Cannot mknod: Operation not permitted
cpio: dev/hdc4: Cannot mknod: Operation not permitted
cpio: dev/sdf: Cannot mknod: Operation not permitted
cpio: dev/sdc9: Cannot mknod: Operation not permitted
cpio: dev/sda15: Cannot mknod: Operation not permitted
cpio: dev/sdf7: Cannot mknod: Operation not permitted
cpio: dev/hda6: Cannot mknod: Operation not permitted
cpio: dev/sdf2: Cannot mknod: Operation not permitted
cpio: dev/sdc1: Cannot mknod: Operation not permitted
cpio: dev/sdd5: Cannot mknod: Operation not permitted
cpio: dev/sda11: Cannot mknod: Operation not permitted
cpio: dev/null: Cannot mknod: Operation not permitted
cpio: dev/ram0: Cannot mknod: Operation not permitted
cpio: dev/ram1: Cannot mknod: Operation not permitted
cpio: dev/hda8: Cannot mknod: Operation not permitted
cpio: dev/sda5: Cannot mknod: Operation not permitted
cpio: dev/sr0: Cannot mknod: Operation not permitted
cpio: dev/sda8: Cannot mknod: Operation not permitted
cpio: dev/hdc8: Cannot mknod: Operation not permitted
cpio: dev/loop5: Cannot mknod: Operation not permitted
cpio: dev/hdb: Cannot mknod: Operation not permitted
cpio: dev/hdd3: Cannot mknod: Operation not permitted
cpio: dev/hdc2: Cannot mknod: Operation not permitted
cpio: dev/hda15: Cannot mknod: Operation not permitted
cpio: dev/sdd: Cannot mknod: Operation not permitted
cpio: dev/sdg: Cannot mknod: Operation not permitted
cpio: dev/mmcblk0p2: Cannot mknod: Operation not permitted
cpio: dev/sdi2: Cannot mknod: Operation not permitted
cpio: dev/hda16: Cannot mknod: Operation not permitted
cpio: dev/sda: Cannot mknod: Operation not permitted
cpio: dev/hdc5: Cannot mknod: Operation not permitted
cpio: dev/zero: Cannot mknod: Operation not permitted
cpio: dev/console: Cannot mknod: Operation not permitted
cpio: dev/tty2: Cannot mknod: Operation not permitted
cpio: dev/hda4: Cannot mknod: Operation not permitted
cpio: dev/hdc6: Cannot mknod: Operation not permitted
cpio: dev/sdb14: Cannot mknod: Operation not permitted
cpio: dev/hda5: Cannot mknod: Operation not permitted
cpio: dev/sr2: Cannot mknod: Operation not permitted
cpio: dev/sdb10: Cannot mknod: Operation not permitted
cpio: dev/scd2: Cannot mknod: Operation not permitted
cpio: dev/sdd7: Cannot mknod: Operation not permitted
cpio: dev/fuse: Cannot mknod: Operation not permitted
cpio: dev/systty: Cannot mknod: Operation not permitted
cpio: dev/sdd8: Cannot mknod: Operation not permitted
cpio: dev/sda7: Cannot mknod: Operation not permitted
cpio: dev/fb0: Cannot mknod: Operation not permitted
cpio: dev/sdb5: Cannot mknod: Operation not permitted
cpio: dev/hdb5: Cannot mknod: Operation not permitted
cpio: dev/sdc8: Cannot mknod: Operation not permitted
cpio: dev/hda10: Cannot mknod: Operation not permitted
cpio: dev/loop9: Cannot mknod: Operation not permitted
cpio: dev/loop6: Cannot mknod: Operation not permitted
cpio: dev/sda13: Cannot mknod: Operation not permitted
cpio: dev/hda: Cannot mknod: Operation not permitted
cpio: dev/sdd2: Cannot mknod: Operation not permitted
cpio: dev/sdb2: Cannot mknod: Operation not permitted
cpio: dev/tty0: Cannot mknod: Operation not permitted
cpio: dev/sda4: Cannot mknod: Operation not permitted
cpio: dev/sdb12: Cannot mknod: Operation not permitted
cpio: dev/hdc3: Cannot mknod: Operation not permitted
cpio: dev/tty: Cannot mknod: Operation not permitted
cpio: dev/sdb11: Cannot mknod: Operation not permitted
cpio: dev/hdd: Cannot mknod: Operation not permitted
cpio: dev/sdh2: Cannot mknod: Operation not permitted
cpio: dev/sda12: Cannot mknod: Operation not permitted
cpio: dev/sdg1: Cannot mknod: Operation not permitted
cpio: dev/sdf4: Cannot mknod: Operation not permitted
cpio: dev/hda12: Cannot mknod: Operation not permitted
cpio: dev/loop8: Cannot mknod: Operation not permitted
4930 blocks
258635 blocks
Done. Initrd now contains lupu-501.sfs. Your old initrd is kept as initrd.gz.old
and the file size: 130518322 2010-07-30 19:34 initrd.gz

I am using ext4 for my filesystem which according to rolfm does not work. So I created an opensuse 11.3 server install inside of virtualbox and specify ext3 as the filesystem during the installer.

Repeating the above process inside the virtualbox I get the same output as before from cpio. The filesize of the output is different: 130519413 2010-07-04 19:31 initrd.gz

So I tried to PXE boot a client with each of the above initrd.gz files.

Here is the pxelinux.cfg/default config file:

Code: Select all

LABEL 6
  KERNEL puppy_5/vmlinuz 
  APPEND keeppxe initrd=puppy_5/initrd.gz
Attached is a screenshot of the client output. I am stuck as to how I can get this process to work for me.
Attachments
puppy_bug.jpg
Screenshot of the bug
(30.73 KiB) Downloaded 2753 times

rolfm
Posts: 4
Joined: Tue 13 Jul 2010, 19:11

PXE boot Puppy 5.0.1

#16 Post by rolfm »

i did the embed_sfs in Puppy /tmp

omf
Posts: 2
Joined: Fri 30 Jul 2010, 23:21

#17 Post by omf »

i did the embed_sfs in Puppy /tmp
With that in mind here is what I did.

I created a virtualbox with 1 gb RAM so I could do all the work in RAM and had it boot the Puppy 5.0.1 iso.

Next I used the mount icon on the desktop to mount the iso and copy the files needed to temp. Typed in the commands and the initrd.gz generated works perfectly being launched over the network, thanks rolfm.

So the next step is to configure it for my purposes.

I used this pxelinux.cfg/default setup:

Code: Select all

LABEL 6
  KERNEL puppy_5/vmlinuz 
  APPEND initrd=puppy_5/initrd.gz nousb acpi=off pfix=nox,ram pkeys=us
The error generated can be seen in the attached image. After the 60 second timeout I have to setup country and timezone. I would like to set all three options so the end user in this process has less work to do.

I cannot find options to set the locale and gmt via booting options. Some references I looked at were http://www.murga-linux.com/puppy/viewto ... 2a412a8d9e and the wiki http://pupweb.org/wikka/BootParms

Do I need to setup the files in initrd.gz to automate this process?
Attachments
pxe_pkeys_error.jpg
Pkeys error during pxe boot
(48.92 KiB) Downloaded 693 times

rolfm
Posts: 4
Joined: Tue 13 Jul 2010, 19:11

PXE boot Puppy 5.0.1

#18 Post by rolfm »

sorry omf, i can't help you with that

fred777
Posts: 4
Joined: Sat 08 Jan 2011, 21:27

pxe boot puppy 5.2

#19 Post by fred777 »

Hi there,

the nice embed_sfs.sh script from this post: http://www.murga-linux.com/puppy/viewto ... 267#426299 does not work anymore for puppy 5.2.
It did work for versions 5.0.1 and 5.1. Please help.

thanks,
fred

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#20 Post by jamesbond »

fred,

The embed.sh script doesn't do anything other than unpack the initrd.gz, put the puppy.sfs into it, and pack it back.

The actual magic that makes it work (puppy reads the SFS inside initrd.gz instead of searching from disk or elsewhere) is inside puppy initialisation script itself. This originally came from Barry, in puppy 4.x days, and is shared by many many other puplets and derivatives (so that most of them are netboot capable as well).

Now, apparently enough things have changed in between Lupu 5.1 days and Lupu 5.2 that breaks this functionality. You can try a recent puppy (e.g wary 5.0) and see whether it works. If it does work, then the original code is still there and something broke in Lupu 5.2 when it was developed. If this is the case, you can report this to Lupu 5.2 support forum and hope for a fix.

If wary 5.0 itself doesn't do netboot anymore, then the code is broken "at the source", and you should report this to Barry, again, hoping for a fix.

EDIT: Wary 5.0 also has this problem, so I guess Lupu 5.2 just "inherits" the same problem. I've reported this to Wary 5.0 bug report thread, let's hope it get Barry's ear.

Alternatively, if you're interested, you can unpack initrd.gz and look at the file called "init", and go from there ...

cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

Post Reply