(old)Puppy Linux Discussion Forum

Yes Barry, I'd say there is a problem as you described.

# probepart
/dev/hda1|ext2|78124032
/dev/hda2|ext2|58589054
/dev/hda3|ext2|58589054
/dev/hda4|none|2
/dev/hda5|ext2|58588992
/dev/hda6|ext3|58588992
/dev/hda7|ext2|174803202
/dev/hda8|swap|1108422
/dev/hdc1|ext2|156296322
/dev/hdc2|ext2|156280320
/dev/sda1|vfat|3893910
/dev/sr0|iso9660|0
/dev/hdb|iso9660|0

# mount
/dev/root on /initrd type ext2 (rw)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
tmpfs on /initrd/pup_rw type tmpfs (rw)
unionfs on / type aufs (rw,xino=/initrd/pup_rw/.aufs.xino,diropq=w,dirs=/initrd/pup_rw=rw:/initrd/pup_ro2=ro)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
none on /proc/bus/usb type usbfs (rw)

Puppy booted with puppy pfix=nox,ram argument, then xwin run to setup the GUI

The universal installer doesn't give an option to install on /dev/hda1

RazzBear wrote:Sorry about the big picture in my previous post

I have grub intalled on linux partitions (not on MBR)
and using windows bootloader on /dev/hda1 to bring up a boot selection menu

Forgive my bluntness, but why apologize and then leave the big picture?

I choose MBR to install grub .

I posted picture first then apologised in my next post
after seeing how big it was

"Sorry about the big picture in my previous post "

Maybe i could have resized or cropped just the relevant part,
is what the apology is for

Grup in MBR. Did a Grup reinstal in MBR - no difference.
So somewhere in the update of the 1500+ lines puppyinstaller-script is a secret hiding. Could be around the 'find' command or ext2/3 where something is altered.

There is a method of resetting these fora so that they display, even in 640x480. Apparently our two moderators haven't learned about this trick. Line overflow is really irksome. I'm sure that the board or php have some advice somewhere on how to do it? Moderators should always defer to the L.C.D. to allow for young folks with old kit, old folks with poor eyesight and poor folks who can't afford 100" lcd monitors with outrageous resolutions.

I can add, to my posts before, that if I install grub to the superblock of the partition, which makes the partition disappear in universal installer.
Then a re-install of grub to mbr, won't make it appear again. only a delete and create of partition and then install to mbr, will work.
Well, thats on my system!

Can anyone confirm this?

Guest07:
Have you installed grub to superblock of the missing partition at any time?

Jorgen.

I'll post another puppyinstaller script to test very soon.

There is a lot of clever code in there connected with GRUB detection, and maybe that has got something to do with it. I'm not familiar enough with it to locate the problem, especially since I can't reproduce the bug and I'm forced to just work through the code theoretically.

Anyway, will post something very soon.

Well, this is not ready to be used, but could you guys just start it up and tell me if it shows all your partitions? Attached.

SUCCESS - thanks Barry !
Now its there again. Did an upgrade of the full install on hda2 - writing from there. javascript:emoticon(':roll:')

RazzBear wrote:I posted picture first then apologised in my next post
after seeing how big it was

"Sorry about the big picture in my previous post "

Maybe i could have resized or cropped just the relevant part,
is what the apology is for

I get it. You thought it was too late to remove, crop or resize after it was posted. It wasn't and probably still isn't.

Barry, puppyinstaller-bk1.gz worked for me also. It now shows /dev/hda1, wereas the default installer didn't.

All existing disks/partitions are seen here.

I just tried 2.17, nolzma version downloaded from a mirror other than ibiblio, with a good md5sum starting with 2d0. Installing to a 1.6GB hard disk, cabled as secondary master.

If the disk has a single existing vfat partition, formatted vfat but with nothing on it, then Puppy Universal Installer (PUI) will put a frugal install on it, automatically.

If the disk has no partitions (i.e. I just used GPartEd to erase the vfat partition, but didn't then put a new partition on), then PUI does not offer any install. This is potentially confusing to a new user, since it still offers (only) the superfloppy install, and I can foresee woe down that path. You have to fdisk the disk first, using GPartEd, whose default setting is ext2. Ext3 and reiserfs are also offered.

If you at this point go away from PUI and call up GPartEd from the menu, and tell GPartEd to fdisk the particular disk partition to ext2, ext3, or reiserfs, then PUI installs to it just fine. You can choose either a frugal (co-exist) install or a full install. There is a danger to new users here, since the desired disk is not automatically selected by GPartEd.

It might be wise if GPartEd is automatically started, after an initial advisement prompt, and if the option is somehow advised of or prompted for, before GPartEd is started, which disk to install to. Also, it would be nice if PUI offers to put a 256MB swap partition on the disk if none already exists on the system.

Since I have a pre-exising GRUB install, I told PUI to quit when it offered to install GRUB; I then modified my existing GRUB config file (menu.lst) to boot from the newly-created install.

Works just fine, no matter whether the underlying partition is ext2, ext3, or reiserfs.

Upon first boot to the new disk-install, the heavy-encrypted pup_save file I created works just fine (however, I have recently seen it stated on the Gentoo forum that aes is now trivially easy to break).

Auto-version-update did not find any of the other pup_saves I have on other hard disks in this system (for earlier Puppy versions), which is good.

I notice the 2.17 bootup script is creating a Linux swap file, regardless of the fact I never told it to.

After creating the hard disk full install using PUI from the live CD, the CD (well, in my case, DVD actually) would not eject using the DVD-writer's front panel eject button. Had to choose Menu-Shutdown-Reboot and then push the DVD-writer's eject button in between Puppy shutdown and the initial BIOS splash screen of the next boot, in order to get the DVD to eject so as to boot from hard disk. I guess this means that it is not possible to play a DVD or access a data CD from the initial live-CD boot of 2.17.

The "Do you want to encrypt the pup_save.2fs file?" question talks about "to void the overhead." That should be "to avoid the overhead." Grammatical neatness counts.

BTW, when I GPartEd'd this disk, I forgot to format it after I fdisk'ed it. All three times with the three filesystems ext2, ext3 and reiserfs. Didn't matter, Puppy installed and ran just fine. I presume, then, that GPartEd automatically formats the partition if I forget to?

Seems you have solved it, I can see all partitions now!
Jorgen.

That CD retention matter can be a nuisance. Klaus introduced the auto-tray-open-before-shutdown-with-message right at the beginning of liveCD s. Has a touch of class about it! Several distros have adopted it. Not sure what the overheads are, though?

puppyinstaller-bk1.gz worked for me
It recognised the partitions and i did a full HD install to /dev/hda3
using grub on partition only

Well, I haven't really solved it. puppyinstaller-bk1 is the version from Puppy 2.14 with some small improvements only. Dougal used that version and made considerable improvements, particularly with handling of GRUB and his version is in 2.16 and 2.17.

Now I will carefully look at importing some of Dougal's improvements into our working script. I'll just do some basic enhancing that is not likely to break anything, then release 2.17.1-prerelease soon.

Can confirm also your test installer worked on mine as well.

Have made a few more improvements.

Klaus introduced the auto-tray-open-before-shutdown-with-message right at the beginning of liveCD s. Has a touch of class about it!

Between the way Puppy does it, and Knoppix, I prefer Puppy. Otherwise you are always having to screw around with the CD drawer every time you boot. But I have a BIOS password enabled, which allows me to open the drawer any time I need to before proceeding with entry of the password. So I have to screw around with a password on every boot instead. One could put in a single-letter password (if that is allowed) which wouldn't be that much screwing around...

Guess this is getting pretty far afield.