(old)Puppy Linux Discussion Forum

# uname -a
Linux e732 3.10.19 #1 SMP Wed Nov 13 16:52:29 EST 2013 i686 Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz GenuineIntel GNU/Linux
# free
total used free shared buffers
Mem: 1804484 986392 818092 0 61288
-/+ buffers: 925104 879380
Swap: 0 0 0
# uptime
16:31:02 up 2:08, load average: 0.21, 0.30, 0.25
#

So far all looking very good. No unexpected surprises - seems to work OOTB as expected.
Nice. Very best regards - Ray

Hi Mick

Downloaded the 5.6.1 iso, devx and kernel sources - boy it took a lonnnnnngggg time from your website (at 8am UK time) .... so much so I had to leave my pc running while I went to work today.

Did all my usual tests - compiled wl.ko and installed the Broadcom STA driver for my wifi - installed the LxPup-by-SFS and Compiz sfs's and switched to Compiz - loaded Chromium-30 sfs

All working great and as expected - no problems at all to report - posting from Compiz / Chromium as we "speak"

Cheers
peebee

I mentioned (elsewhere) about drive icons not getting refreshed after partitioning (in 5.6). Much better in 5.6.1 - after creating a new partition, icons are being refreshed, but after deletion it's necessary to remount another partition, in order to trigger this. Can live with that.
___________

Old, but recently discovered by me, annoying bug in /bin/df, line 8 (missing quotes around $@): ___________

Perhaps it's too early for that, but there are few, less obvious apps, that are worth upgrading IMHO:
- unrar - supports the latest rar5 format
- ms-sys - supports Vista/7 MBR
- exploderpm (part of src2pkg) - supports newer RPMs
___________

Maybe too early as well, but I keep forgetting about this since 5.4, so let it be written for future reference.
Minor enhancement. Since Xarchive supports 7z archives (7za wrapper) and Slacko has 7z, so what about:

/usr/local/bin/pupzip, line 147/8: (or maybe shorter & safer) + let 7za wrapper to see 7z: + MIME-type for ROX: + optionally: ___________

Anyway, 5.6.1 looks really solid (playing in VBox for now).

Thanks &
Greetings!

peebee, mirrored here:

http://archive.org/details/Puppy_Linux_Slacko

SFR wrote: Old, but recently discovered by me, annoying bug in /bin/df, line 8 (missing quotes around $@):

Code: Select all

RETSTUFF="`$DF "$@"`"

Fixed. See PM about exploderpm and other stuff.

Slacko 5.6.1

Using Firefox browser installed in Slacko 5.6.1.
Tried to download an image file and got this screen for selecting location to save to. Notice blank screen. Seemed to go blank at random times, trying to navigate to a location in file system.

Not a bug bigpup, you are running firefox as Spot. It will only be able to open /root/spot (spots home) and any sub-directory. If you don't wan to be spot, quit firefox, open menu>system>Login and Security Manager, uncheck firefox and click Ok.

Alas ways PPM :

Hit button just download the dependencies (5) and the package (imagemagick) ..

NOTHING happens :

01micko,

I was wondering if Spot was the problem, but was not sure.
Now you know why I never use spot.

Test results:
Spot operation mode seems to be working in Firefox

Computer just gave me the coffee warning.

Slacko 5.6.1

PPM (initial default setup)

Repositories showing in PPM are 5. OK.
Max number able to list at one time 5.
In configure PPM
6 repositories are selected initially, by default.
The Puppy-noarch offical repository is not showing.
This one should be seen by a new user for no other reason then this.

While looking at PPM as a new user of Puppy and Linux for that matter.
I feel there would be less confusion for a new user, if PPM initial default setup, would have

package types

defaulted to:

any type.

Let them change it to other options, when they understand what those options are.

As it is now, default is GUI apps only.

Do you even understand all of these options?

Hi, Mick.

Bad news here... V. 5.6.1 has the first save bug. The size determination
dialogue is skipped, and we end up with a negative value of -1 Mb for
the pupsave file. (Please see attached illustration.)

It may be tempting to blame the problem on my 10-year old machine,
but it has 2 Gb's of RAM and 1.128 Tb of mass storage attached to it,
so it still has plenty of power. Moreover, this machine does not have
save-file (or equivalent) problems with other types of Puppies, nor
on other distros that accept save files for frugal mode (e.g. Debian
Squeeze).

I did peruse the shutdown code, but I won't touch it. Some people are
better and more experienced at editing it than I am. Especially code
by BK.

That said, here are a couple of ideas.
1) If the set_pupsize function (not exact name) could default the
SIZEPFILE (exact name) variable at 16 or 32 Mb's when there is an error
at first save in this frugal mode (is it mode 12 or 13?), it would prevent
frustrations. The user could fatten the pupsave file easily at 2nd or 3rd
boot.

2) If the "DO NOT SAVE" button halted the script, the user would be
able to save his/her configurations to another medium, again
preventing frustrations, and saving time.

Best of luck with your new version, but this tester is out for the above
reason. However, I did provide sufficient test information (I think) about
this problem in a thread that I created yesterday, so if you or anyone
wants to draw on my experience of this bug, you know where to look:
http://murga-linux.com/puppy/viewtopic. ... ost#739203.

BFN.

musher0

Just wanted to report that I ran Slacko 5.6.1 off and on all day with no real problems. Installed some pets,did some visual tweaks and made Firefox run as root....... really nothing bad to report.Used both the Athlon XP and the P4 installs.... a bit slower on the Athlon XP box but no real difficulties.

Switched over to Sid a bit ago........

Works fine in my AMD E-350 laptop. X usually consumes 10% of cpu power and firefox 15% with just the forum active - these are higher than usual (The white load line is generally visible. Anyway, don't pay attention to it, am just a spoiled puppy user ). I thought that this should be normal with a new kernel.

As to musher0's negative pupsave file, I haven't encountered it yet in any recent puppy.

Hello, people.

I did manage to get a pupsave. Please see how at http://murga-linux.com/puppy/viewtopic. ... ost#739203

However, upon reboot, I got the gdk bug, as in Precise 5.7.1 "non-retro".
Shucks.

BFN.

I too can not recreate the negative size of savefile (nor PPM hang) yet...
@Musher0: you could launch shutdownconfig from terminal - maybe some errors will show up..?

raffy wrote:Works fine in my AMD E-350 laptop. X usually consumes 10% of cpu power[...]

I'm getting the same on AMD C60 netbook. But after installing fglrx (when will be available) this should drop ~3-5%.

@Mick: Slacko has (in devx) strings, but named as "strings-GNU" - shouldn't it be just "strings" (like in Precise's or Dpup's devx)?

Greetings!

SFR wrote:I too can not recreate the negative size of savefile (nor PPM hang) yet...
@Musher0: you could launch shutdownconfig from terminal - maybe some errors will show up..?

raffy wrote:Works fine in my AMD E-350 laptop. X usually consumes 10% of cpu power[...]

I'm getting the same on AMD C60 netbook. But after installing fglrx (when will be available) this should drop ~3-5%.

@Mick: Slacko has (in devx) strings, but named as "strings-GNU" - shouldn't it be just "strings" (like in Precise's or Dpup's devx)?

Greetings!

Musher, what SFR says might shed some light (run wmpoweroff in terminal with original shutdown script), it may be a 'mount' error or something silly. This was the case with the ntfs bug which I fixed about a year ago but it was a bit more than just running in the terminal, however yours should get that far since it's still in GUI when you see the bug.

SFR, already have a work around. I actually had an argument about this with Barry, then he changed busy box strings to be used, but then for some reason changed it back! Slackware has strings in util-linux package but other distros (all of them according to Barry - see the template for util-linux in woof) have it in bin-utils. Now I am just renaming strings-GNU (part of slackware bin-utils). See how that works.

Hello, all.

@SFR and 01micko:

Success using shutdownconfig directly, as a standalone program.
The size dialog showed correctly.

That seemed to do something to the rc.shutdown script in /etc, since
it ran correctly, in full, and I got another valid pupsave file on
the "official" reboot run.

@SFR:
I ran shutdownconfig from console with < set -xe > added at the top
of the script, and the run displayed no errors.

So partial success, again.

When I got back in, on second boot with this new pupsave file, though,
the gdk bug was staring me in the face! But let's handle only one insect
at a time, shall we?!...

BFN.

musher0

Hope it is okay with my noob question.
How do I know which version is best for my computer

slacko-5.6-4G-NON-PAE.iso or slacko-5.6-PAE.iso

I have a Desktop HP/Compaq AMD Athlon X2 Dual Core
rather old computer CPU now. ?
3GB RAM Doing frugal install on the NTFS HD

The Graphics are nVidia G98 (GE Force 9300 )

musher0 wrote:Hello, all.

@SFR and 01micko:

Success using shutdownconfig directly, as a standalone program.
The size dialog showed correctly.

That seemed to do something to the rc.shutdown script in /etc, since
it ran correctly, in full, and I got another valid pupsave file on
the "official" reboot run.

@SFR:
I ran shutdownconfig from console with < set -xe > added at the top
of the script, and the run displayed no errors.

So partial success, again.

When I got back in, on second boot with this new pupsave file, though,
the gdk bug was staring me in the face! But let's handle only one insect
at a time, shall we?!...

BFN.

musher0

Now its me also about to complain about rc.shutdown !!!

Save-file was created correctly to vfat in size of 128 MB with ext3 .
Then I went wmexit to prompt and reboot then failed to copy /initrd/pup_rw into the save-file .
/dev/sdb1 1018084 845548 172536 84% /mnt/sdb1

Today's boot failed with kernel panic about smp, shed and hrtimer .

e2fsck -v /mnt/sdb1/WoofCEtest/slackosave-2013_11_23.3fs
e2fsck 1.42.6 (21-Sep-2012)
/mnt/sdb1/WoofCEtest/slackosave-2013_11_23.3fs: recovering journal
/mnt/sdb1/WoofCEtest/slackosave-2013_11_23.3fs: clean, 11/32768 files, 9804/131072 blocks

/dev/loop1 126931 5663 121268 5% /mnt/+mnt+sdb1+WoofCEtest+slackosave-2013_11_23.3fs

Only empty lost+found in that