(old)Puppy Linux Discussion Forum

I temporarily moved rc.network out or /etc/rc.d. Now I put it back but it keeps disappearing after I reboot. Is this whole directory getting copied from somewhere else? I can't figure out why the file is no longer there after I reboot. Please help. Thanks!

Hello Edwin- for the rest of the board, Pup 5.0, right?

At this point, your best bet is to start a clean install.

Semme wrote:Hello Edwin- for the rest of the board, Pup 5.0, right?

Yes, I'm running Puppy 5.0. Any idea why this could happen?

(Sorry, I forgot to watch the topic before, thus the slow reply.)

Maybe boot live, replacing this file >> /etc/rc.d/rc.sysinit.

Keep in mind rc.network's executable.

Semme wrote:Maybe boot live, replacing this file >> /etc/rc.d/rc.sysinit.

Keep in mind rc.network's executable.

I'm not sure what you mean by boot live. I'm already running Puppy off an SD card. What should I do to boot live?

SD cards aside, puppy pfix=ram should allow you to boot live.

Semme wrote:SD cards aside, puppy pfix=ram should allow you to boot live.

I don't understand. How can it boot from ram? Isn't that non-persistent memory? What do you mean by boot live?

I don't run a hard install so, if ya can't boot live, I guess it ain't gonna happen.

What you can do is dwnld the iso and extract what'cha need- save'n replace.

I guarantee nothing..

If you are running in frugal mode :
Check for wipeout files ! These are hidden files named like

.wh.

These are blocking things . Try to locate them in the save-file.2fs in
/initrd/pup_ro2/etc/rc.d/.wh.rc.network
and delete it/them and try to copy again.

NOTE : directly in the save-file !! The RAM folders'n'files still are copied into the save file at regular shutdown - but .wh. files are blocking things without giving you hints/error-messages then .

Karl Godt wrote:If you are running in frugal mode :
Check for wipeout files ! These are hidden files named like

.wh.

These are blocking things . Try to locate them in the save-file.2fs in
/initrd/pup_ro2/etc/rc.d/.wh.rc.network
and delete it/them and try to copy again.

NOTE : directly in the save-file !! The RAM folders'n'files still are copied into the save file at regular shutdown - but .wh. files are blocking things without giving you hints/error-messages then .

Thank you! I don't have these in pup_ro2 but I do have these in pup_ro1.

/initrd$ find . -iname *\.wh*
./pup_ro1/usr/sbin/.wh.xorg-setup
./pup_ro1/usr/sbin/.wh.fixicons
./pup_ro1/.wh..wh.orph
./pup_ro1/.wh..wh.plnk
./pup_ro1/etc/rc.d/.wh.rc.network_basic
./pup_ro1/etc/rc.d/.wh.rc.network
./pup_ro1/dev/.wh.sdb1
./pup_ro1/dev/.wh.mixer
./pup_ro1/dev/.wh.sequencer2
./pup_ro1/dev/.wh.sequencer
./pup_ro1/dev/.wh.dsp
./pup_ro1/dev/.wh.audio
./pup_ro1/dev/.wh.sdb
./pup_rw/.wh..wh.orph
./pup_rw/.wh..wh.plnk
./pup_rw/.wh..wh.aufs

Is this the issue then? What is the difference between ro1 and ro2? How do you think I got into this problem?

The /initrd/pup_ro[1-2] depends on the kind of frugal installation . Since i run Puppy as full installs mainly and occasionaly as frugal from HDD with save-file I myself get confused with the naming of the /initrd/* directories :

/init wrote:#decide the mount-points...
#unionfs layers: RW (top) RO1 RO2 PUPMODE
#full install, flash drive: tmpfs PDEV1 3
#First boot (or pfix=ram): tmpfs pup_xxx.sfs 5
#pup_save is a partition: PDEV1 pup_xxx.sfs 6
#ditto, but flash drive: tmpfs PDEV1 pup_xxx.sfs 7
#Normal running puppy: pup_save.3fs pup_xxx.sfs 12
#ditto, but flash drive: tmpfs pup_save.3fs pup_xxx.sfs 13
#Multisession cd/dvd: tmpfs folders(tmpfs2) pup_xxx.sfs 77

shows that you run Puppy from USB Pendrive .

To Look inside the /init code of the initrd.gz _compressed_archive_file look here :

Pizzasgood wrote:First, put initrd.gz somewhere on a Linux filesystem (I tend to use /tmp/NewDir). Open a terminal there and do this to extract it:
Code:
mkdir initrd-tree
cd initrd-tree/
zcat ../initrd.gz | cpio -i -d

Now the contents are inside initrd-tree/

http://murga-linux.com/puppy/viewtopic. ... 64&t=24899

How do you think I got into this problem?

Since the SPACE is named whitespace everywhere, the wipeouts are named "whiteouts" officially . They occure whenever there is a deletion somewhere . It seems to me that you needed to run alsa-wizard to gain sound also .