Getting Pup2 to see the pup_save.3fs file at boot up

Under development: PCMCIA, wireless, etc.
Post Reply
Message
Author
wilcal
Posts: 14
Joined: Thu 26 Jan 2006, 18:36
Location: San Diego, CA

Getting Pup2 to see the pup_save.3fs file at boot up

#1 Post by wilcal »

Lots of good things are working for me with Pup2
except I'm not understanding how to get it to
sense and use the previously saved pup_save.3fs
file at boot up from the Live-CD. During
shutdown I can successfully direct the file to be
written to a floppy or hd, but, I don't see where
in the boot up sequence it can find or asks for it.

This message was created and sent from the below
system running Pup2

Test Platform
----------------

P600 - Test System
Pentium III (Coppermine), 600Mhz, 256Kb Cache
440BX MoBo
DIMM1 128MB, DIMM2 128MB = 256MB
ATI Rage 128 GL AGP 1x/2x 32MB All-In-Wonder TV Tune/out
SoundBlaster Live (snd-emu10k1 driver)
USB Intel 82371AB PIIX4
D-Link DFE 530 TX+ Fast Ethernet
DVD-ROM (hda) Hitachi DVD-ROM GD-2500
CD-RW (hdb) Sony CRX140E
Floppy 1.44MB
KingWin HD Rack/Tray subsystem (Multiple HD's)
Boot Sequence: Floppy -> DVD-ROM -> HD

Media Utility Tool 0.0.7b info
fdo: floppy formated and working. pup_save.3fs succcessfully written
hda::Hitachi DVD-ROM GD-2500 Mounts ok. Contains Pup2 Live-CD
hdb:: Sony CD-RW CRX140E
hde:: Quantum Fireball 5GB IDE HD
hde1: 586 Linux Swap active and working
hde5:ext3 2570MB Mounts. pup_save.3fs successfully written
hde6:ext3 1839MB Mounts. pup_save.3fs successfully written

Thanks for any hints.
"DISK BOOT FAILURE - INSERT SYSTEM DISK AND PRESS ENTER"
is my friend
User avatar
Flash
Official Dog Handler
Posts: 13071
Joined: Wed 04 May 2005, 16:04
Location: Arizona USA

#2 Post by Flash »

Puppy2 alpha is a rough sketch. Barry is filling it in. Don't expect perfection just yet.

That said, when I boot Puppy2a it finds the pup file it created in the ext3 partition of my hd8.
dominic
Posts: 66
Joined: Mon 30 Jan 2006, 16:54
Location: UK

#3 Post by dominic »

Don't quote me on this, but logic would suggest that it calls it somewhere in initrd. In a NORMAL;) distro, initrd, is loaded into the ram as like a mini OS just to get the basics going, then it calls the proper OS, which part of it is pup_save.3fs
User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#4 Post by BarryK »

wilcal,
At the first shutdown, you chose somewhere to save the session, like a hard drive
partition or floppy disk or usb drive, and Puppy2 then created pup_save.3fs on
it.

At bootup, the "init" script has the code that searches for pup_save.3fs.
It seems in your case that the search is failing.
Firstly, verify that you do actually have a pup-save.3fs file to find.
Then, look at /initrd/sbin/init -- that's the first boot script, and it has a function
called "searchsavefunc" that is supposed to locate pup_save.3fs.

...if you have some knowledge of scripting, you could pull that code out to
a separate script and run it, see what it finds. Then, you could find out where
it is going wrong...
...then let me know!
User avatar
Puppy Dog
Posts: 58
Joined: Sat 21 May 2005, 13:53

#5 Post by Puppy Dog »

When I save to floppy using puppyalpha2 a pup_save.2fs file is created.

( File rwx, r-x,r-x/---root 1423k) please pardon dash placement

Would a pup_save.2fs file be picked up on reboot? I`m not getting

anything to save,or is this possibly a BIOS reajustment problem?

Or a pup_save.3fs vs. pup_save.2fs problem ?
"Best In Show"
User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#6 Post by BarryK »

The floppy drive is a special case, as it doesn't have enough
room for a ext3 f.s., so a ext2 f.s. is created and the file is
called pup_save.2fs.
The function "searchsavefunc" is supposed to work for
pup_save.2fs on a floppy also.
wilcal
Posts: 14
Joined: Thu 26 Jan 2006, 18:36
Location: San Diego, CA

#7 Post by wilcal »

Well I got one of my computers to properly save and restore
the Pup2 pup_save.3fs file. It appears, at least with this machine,
that so long as the file is on an "a" hd in this case hda1
then during boot up Pup2 sees the file and restores the
session back to where it was. The machine described above
uses:

hde1: 586 Linux Swap active and working
hde5:ext3 2570MB Mounts. pup_save.3fs successfully written
hde6:ext3 1839MB Mounts. pup_save.3fs successfully written

"e" hd's

Pup2 does not see these hde drives/partitions at bootup

I'll fiddle some more with this thing later on.
"DISK BOOT FAILURE - INSERT SYSTEM DISK AND PRESS ENTER"
is my friend
User avatar
Puppy Dog
Posts: 58
Joined: Sat 21 May 2005, 13:53

#8 Post by Puppy Dog »

1. During reboot after pup_save.2fs creation, I noticed
in the startup procedure:

"disktype: Can`t stat dev/fd0 no such file or directory"

2. During the creation process of pup_save.2fs, I noticed

"creatingpup_save.2fs in dev/fd0
dd:writing please wait-----

1424 + 0 records in
1423 + 0 records out



I have not created a swap partition yet, in an effort to
isolate this floppy problem.

When I remove the hard drive, no partition option
GUI appears, and I have to pull the plug.

I hope this helps.

Love sea monkey, by the way- and the clean shutdown
with hard drive attached.
"Best In Show"
Guest

#9 Post by Guest »

Puppy Dog wrote:I have not created a swap partition yet, in an effort to
isolate this floppy problem.
Do note that in playing around with the Pup2
boot process I think I have identified some
sensitivty to how your hd is structured especially
where the swap drive is located. I still have
some testing to do but one thing I have done
is to move the swap drive from the first partition
to the last. Also to create at least 2 partitions
plus the swap. This stucture is probably wrong:

hde1: 586 Linux Swap active and working
hde5:ext3 2570MB Mounts. pup_save.3fs successfully written
hde6:ext3 1839MB Mounts. pup_save.3fs successfully written

For one thing Pup2 seems to not understand the "e"
drive. It does understand and see an "a" drive as
in hda1, hda2, hda3 ect ect. Also if the swap drive
is first as in hde1 above or even hda1 then Pup2
won't or can't search beyond that.

I'll give it another look tonight and post the partition
structure that works best for me.

Do note that this process of choices in the boot up
and boot down in Pup2 is seriously better then
what was happening in Pup1. Great concept so far.
wilcal
Posts: 14
Joined: Thu 26 Jan 2006, 18:36
Location: San Diego, CA

#10 Post by wilcal »

Sorry I'm guest above

Works
-----
hda1: ext3 5125MB Mounts. pup_save.3fs successfully written/boots
hda5: 1217MB Linux Swap

Works
-----
hda1: 1217MB Linux Swap
hda5: ext3 5125MB Mounts. pup_save.3fs successfully written/boots
"DISK BOOT FAILURE - INSERT SYSTEM DISK AND PRESS ENTER"
is my friend
User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#11 Post by BarryK »

Puppy Dog wrote:1. During reboot after pup_save.2fs creation, I noticed
in the startup procedure:

"disktype: Can`t stat dev/fd0 no such file or directory"

2. During the creation process of pup_save.2fs, I noticed

"creatingpup_save.2fs in dev/fd0
dd:writing please wait-----

1424 + 0 records in
1423 + 0 records out



I have not created a swap partition yet, in an effort to
isolate this floppy problem.

When I remove the hard drive, no partition option
GUI appears, and I have to pull the plug.

I hope this helps.

Love sea monkey, by the way- and the clean shutdown
with hard drive attached.
Where you have "dev/fd0" is this just a typo?
it should be "/dev/fd0"

That 1424 records in, only 1423 records out ain's so good.
Seems that there isn't enough room for the chosen size of the file.
wilcal
Posts: 14
Joined: Thu 26 Jan 2006, 18:36
Location: San Diego, CA

#12 Post by wilcal »

BarryK wrote: Seems that there isn't enough room for the chosen size of the file.
Careful of floppys. Could be a bad spot. I always format a floppy a
couple three times making sure the whole thing formats properly
before using it. Also always format a floppy on the same drive you
are writting the data to it with.

Wilcal - 30+ Years in the removable data storage industry :x
"DISK BOOT FAILURE - INSERT SYSTEM DISK AND PRESS ENTER"
is my friend
User avatar
Puppy Dog
Posts: 58
Joined: Sat 21 May 2005, 13:53

#13 Post by Puppy Dog »

Sorry, my typo.

Creating pup_save.2fs in /dev/fd0 , please wait awile...
dd: writing '/tmp/savepup/pup_save.2fs' : No space left on device

1424 + 0 records in
1423 + 0 records out

then on reboot:

disktype: Can`t stat /dev/fd0: No such file or directory

It goes by quickly. I think this is closer.
------------------------------------------------


The good news is I had no problem creating a
pup_sav.3fs on /dev/hda1

279020 + in
279020 + out - and it works!

The 1.24g hard drive has only 8.00mb left.
No biggie, I will attempt to reduce the file
size.
I wasn`t sure if puppyalpha2 was going to
somehow repartition my hard drive- moving
away from the pupxxx system I like.
"Best In Show"
User avatar
Puppy Dog
Posts: 58
Joined: Sat 21 May 2005, 13:53

#14 Post by Puppy Dog »

Sorry, my typo.

Creating pup_save.2fs in /dev/fd0 , please wait awile...
dd: writing '/tmp/savepup/pup_save.2fs' : No space left on device

1424 + 0 records in
1423 + 0 records out

then on reboot:

disktype: Can`t stat /dev/fd0: No such file or directory

It goes by quickly. I think this is closer.
------------------------------------------------


The good news is I had no problem creating a
pup_sav.3fs on /dev/hda1

279020 + in
279020 + out - and it works!

The 1.24g hard drive has only 8.00mb left.
No biggie, I will attempt to reduce the file
size.
I wasn`t sure if puppyalpha2 was going to
somehow repartition my hard drive- moving
away from the pupxxx system I like.
"Best In Show"
Post Reply