Puppy Linux Discussion Forum

FYI
This leads us to a "Topic Area" (wiki? or google doc accessible by all users) for examples to use cases such that boot-time session finding is understood and minimized. This would go a long way for future users and developers of an IMPORTANT basic of PUPs.

Current documentation is not necessarily clear enough for good understanding as it intermingles file and folder operations. That documentation could stand for some restructuring making things more apparent.

I am willing to work with anyone on such to promote a clearer understanding with examples if anyone wants. PM me should you desire.
FYI

Finding the save, is something that has gone back and forth in Woof-CE coding, of the basic operations, of booting Puppy.
It seems to change, with the wind, on what the boot process, will do.

Several Puppy versions back.
The boot process would keep looking on any drive, any partition, until it found the save.
Then the idea changed to the save, should be in the same location, as the other Puppy files.
That would be the only place to look for them.
Then it went back to looking in more places.
Then the idea of putting Puppy on a USB stick, would be best if the save was only on, that USB stick.
So, using the stick on another computer. The USB stick would have the save, along with the Puppy, booting from it.

Then people started complaining about the time that it was taking to boot, because all drives, where being searched, for the save.
So, lets limit where to look for the save.

Another issue was, how far into the layers of directories, do you go looking.
2, 3, 4, 5, unlimited directories deep, and do this for each partition, searched on all drives.

Then it became what pupmode are you running in.
From a CD/DVD the save has to be on another drive, unless you are saving back on the CD/DVD.
So it needs to look on all drives.
Installed on a USB flash drive, usually the save is on the USB drive. Why look other places.
Installed on an internal drive. The save should be on that same drive. So why look on other drives.

Then you have the people that seem to want to put the save, anywhere but the drive, Puppy is installed on.
Again, the question of how long do you want the boot process, to slow down, looking for the save.

So over the years, finding the save, has changed.
Depending on the version of Puppy.
It is looking for the save, based on what was being done, at that time, in the boot process.

Only thing for sure.
If the save is in the same place as the other Puppy files. It should be found, with no problems.
That has always stayed, as the first place to automatically look.

Hello. I would like to say thank you to josejp2424 for putting this wonderful puppy together. I've been playing with Dpup Buster 64 XFCE version since January and this has become my favorite puppy. I think this is the best XFCE puppy so far. I guess puppy+debian+xfce has the greatest appeal for me. Is a new version coming perhaps with the latest XFCE release?

I haven't encountered booting issues like others perhaps because I normally do manual frugal install of my puppies. I just copy puppy_dpupbuster64_8.0.0.sfs, zdrv_dpupbuster64_8.0.0.sfs, vmlinuz and initrd.gz to a folder in my drive (say DPupBuster8) then add entries to grub.

Sample menu.lst entry for grub 2.

title DPupBuster 8.0
  find --set-root uuid () 642E78822E784ED4
  kernel /DPupBuster8/vmlinuz  pdrv=642E78822E784ED4  psubdir=/DPupBuster8 pmedia=atahd pfix=fsck,copy
  initrd /DPupBuster8/initrd.gz

Sample grub.cfg if you're using this.

menuentry "DPup_Buster"{
	set root='(hd0,1)'
	search --no-floppy --fs-uuid --set=root 642E78822E784ED4
	linux /DPupBuster8/vmlinuz root=UUID=642E78822E784ED4 psubdir=/DPupBuster8 pmedia=atahd pfix=copy,fsck
	initrd /DPupBuster8/initrd.gz
}

-ronriel

ronriel wrote: ↑Thu Apr 15, 2021 4:12 am

Sample grub.cfg if you're using this.

Code: Select all

menuentry "DPup_Buster"{
	set root='(hd0,1)'
	search --no-floppy --fs-uuid --set=root 642E78822E784ED4
	linux /DPupBuster8/vmlinuz root=UUID=642E78822E784ED4 psubdir=/DPupBuster8 pmedia=atahd pfix=copy,fsck
	initrd /DPupBuster8/initrd.gz
}

Just a little thing.
It looks as if you set root twice.
My guess is you can leave out the first line (or the second) under the menuentry line.

I've been using dpupbuster64-8.0.0 RC3 (jwm version) daily for awhile now. It has been
stable. I use the latest version of firefox (now at 88). A couple of apps were broken, and
I used PupClockset-2.7.pet and htop-2.0.2-x86_64.pet (easily found). abiword wasn't
installed but can be installed via PPM.

There is a very long delay (over a minute) before wireless starts to connect at startup.
I found that clicking on the htop desktop icon kills any delay. I haven't been able to
discover how to automate this workaround. Startup scripts don't do the trick.

It's unfortunate that this particular dpup version has never been fixed and raised to
release level. I really enjoy using this potential gem!

art

Just a quick note that DpupBullseye-9.7.0 beta was released a couple days ago. I've been using it the past couple days and it's quite nice.

Thanks for the info on bullseye, dasouth. It has the same old issues with htop and pupclockset.
The delay after startup before (sns) wireless connection process starts is far lower at about 20 seconds.
I could not find a word processor (such as abiword) installed. There are a few improvements and
a few things that are worse compared to 8.0.0 jwm.

art

@art
I'm in total agreement with some improvements and also some regressions with this build.
Anytime I have a new distro, I know I'm going to spend a bit of time setting it up so that it's usable for me.

Just to say thanks, josejp2424, for another really nice Puppy.
I haven't completed exploring. But AFAICT so far, it is able to run all the portables and AppImages that Fossapup64 can. Looking forward to your 'Bullseye' version preferably JWM-Rox. Hint, Hint.

Edit: Found your duveanpups, viewtopic.php?p=26799#p26799. Something new to learn.

Is this still alive?

I'm using the older RC1 64-bit version, nicely setup but I need an Abiword package for this that works, the stuff I downloaded doesn't. BTW - I've tried this CE version but have problems with it on my computer so I'm sticking with RC1 which runs well with an older kernel..

@amethyst. Abiword's a hard one. pkgs.org indicates it has about 30 dependencies. Ubuntu Bionic Beaver use Buster as it's base. But ibiblio>puppy doesn't have an Abiword pet in either pet packages bionic or common64.
Why Abiword? Aren't you better off running wine and using Atlantis --just a better wordprocessor.

On my hard-drive's folder for Bionicpup6's applications I have both WordGrinder, https://cowlark.com/wordgrinder/index.html and TED, https://en.wikipedia.org/wiki/Ted_(word_processor). Don't know why I have WordGrinder --someone must have published it and I downloaded without thinking: I don't do terminal apps. TED isn't bad if you need something simple. Under Bionic64, the 64-bit package from here, https://nllgg.nl/Ted/ seems to only be missing libtiff.so.4. Previously, I tracked it down to create the pet package (too large to attach). But all you'd need is the lib and symlink I've attached.

.
Extract and drop into /usr/lib.

mikeslr wrote: ↑Sun Jun 11, 2023 3:53 pm

@amethyst. Abiword's a hard one. pkgs.org indicates it has about 30 dependencies. Ubuntu Bionic Beaver use Buster as it's base. But ibiblio>puppy doesn't have an Abiword pet in either pet packages bionic or common64.
Why Abiword? Aren't you better off running wine and using Atlantis --just a better wordprocessor.

On my hard-drive's folder for Bionicpup6's applications I have both WordGrinder, https://cowlark.com/wordgrinder/index.html and TED, https://en.wikipedia.org/wiki/Ted_(word_processor). Don't know why I have WordGrinder --someone must have published it and I downloaded without thinking: I don't do terminal apps. TED isn't bad if you need something simple. Under Bionic64, the 64-bit package from here, https://nllgg.nl/Ted/ seems to only be missing libtiff.so.4. Previously, I tracked it down to create the pet package (too large to attach). But all you'd need is the lib and symlink I've attached.
lib.tar.gz.
Extract and drop into /usr/lib.

I don't have 64-bit Wine and not going to download that AND a 32-bit compatable package for 32-bit programs. Anyways, I've set up Fossa64-bit 9.5 now which has Abiword. I'm continuing to use Bionic 32 as my pimary driver and only really interested in 64-bit to run DMR content (which happens seldomly in my case). This is something that has always p*ssed me off about Linux, this bloody wild goose chase for dependencies and so on for certain packages and versions. Windows are miles ahead as far as convenience of software packages are concerned. Too many distributions and versions in Linux world, it's ridiculous actually.

Edit 2: ozsouth has just published an abiword-gnumeric combo for fossapup64-low but identified as 'slightly older versions'. May work under DpupBuster OOTB, or only need a couple of libs. Link from here, https://www.forum.puppylinux.com/viewto ... 280#p91280. But as I question Abiword's reliability, still suggest the following.

Edit: Ignore everything below the line. Use MikeWalsh's Textmaker portable. https://mega.nz/folder/LShHgaCC#QKEiIMMQDVlvQPdJ5IHcWw. It could be located in /opt if you want to run completely in RAM. Eventually, you would have to register. But it's a reputable company which doesn't share your email. Maybe about twice a year you'll receive a offer to upgrade to SoftmakerOffice at a discount; or to download a free font.
@ 155 Mbs, it's not all that much larger than abiword. Even if locate in /opt it won't have a significant impact on available RAM. And if locate outside the Save almost none. It's reputed to be the most microsoft-word-compatible. Best of all, it doesn't have abiwords reputation of screwing things up when you actually need a wordprocessor.

-=-=-=-=-=--
You didn't need 64-bit wine, nor loading a 32-bit compatibility SFS to run Atlantis. Use MikeWalsh's Wine-portable 5.11, https://www.forum.puppylinux.com/viewto ... 191#p68191. The AppImage it's built-around contains its own 32-bit libraries, and its script create both the wine-prefix and menu-entries. Of course, using it you can't run entirely in RAM.

If DpupBuster is a better Puppy with your system, while running fossapup64 you can use PPM to download abiword and ALL dependencies.

Thanks for the links, that Abiword works OOTB for DpupBuster. Some of those other sruff are eye-watering in size, wow. I think I'll stick with running Bionic 32 all the time and then just boot one of the 64-bits on those rare occasions I need to watch DMR stuff or when the need arises to use something like Tor browser . In all other scenarios, 32-bit is a much better option for my setup.