Dpup Stretch 7.5 CE (RC-5)

[foxpup]

to foxpup, yes my pendrive only installed grub4dos. in legacy mode, nothing happened. The laptop juz boot into windoze.. I tried with antix installed on another 16gb pendrive. Nothing happened too.

Yes indeed the k4.1.48 iso is for older hardware. But the same dpup stretch setup booted successfully on Dell pc with latest i7 processor.

The kernel is probably not the problem.

If I understand correctly, you can boot the same dPupStretch pendrive on the Dell uefi machine but not on the uefi Zenbook.
This pendrive only has grub4dos (legacy boot).
Something must still be wrong in your BIOS or Windows to allow legacy boot.
Look for hibernation, sleep, fast startup, secure boot (should be off), CSM, legacy boot, usb boot (should be enabled).
There is no standard as to what you will find in the BIOS and what is supported.
Also, you may find some things in windows AND in the BIOS, separately; that may be the case for fast boot.
Also check the boot order in BIOS. Legacy should be first and usb as well if detected (should be detected).

Wish to use the same os with my custom setting accross all pc. Is there a boot method or grub setting that can boot for both new and old hardware?

Not that I know of.
If you put an Puppy iso with uefi in the name on a pendrive with the command dd, it will boot both Legacy and EFI. Try it.
But this will block the rest of the pendrive to be used, unless you can fix the usb.
There is often a script fix-usb.sh in the iso, but it is not always working well.
Also there is just 1 Puppy on your pendrive, you may want several.

---

But it is easy to prepare your pendrive for both Legacy and EFI and frugal installs (in folders).
HOWTO coming up later.

EDIT (later):
I suppose you know how to put Puppys each in their own folder.
I suppose you also know how to run grub4dos to have it installed on the pendrive.
I suggest, before doing this, you use Gparted and make a smaller fat32 (50-100M) and an ext3/4 partition.
Put flag boot (and esp - probably not needed) on the fat32. This is for the boot installations.
Ext3/4 is for the Puppys.
The rest is to use freely.

So put the Puppys each in their own folder on ext3/4.
Then run grub4dos to install grub4dos on the pendrive. Mind the options!
Grub4dos will install on flagged fat32.

Now the boot installation for efi.
Puppy Linux UEFI boot EASY and http://helledussen.com/linux/files/UEFI_boot/ from Limbomusic have a good explanation.
On fat32 "make a folder called "EFI" and a "boot" folder inside that. (EFI/boot) and then just put" bootx64.efi "inside it.
Make a file called "grub.cfg" in the root of the flashdrive [=flagged fat32 partition] with this text:

Code: Select all

menuentry "Start whateverYOuwant" {

linux /vmlinuz

initrd /initrd.gz

}

[/i] "
Because Limbomusic put just 1 Puppy on the only partition of his pendrive,
but we put several Puppys in their own folder,
the grub.cfg should be a little different.
Example:

Code: Select all

set timeout=10

menuentry "Puppy stretch 7.5" {
  search --file --set root --no-floppy /dpupStretch/initrd.gz
  linux /dpupStretch/vmlinuz    psubdir=/dpupStretch pmedia=usbflash pfix=fsck
  initrd /dpupStretch/initrd.gz
}

menuentry "Puppy bionicpup64 8.0" {
  search --file --set root --no-floppy /bionicpup64/initrd.gz
  linux /bionicpup64/vmlinuz    psubdir=/bionicpup64 pmedia=usbflash pfix=fsck
  initrd /bionicpup64/initrd.gz
}
menuentry "Puppy slacko64 6.3.2" { 
  search --file --set root --no-floppy /slacko64-6.3.2/initrd.gz
  linux /slacko64-6.3.2/vmlinuz    psubdir=/slacko64-6.3.2 pmedia=usbflash pfix=fsck
  initrd /slacko64-6.3.2/initrd.gz
}
menuentry "Puppy wary 5.5" {
  search --file --set root --no-floppy /wary/initrd.gz
  linux /wary/vmlinuz    psubdir=/wary pmedia=usbflash pfix=fsck
  initrd /wary/initrd.gz
}

menuentry "EFI Firmware configuration interface (BIOS)" {
	fwsetup
}

menuentry "Shutdown" {
	halt
}

Notice this is very similar to menu.lst generated by grub4dos:

Code: Select all

# menu.lst produced by grub4dosconfig-v1.9.4
#color blue/cyan yellow/blue white/black cyan/black
splashimage=/splash.xpm
timeout 10
default 0

# Frugal installed Puppy

title Puppy stretch 7.5 (sdb2/dpupStretch)
  find --set-root --ignore-floppies --ignore-cd /dpupStretch/initrd.gz
  kernel /dpupStretch/vmlinuz    psubdir=/dpupStretch pmedia=usbflash pfix=fsck
  initrd /dpupStretch/initrd.gz

title Puppy bionicpup64 8.0 (sdb2/bionicpup64)
  find --set-root --ignore-floppies --ignore-cd /bionicpup64/initrd.gz
  kernel /bionicpup64/vmlinuz    psubdir=/bionicpup64 pmedia=usbflash pfix=fsck
  initrd /bionicpup64/initrd.gz

title Puppy slacko64 6.3.2 (sdb2/slacko64-6.3.2)
  find --set-root --ignore-floppies --ignore-cd /slacko64-6.3.2/initrd.gz
  kernel /slacko64-6.3.2/vmlinuz    psubdir=/slacko64-6.3.2 pmedia=usbflash pfix=fsck
  initrd /slacko64-6.3.2/initrd.gz

title Puppy wary 5.5 (sdb2/wary)
  find --set-root --ignore-floppies --ignore-cd /wary/initrd.gz
  kernel /wary/vmlinuz    psubdir=/wary pmedia=usbflash pfix=fsck
  initrd /wary/initrd.gz
...
..
.

The entry Wary will not work in EFI because Wary is too old.
It is not capable of booting into EFI.

[WiZard]

Hi radky,
Running rc5 on my laptop. I prefer to turn the touchpad off otherwise I am always hitting it while typing or navigating. I use control center>hardware>touchpad = off then save and quit. This works until I restart and the touchpad is back on. I checked the /.flSynclient file and the TouchpadOff parameter does change to =1 when the setting is made and is still =1 after a restart, but the touchpad is reactivated.

I checked this in rc3 and rc4 and get the same results. Checking in Slacko 6.3 and LXxenial 7.5 it works correctly.

Please let me know if there is a solution.

thanks

wiz

[radky]

I prefer to turn the touchpad off otherwise I am always hitting it while typing or navigating.

@WiZard,

Recent Pups rely increasingly on eudev for mangement of the keyboard, mouse and touchpad -- and our Woof-CE devs are currently adjusting the implementation of eudev in Puppy.

For now, maybe MochiMoppel's suggestion below would automatically disable the touchpad when your system boots. Name the script, make it executable and place in /root/Startup.

Code: Select all

#!/bin/sh
synclient TouchpadOff=1

http://murga-linux.com/puppy/viewtopic. ... 32#1002132

[WiZard]

@radky

Thanks for the explanation and solution.

wiz

[WiZard]

hi radky,

I converted from rc4 to rc5 the first part of August. I copied the rc5 files into a directory and then copied my rc4 save file into the directory. On the first run it did a save file conversion and everything seems to be working well. I have found that pupsnap now thinks that the keyboard up arrow key is its hot key. Is there a file that can be edited to change that setting?

thanks

wiz

[radky]

hi radky,

I converted from rc4 to rc5 the first part of August. I copied the rc5 files into a directory and then copied my rc4 save file into the directory. On the first run it did a save file conversion and everything seems to be working well. I have found that pupsnap now thinks that the keyboard up arrow key is its hot key. Is there a file that can be edited to change that setting?

thanks

wiz

@WiZard,

Please see:

http://murga-linux.com/puppy/viewtopic. ... 86#1031986
http://murga-linux.com/puppy/viewtopic. ... 11#1032011

---

As true for the current releases of BionicPup(32/64), keyboard and mouse interactions for the 4.19.56 release of Dpup Stretch are managed by evdev rather than conventional drivers (kbd_drv.so and mouse_drv.so).

In some scenarios, it seems the evdev keybindings for certain keyboards may have mapping issues for the PrtScr, Up and End keys -- at least in the openbox desktop environment.

In the upcoming RC-6 release of Dupup Stretch, management of keyboard and mouse interactions will revert to conventional drivers, but a small script and GUI will be provided for those who prefer input management by evdev.

For now, please try the following if you see mismapping of the PrtScr, Up or End keys in FbBox (openbox and fbpanel):

1 - Go to FbPanel configuration -> Plugins tab -> Key Bindings -> select 'true' -> click Apply
2 - Restart X to automatically reset keybindings for the PrtScr, Up and End keys

[WiZard]

@radky

fbpanel was the fix, I had searched in the pupsnap topic and didn't find anything. Should have done a better search to find it right here in the Dpup topic. Will do better in the future.

thanks for your help and patience

wiz

[tallboy]

Hi radky.
I have tried to make a multisession CD-R with the RC-5 version with k4.1.48, and it's latest update of cdrecord. I first made a a few small changes to the default setup to see if it would save the session back to the CD-R, and that worked. I booted the modified CD-R, and it loaded the saved dir as it should. I then made several modifications and additions, saved the session to the CD-R at shutdown and booted again. Bummer!
There is something seriously wrong with woof-CE, because the saved sessions were loaded, I had a screen, but with my old PuppyPin - not the new, I had mouse but no keyboard. I opened a virtual keyboard and an urxvt, and tried to find a solution.
I opened the Mouse/keyboard wizard, and tried to modify my keyboard settting there. I got a message: 'Your xorg.conf file does not contain any XkbModel options.' So I thought I could make an addition to xorg.conf. Hahahaha. You have changed the possibility to make a personal xorg.conf. What the h...? The xorg.conf settings are now automated. I opened the latest savefile on the CD-R, and started to check all my other modifications. I used the same settings as in my RC-4. Some were there, many were gone. There was a new dir made in /, 'include'. Not by me, but by the system. My 22.000 line /etc/hosts was not saved, but the default one was back, even if I deleted it before saving my own.
The whole Puppy's internals are being turned around, there seem to be a mix of old and new. Have anybody tried to remaster the latest version? I think you are in for a surprise.
I admit that the very idea to save to a multisession CD-R, will disappear in a near future. One reason is that the latest Puppys are way to big to load into a RAM-starving old PC, and the old PCs may not be able to use a late model browser with the smaller, old Puppys. But I still have old PCs that won't eat anything that isn't served on a disc, and Stretch is no solution for them. If I cannot remaster a late Puppy to make it smaller, and run it from a CD, those machines go into the garbage, and I dislike that thought very much.
I have seen that BarryK has made an interesting derivative named EasyOS Pyro, which is compiled from source to keep it small, and includes a lot of my favorite programmes. But even that small build is 418Mb, which is a tad to large for an old PC with 500Mb RAM, and his latest Buster EasyOS build is more than 500Mb in size. But they can probably be remastered to a smaller size, if the late kernel is OK for old hardware. I'll play with them a little.

Question: Can the swap partition be loaded earlier in the boot process, and maybe help a large Puppy work on a RAM-starved Linuxbox?

One small issue I noted with RC-5. If you enable the screensaver in Menu->Desktop->pupX set properties of X, it is not enabled i Menu-> Desktop->ScreenSaver Control, but has to be enabled manually there too.

[radky]

I have tried to make a mult-isession CD-R with the RC-5 version with k4.1.48, and it's latest update of cdrecord...Bummer!

@tallboy,

In recent Pups, saving the desktop to multi-session optical media is a function of Woof-CE code implemented in December 2016, with additional minor revisions after that date. If I understand correctly, future revisions are considered low priority by our Woof-CE devs since optical drives are becoming increasingly obsolete in most modern PCs.

For old PC hardware, perhaps legacy Pups (released before December 2016) may provide your requested support for multi-session optical media.

[tallboy]

radky, there is an update after the last time I mentioned in RC-4, that I could not save back to a multisession CD-R. That was actually noted as a bug by someone, and a new version of cdrtools is available in woof-CE. I have downloaded the cdrtools-3.02a09-i686_common32.pet. I thought it was included in the latest RC-5, but cdrtools may have been updated after your release date of RC-5.

As mentioned earlier, I also suspect the new policy regarding hostname followed by a number, may make some difficulties concerning the /etc/hosts file, and maybe other files, not being saved back to the CD.

[OscarTalks]

The executable /usr/bin/xxd is required for compiling NetSurf browser.
In DpupStretch 7.5 CE (RC-5) this file is a symlink to busybox, but this fails during the build because of an unrecognised option.

In earlier distros, xxd was part of the vim-common package, but this is now separated out as a package just named xxd

I suggest replacing the busybox symlink with this package. It could probably go in the devx but perhaps in the main .iso since it is small?

[radky]

The executable /usr/bin/xxd is required for compiling NetSurf browser.
In DpupStretch 7.5 CE (RC-5) this file is a symlink to busybox, but this fails during the build because of an unrecognised option.

In earlier distros, xxd was part of the vim-common package, but this is now separated out as a package just named xxd

I suggest replacing the busybox symlink with this package. It could probably go in the devx but perhaps in the main .iso since it is small?

@OscarTalks,

For the next release of DpupStretch, I will add the xxd binary to the main Puppy sfs.

Thanks

[lizardidi]

I am still on Dpup stretch 7.5 CE (RC-4), the bcrypt preinstalled is not working. When try to encrypt file, it says "Encryption is disabled". Is the bcrypt broken?
Further reading on Debian's bug report stated that bcrypt is not safe to use as the algorithm can be predicted.
I posted here because I had not found any bcrypt related changes in the RC5 change log.

[mikeslr]

Hi lizardidi,

With bcrypt neither working nor safe, you might want to use veracrypt as an alternative. The pet I built is available here, https://www.mediafire.com/folder/7m55ivwku6fb5/. You'll want the pet named veracrypt32_1.23.

I particularly like veracrypt as, if I choose, I can create one folder for files I want to protect rather than having to encrypt each file.

Caution: I haven't used it under dpup-stretch to store files. But it does open and appears to be functional. Test it a couple of times before relying on it.

[radky]

I am still on Dpup stretch 7.5 CE (RC-4), the bcrypt preinstalled is not working. When try to encrypt file, it says "Encryption is disabled". Is the bcrypt broken?
Further reading on Debian's bug report stated that bcrypt is not safe to use as the algorithm can be predicted.
I posted here because I had not found any bcrypt related changes in the RC5 change log.

@lizardidi,

Because of security concerns, the Debian devs have disabled the encryption algorithm in the current bcrypt package (1.1-8.1+b1), but the capacity to decrypt existing archives is still intact.

Perhaps it would be best to completely remove bcrypt and bcrypt_gui from Dpup Stretch, but for now they are included for decryption of existing archives.

Thanks for your question.

---

@mikeslr,

Thanks for your recommendation of veracrypt as an alternate encryption utility.

[lizardidi]

@mikeslr
Thanks for the recommendation, I downloaded the .sfs made by you, and currently in the process of learning to use the new tool. Please recommend me other newbie-friendly encryption tools if got any. I found the Pcrypt very easy to use too.

***edit: I tested the 32 bit veracrypt.sfs in dpup-stretch, the .sfs missed the "dmsetup" dependency. dmsetup is needed in order to decrypt the container.



@radky
Looking forward for your Dpup Stretch Ultimate version!

[Max Headroom]

G'day Radky, Thanx 4 this Stretchpup which works so far on an MSi U100 Wind NetBook w/ a N270 1.6 GHz Atom CPU which is Ltd to 2 GB RAMemory. I'm wanting 2 add zram-config, But can't find it in the PPM Repos, or is there a pet which I've Searched for but can't find. Any suggestions Mate?

;-)K

[mikeslr]

***edit: I tested the 32 bit veracrypt.sfs in dpup-stretch, the .sfs missed the "dmsetup" dependency. dmsetup is needed in order to decrypt the container.

Hi lizardidi. Just stumbled on your post. Oddly, even with veracrypt neither installed nor loaded, my systems show /sbin/dmsetup. Wonder where they came from?

Will have to boot into dpup-stretch and rebuild veracrypt under it.

Of course, if you really want to keep prying eyes from reading sensitive information, not being able to decrypt them is the way to go.

Well, if you really insist on decrypting them, try the new version I've uploaded. https://www.mediafire.com/folder/7m55ivwku6fb5/

[rufwoof]

***edit: I tested the 32 bit veracrypt.sfs in dpup-stretch, the .sfs missed the "dmsetup" dependency. dmsetup is needed in order to decrypt the container.

Hi lizardidi. Just stumbled on your post. Oddly, even with veracrypt neither installed nor loaded, my systems show /sbin/dmsetup. Wonder where they came from?

Isn't dmsetup a lower level command/program

man 8 dmsetup ... indicates

Referenced By
blkdeactivate(8), cmtab(5), cryptsetup(8), fsfreeze(8), lvm(8), lvmchange(8), multipath(8), multipath.conf(5), vgmknodes(8)

[radky]

G'day Radky, Thanx 4 this Stretchpup which works so far on an MSi U100 Wind NetBook w/ a N270 1.6 GHz Atom CPU which is Ltd to 2 GB RAMemory. I'm wanting 2 add zram-config, But can't find it in the PPM Repos, or is there a pet which I've Searched for but can't find. Any suggestions Mate?

@Max Headroom,

It seems there are no zram tools in the official packages of Debian Stretch.

However, on the Puppy forum, wiak offers an interesting discussion about zram and zswap, and Puppus Dogfellow provides packages for testing this concept in Puppy.

Please see the following link to download those packages shared by Puppus Dogfellow on Google Drive.

http://www.murga-linux.com/puppy/viewto ... 078#987078

I hope this helps.