ScPup & ScPup64 - Slackware Current based Woof-CE pups

[OscarTalks]

Minor thing, the download link buttons for 32bit kernel-sources and kernel-headers don't work. Looks like they have just "pup" instead of "lxpup" in the name. I was still able to navigate and find them.

[peebee]

buttons for 32bit kernel-sources and kernel-headers don't work.

Many thanks - fixed.

[mash]

mash, I believe busybox fdisk only uses MB, GB whereas gnu fdisk does use MiB and GiB. In the initrd.gz we only have busbox fdisk available.

See screenshot.

Ah, I see. Didn't know the output is different.

This init works for me too. Either with gyro's or with original lxpup kernel.

Yes, the original kernel already had the drivers for your mmc hardware builtin, whereas it did not for 01mico's Dell.
I think you had the problem because the 'init' script was aware of your mmc device.

Indeed. If I remove

Code: Select all

fdisk -l $DEVICE | grep -qm1 "using GPT" && return # bale out if GPT

line I get kernel panic back.

Latest ScPup64 and Woof-CE Slacko64 build boot without problems. Thanks.

[gyro]

I've uploaded 'huge-5.4.46-gyro-64.tar.bz2' to http://www.mediafire.com/folder/21fyvbi4xglau/kernels, for ScPup64.

I've uploaded 'huge-4.14.184-gyro-pae.tar.bz2' to http://www.mediafire.com/folder/21fyvbi4xglau/kernels, for ScPup.

These 2 kernels are now sort of obseleted by "ScPup...20.06", the new release kernels already contain enhanced mmc storage support.
Although they might still be relevant to "ScPup ...20.01" users.

I'll probably delete them in the near future.

gyro

[Wiz57]

peebee, following your tip to rename savefile works, for the most part...
regular ScPup 32 and ScPup 32 with LXDE updated without issues...
even renaming the ydrv for LXDE worked well. However, LXQt would
not load as ydrv nor as a regular SFS...have went back to 20.01 + 6T
for use with LXQt, also using an older LXQt (0.14). Thanks for all the
work you do keeping these Slackware based Puppies current! Much
appreciated!
Wiz

[peebee]

However, LXQt would not load as ydrv

Hi @Wiz57

Have you downloaded the new ydrv?:
https://sourceforge.net/projects/spup/f ... s/download

also - try in a pristine frugal install before using with an existing savearea.

[gyro]

@peebee,

I downloaded 'devx_ScPup32_20.06.sfs' and tried to compile kernel v5.4.46 in 'ScPup32_20.06', using the latest Woof-CE 'kernel-kit'.
It failed trying to compile the DOTconfig editing utility.
Seems there is no '/usr/include/linux' directory in 'devx_ScPup32_20.06.sfs'.

I had to go back to ScPup to do it.

gyro

[gyro]

@peebee,

Same problem with 'devx_ScPup64_20.06.sfs'.

gyro

[peebee]

Hi @gyro

kernel_sources and kernel_headers are separate .sfs for my kernels and are not in the devx.....

for /usr/include/linux you need to install the kernel-headers
e.g. for 32-bit bottom of:
http://distro.ibiblio.org/puppylinux/pu ... -20.06.htm

Cheers
peebee

[gyro]

kernel_sources and kernel_headers are separate .sfs for my kernels and are not in the devx.....

for /usr/include/linux you need to install the kernel-headers

Yes, that worked, thanks.

gyro

[didit]

is there any way to make a full install ? somehow it offers frugal only

[ozsouth]

@didit - the install names are largely misnomers. Frugal is the standard install & saving with the save folder option has almost identical function to the old-style full install. Modern pups are not designed for that old style.

[didit]

@didit - the install names are largely misnomers. Frugal is the standard install & saving with the save folder option has almost identical function to the old-style full install. Modern pups are not designed for that old style.

but as i understand frugal system will consume more RAM than full

[foxpup]

but as i understand frugal system will consume more RAM than full

Puppy is not big, so mostly it doesn't matter.
Also Puppy will try to accomodate and not load (main) sfs if RAM is too small.

However, if you have little RAM, you can add pfix=nocopy to the kernel/linux line.
(edit the config of your bootloader
you know how you boot and where to find the config of your bootloader? don't you?)
Then Puppy will not copy to RAM, like full install.

You use a swap (file or partition)?
That may help if your RAM is to small for just a moment, to prevent freezing.
You should not need it continuously, just for the critical moments.

I think 'layered install' would be a better name for frugal install.
(that answers to your question how to do a full installl:
you could open up all the layers and drop it all together )

[mikeslr]

@ didit,

As to why we recommend Frugal Installs see this post, http://murga-linux.com/puppy/viewtopic. ... 89#1023489

Mentioned in that post is that only with Frugal installs can you use SFSes. SFSes are loaded when you want them, unloaded when you don't. An unloaded SFS uses no RAM.
Any Application you can install can be built instead as an SFS. Usually easily. Install PaDS, http://murga-linux.com/puppy/viewtopic. ... 922#998922. Then, rather than use Puppy Package Manager to Auto install an application and its dependencies, change the setting (at the Top-Right) to "Download all (packages and dependencies)". Place the downloaded files in a uniquely named folder. Right-Click the folder and Select Combine to SFS.

A more complex example is given here, http://www.murga-linux.com/puppy/viewto ... 36#1024636

You'll find some excellent Remaster tools on the Forum, such as that in nic007's Utilities. http://www.murga-linux.com/puppy/viewto ... 10#1053410. I think it now includes an application for creating a pet package from a builtin application. If not, gnewpet will, http://murga-linux.com/puppy/viewtopic. ... 673#598673. What you can do is create pets of those builtin applications you rarely use. Then use Menu>Setup>Remove Builtins and Remaster your Puppy. [A remaster is necessary to actually remove them]. Use PaDS to create SFSes or SFS-Suites of those 'removed' applications you actually want.

But all of the above is merely 'icing on the cake'. As other have posted: a Frugal Puppy actually uses little RAM; and less if you use the 'no-copy' boot argument.