Puppy Linux Discussion Forum

[zygo]

Using grep -E -o. GNU's grep 2.5.4 (in Q130) will not match 'literal.* literal' near the end of a single line bigger than about 150kB. GNU's grep 2.5.3 (copied from P431 & tested in Q130) and the one in BusyBox v1.16.2 (in Q130) will match. However, a more efficient way to search is with {1,99} in place of * which works in all 3 versions of grep.

[linuxcbon]

Why still using oss since alsa replaced it ?

[zygo]

I know that /dev/sda is an unknown device but why the 19 seconds delay?

[Béèm]

[PANZERKOPF]

[zygo]

I can't remaster Q130. I applied these 2 bug fixes:

Bug 1: the remaster script terminates with "your Puppy is too old"
my (apparent) fix is to edit /usr/sbin/remasterpup2 line 236
change $DISTRO_SPECS to $DISTRO_IDSTRING

Bug 2: DaveS (after BK) describes the need to append the $DISTRO_IDSTRING value to the puppy.sfs http://www.murga-linux.com/puppy/viewtopic.php?t=60720

I don't change the new root or .etc when offered but I do allow console customisations and edit:
- isolinux.cfg to add a pfix=ram boot option
- boot.msg to add indicate it's remastered and
- puppy.sfs as in Bug 2.

Attempt 1
At the badly drafted "make zdrv.sfs inside?" dialogue I click "no" (thinking it starts outside so why change it). Before the dialogue offering to change /tmp/root there's an orange window which starts with an error and then a progress bar which completes. I let the remaster script make the cd-rw when it offers. The new cd boots but stops saying it can't find puppy.sfs. Game over.

Attempt 2
At the "make zdrv.sfs inside?" dialogue I click "yes". The error in the orange window is something like "cannot stat exclude puppy.sfs ignoring... parallel mksquashfs". I let the remaster script make the iso when it offers and use the iso burning utility to make the new cd. This cd boots much further but will not start X. Very hard to see what's wrong but maybe the intel graphics driver is missing. This runs so smoothly at first boot but not a dodo now. Where is this in the original iso? It may be just a matter of adding it to the sfs before burning.

Edit: added "exclude" to "cannot stat" error.

[zygo]

Attempt 3

As attempt 1 but when it offers you chance to alter /tmp/root and /tmp/etc
- delete everything within
- copy everything from the live version
- delete .XLOADED

Success.

Note I got these extra 3 steps from the forum and used them on Puppy 431 maybe earlier.

Barry, you do ask in one of the dialogues to tell you if something is not copied that should be. The answer seems to be to copy all but the console customization files and .XLOADED

[fluxit]

I was under the impression that "puppy pfix=ram" should leave no non-swap partitions mounted when the desktop appears. Twice in a row today, I have booted with pfix=ram only to find that "sda1," my ntfs partition is mounted as /initrd/mnt/dev_ro2 and cannot be unmounted as it is "in use."
Puppy was not using my pupsave as far as I could tell.

I normally run from the CD with no boot options, and my pupsave on sda1.

Another issue that has come up(it was not doing this initially) is that JWM will no longer "Exit to prompt," "Reboot computer," or "Power-off computer" without Ctrl-Alt-Backspace to help it along.

I have changed many of JWM's configuration options and have fallen afoul of the "JWM configuration" empty file bug(which then went away on its own,) but it seems to be working properly otherwise currently.

One of the options I changed was to sliding-focus, which I didn't really want, but it keeps me from having to double click on the taskbar to get it to do things that it should do with one click like switching virtual-desktops or minimize/maximize. It took me a while to figure out that I was double-clicking and not merely falling victim to a failing mouse button(my mouse is fine.)

[tlchost]

[PANZERKOPF]

Fragment of code (alternate_driver_func)