Iguleder: You can easily make ".sfs" files for the Trinity KDE stuff used in the latest Porteus-v1.1rc1-i486.iso as follows: Download the latest Porteus-v1.1rc1-i486.iso from: http://porteus.org/distro-download/download-latest-32-bit.html in the "testing/Porteus-v1.1-rc1" directo...

The permission level for BarryK's replacement for "pup_event_backend_modprobe", extracted from his "pup_event_backend_modprobe.gz" file, is not set "executable". If you change the permission level to "executable", most of the previous problems should hopefully...

@Pri

The version of "tar" in the Puppy Linux that you are using to run Woof needs to be updated to one that recognizes the "-j" parameter ( xz compression ).

If you do this then Woof should run successfully.


Grndoor

The following url has lots of info regarding Flash Drive Endurance:

http://www.storagesearch.com/ssdmyths-endurance.html

ttuuxxx:

The following Slackware file contains a full codec pack with the divx stuff:

http://repository.slacky.eu/slackware-1 ... h-1sal.tgz

boscobearbank: In the "Screen" section of your xorg.conf file: Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 Subsection "Display" Depth 24 Modes "1680x1050_60.00" "1280x1024" &qu...

### Missing Reiserfs support files Puppy has the Reiserfs file system drivers compiled into the kernel. However, the following Reiserfs support files are missing from all the Puppy-400 test isos: /sbin/debugreiserfs /sbin/fsck.reiserfs /sbin/mkfs.reiserfs /sbin/mkreiserfs /sbin/reiserfstune /sbin/re...

Please see the recent item in Barry's Blog: "XFS, CIFS filesystem drivers missing" which discusses whether various Filesystem kernel drivers should be added back into Puppy. If you look inside the Puppy 217 xdrv_217.sfs file you will see that it included drivers for a very large set of fil...

Within the "puppy-2.17.1-nolzma-seamonkey-fulldrivers" iso the "zdrv_217.sfs" archive should have been "gzip" compressed as per the "nolzma" in the title of the iso. In fact the zdrv file has been "lzma" compressed, which as a consequence causes all ...

I am using 2.16 and 2.17 full hd installs. I have tested "hardinfo" from the two "pet" packages and also compiled it locally from the latest svn version. "Devices --> Storage" works fine on three different PCs, including a Compaq Proliant 1600 which is an all SCSI hard ...

I have a Laptop with an internal CD drive which is faulty. I therefore boot the Puppy Live CD from an external USB Drive which shows up on /dev/sr0. With the Puppy 2.16/2.16.1 Live CD I have to use the "pmedia=usb" or "pmedia=usbcd" boot parameter to force a boot from the externa...

I have a Laptop with an internal CD drive which is faulty. I therefore boot the Puppy Live CD from an external USB Drive which shows up on /dev/sr0. With the Puppy 2.16/2.16.1 Live CD I have to use the "pmedia=usb" or "pmedia=usbcd" boot parameter to force a boot from the externa...

The "jre_004.sfs" module ( dated 20 Apr 2007 ) is currently inaccessible. The "devx_004.sfs" module ( dated 27 Mar 2007 ) appears to be "faulty". 1) The command: "mount -o loop -t squashfs devx_004.sfs tmp_directory" fails with the message: "mount: Mounti...

Thank you for making the "devx_004.sfs" module accessible. I have a Hard Disk installation of the latest Grafpup iso. How do I mount and extract the contents of the "devx" module so that it can be copied to the HD installation. Barry's "devx_xxx.sfs" modules can be moun...

The latest Grafpup "devx" Module, located at http://grafpup.org/modules/devx_004.sfs, is currently inaccessible.

An attempt to download the module fails with a "403 Forbidden" response.

Please look at the Pupget problem described and possibly fixed in the earlier post:

http://www.murga.org/%7Epuppy/viewtopic.php?t=12694

Please look at the Pupget problem described and possibly fixed in the earlier post:

http://www.murga.org/%7Epuppy/viewtopic.php?t=12694

PrairieDog:

I can confirm your experience with the "pupget package installer" in the latest 212 beta2.

Simply removing the extraneous trailing "$" in "${APKGNAME}$" on line 695 of the "pupget" script fixes the problem.

The drives are already meant to be remounted "rw" through the action of line 71 of "rc.sysinit": 71 echo -n "Remounting '/' read-write... ";mount -o remount,rw /;STATUS=`expr $STATUS + $?` However, the effect of line 62 of "rc.sysinit" is to prevent this remou...