Puppy Linux Discussion Forum

ETP · Joined: 19 Oct 2010 Posts: 310 Location: UK

I originally posted the following in the Slacko 5.4 thread back in Sept 2012 where it rather got buried. It seems more appropriate to post it here as it is still IMHO, as valid as ever.

--------------------------------------------------------------------------------------------------------
It is evident that this forum is littered with posts relating to boot issues with typically either:

1. The main SFS or save-file not being found or
2. The incorrect sfs or save-file being loaded.

These issues generally crop up when multiple pups are in use or more advanced boot techniques are being used where the component parts of puppy are being held on different drives, sub-directories and partitions.

I am aware that BK's philosophy, with which I totally agree, is that Puppy should in the main (with the possible exception of pmedia=) be capable of booting without other boot codes & be clever enough to work things out for itself.
In addition new users should not have to concern themselves with complex boot codes.

Currently the additional codes are intended by him to provide hints/help to Puppy when more complex arrangements are deployed.

This is fine for non-advanced use as probably 90% of users will have all the puppy files together in one directory.

The current problem with advanced use seems to be that the boot codes can sometimes conflict with or undermine the search logic that hunts down the location of firstly the save-file(s) and then the main sfs & any additional sfs files that the selected save-file calls for to be loaded. Often removing a boot code can help but more often than not one has to hit on the right combination of codes by a process of trial and error.

A couple of real world working examples:

CASE 1: Kernel on 16 MEG Smartmedia with main sfs & savefile on NTFS HDD (sda1)

otropogo · Posted: Tue 29 Jan 2013, 03:08 Post subject: Re: Revised/additional boot codes.

ETP · Joined: 19 Oct 2010 Posts: 310 Location: UK

Otropogo,

otropogo · Posted: Thu 31 Jan 2013, 01:47 Post subject: Re: Revised/additional boot codes.

knsridhar · Joined: 22 Mar 2011 Posts: 6

Sir
in your next puppy linux release please include drivers for all types printers and scanners new and old ones.this will make puppies complete replacement for MS windows and its software.I have been using pupplies for quit long time and it serves all my requirments.only problem i have is drivers for my pronters and scanners.hope it will be attended to in future release
knsridhar

jpeps · Joined: 31 May 2008 Posts: 2421

hal8000 · Joined: 05 Mar 2013 Posts: 6

This may not be possible due to the large size of the proprietary drivers but I'd like to see next puppy release include the catalyst (fglrx) driver for ATI cards and the Nouveau nvidia drivers.

If this is not possible would it be possible to include a boot parameter
e.g. puppy pfix=catalyst or pfix=nvidia with the ability to boot the driver
from a pupsave file.

R-S-H · Joined: 18 Feb 2013 Posts: 274

My wish list for the next Puppy is my wish list for the next Puppy is my wish list for the next Puppy is my wish list for the next Puppy is my wish ... ... ...

Laughing

bohocmasni · Joined: 01 Jun 2012 Posts: 13 Location: Hungary

a wish list?

i wish puppy could handle slax's modules, could install and uninstall that fast (did you try it?). or: could be more than 5 sfs loaded in the same time

or: ppm could remove lots of pets with 1 click.

or: i wish some developer tools/toys could be packed in base sfs, like tcc or bacon and not in the one big sfs with kernel sources