Puppy Linux Discussion Forum

Bruce B · Posted: Sat 28 Jul 2007, 13:44 Post subject:

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

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

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?

Joe_DK · Joined: 22 Jul 2007 Posts: 7

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

Sage · Joined: 04 Oct 2005 Posts: 4638 Location: GB

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?

RazzBear · Joined: 30 Jun 2006 Posts: 24

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

BarryK · Posted: Sat 28 Jul 2007, 18:22 Post subject:

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.

Greystar · Joined: 20 Mar 2007 Posts: 26

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

BarryK · Posted: Sun 29 Jul 2007, 10:58 Post subject:

Have made a few more improvements.

PaulBx1 · Joined: 16 Jun 2006 Posts: 2308 Location: Wyoming, USA

Sage · Joined: 04 Oct 2005 Posts: 4638 Location: GB

Clearly too much screwing going on in the USA!

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

Wyoming, Dick Cheney's home turf. Where men are men, and sheep are nervous.

nic2109

edoc · Posted: Tue 31 Jul 2007, 19:26 Post subject:

BarryK · Posted: Tue 31 Jul 2007, 22:26 Post subject:

Here's the latest, as used in 2.17.1rc.

Download somewhere, then open a terminal in that directory, then
type this (not the #):
# gunzip puppyinstaller-bk3.gz
# chmod 777 puppyinstaller-bk3
# ./puppyinstaller-bk3