slacko-6.0 beta 2

[SFR]

* lzop -- should be the real one, not the BB one. The real one does not
zap the original file when archiving or unarchiving.

Can be achieved also with busybox's:

Code: Select all

lzop -c somefile > somefile.lzo
lzop -c -d somefile.lzo > somefile

Interesting list, btw. Personally, I'd be happy if wmctrl & xdotool got included one day. These two lil gems are irreplaceable with any other tool found in Puppy OOTB.

Tried to run pwidgets (.pet used) but found conky was missing libiw.so.29. OK once I copied this from another Pup so pwidgets is now running and I don't have to look out the window to check the weather.

In Slacko-5.7 this lib is a part of wireless_tools-29-slacko-i486 (slacko14.1-official), but Slacko-5.9.1 has wireless-tools-29 from slackware-14.1-official, where this lib is not present.
Yeah, my Conky also won't run without it and additionaly complains about missing libpcre.so.0, but in this case it was just a matter of creating a symlink (-> libpcre.so.0.0.1).

Greetings!

[musher0]

Hey, micko, it's your distro!

My, my, the tone! Hey, you do what you want. Those are not orders or
commands, not even "hypnotic" suggestions (as in "if you look at this
post long enough, you'll do like I want!") -- just plain opinions!

I'm not a passer-by trying to tell the miller and his son what to do
with their donkey!

In any case, the full lzop and blkid can be added "manually" or from
ad hoc pets. I -- for one -- have met with resistance long enough about
certain useful add-ons in the Puppy world that I've sort of built automatic
work-arounds. So you can add or not add this or that utility to your distro,
it does not really matter anymore. It's just that all users are not as handy
as I am with a Puppy, and certainly a request for really useful abiword
plug-ins is not frivolous.

I agree with SFR concerning wmctrl and xdotool. They take very little
space and you (pardon, this is not personal -- "one") can do wonders
with them managing the desktop.

And speaking of SFR, I believe his PackIt and UExtract are so useful that
they should be mandatory on all new Puppies. (BTW, this one IS an
"hypnotic suggestion"...)

Have fun!

musher0

[musher0]

@SFR

About your lzop script:
Frankly, I don't see the point of removing features from a utility so it can
fit in busybox, and then sometime later having to compensate what was
removed through wrapper- or shell- scripts... I'd find it more logical to
keep the initial full-featured utility -- unharmed.

Somebody should definitely create the
"Society for the Prevention of Cruelty to Utilities (SPCU)".
(Everybody saw the smileys, yes?)

My 2¢. BFN.

musher0

[01micko]

My, my, the tone! Hey, you do what you want. Those are not orders or
commands, not even "hypnotic" suggestions (as in "if you look at this
post long enough, you'll do like I want!") -- just plain opinions!

My tone is non-existent because ... I have about 5 terminals, 8 browser tabs, 22 text tabs, 6 filer windows open.. and lots of bugs to fix! ... no offence intended. I do appreciate the feedback.. and I rather think in terms of 'our' not 'my'. Please do test the new Abiword upload if you can, I think we can afford a couple of more plugins if needed.

EDIT: often text does not convey 'tone' very well at all, especially across cultures.. re: my silly comment " chmod 666 /dev/urandom #and again, one more time for the dummies " in rc.sysnit. I removed it because it could be read as 'offensive', though it was intended for me because I had it fixed, but not committed and it got lost in the rather large noise that is woof (the woof program that is)

[shinobar]

What is the reason for the stop; sleep; start in /root/Startup?. Does it need to be refreshed when X starts?

EDIT: If the reason for this is important, be aware that at first pupmode=5 boot that this will not be invoked until after the "first run" routine called form /usr/sbin/delayedrun.

Yes. It is the point.
The acpid starts without X when invoked by the /etc/init.d/rc.acpi via rc.sysinit. It is for the Puppy failed to start X. And it is restarted with X by the Startup or autostart.

Here is a trick to judge the power button emergency or normal.
We can assume the power button without X emergency. The user can type poweroff or reboot command on the console in normal condition.
When start X, we can assume the emergency power button before the quicksetup is finished.

For the latter, I coded based on the fact the switching acpid without to with X occurs after the quicksetup is finished. It is tricky. We are better to use a flag indicatig the quicksetup status, because the autostart sequence may be changed in future.

[01micko]

Beta is out

See main post

[James C]

Beta is out

See main post

Downloading.......

Hopefully this kernel will like my AMD boxes....

[James C]

Beta is out

See main post

Downloading.......

Hopefully this kernel will like my AMD boxes....

It does.

Fresh manual frugal install of 5.9.2. Other than needing to use SNS for internet connection all looking good so far.

Code: Select all

# report-video
VIDEO REPORT: Slacko Puppy, version 5.9.2

Chip description:
VGA compatible controller: nVidia Corporation C68 [GeForce 7050 PV / nForce 630a] (rev a2)

Requested by /etc/X11/xorg.conf:
  Resolution (widthxheight, in pixels): 1024x768x16
  Depth (bits, or planes):              24
  Modules requested to be loaded:       dbe 

Probing Xorg startup log file (/var/log/Xorg.0.log):
  Driver loaded (and currently in use): nouveau
  Loaded modules: dbe dri2 exa extmod fb glx kbd mouse shadowfb

Actual rendering on monitor:
  Resolution:  1440x900 pixels (380x238 millimeters)
  Depth:       24 planes

...the above also recorded in /tmp/report-video
# 

Code: Select all

# glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
4402 frames in 5.0 seconds = 880.331 FPS
4473 frames in 5.0 seconds = 894.510 FPS
4512 frames in 5.0 seconds = 902.252 FPS
4459 frames in 5.0 seconds = 891.708 FPS
4467 frames in 5.0 seconds = 893.269 FPS

Code: Select all

-Computer-
Processor		: 2x AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Memory		: 3111MB (199MB used)
Machine Type		: Physical machine
Operating System		: Slacko Puppy - 5.9.2
User Name		: root (root)
Date/Time		: Sun 22 Jun 2014 07:24:26 AM CDT
-Display-
Resolution		: 1440x900 pixels
OpenGL Renderer		: Gallium 0.4 on NV67
X11 Vendor		: The X.Org Foundation
-Audio Devices-
Audio Adapter		: HDA-Intel - HDA NVidia

More testing......

[01micko]

Beta is out

See main post

Downloading.......

Hopefully this kernel will like my AMD boxes....

It does. [snip]

More testing......

Where is the :phew: smiley?

[James C]

[SFR]

Ah, mhwaveedit's icon does not show in JWM menu.
Attached .pet with corrected .desktop file (it was only a missing Icon=mhwaveedit.xpm extension).

Greetings!

[James C]

.

[SFR]

Broken icon in PUI, due to lack of /usr/local/lib/X11/mini-icons/gparted.xpm.

Greetings!

[shinobar]

Beta is out

Thanks for taking Ctrl+Alt+DEL and power button staff.

Slacko-5.9.2
1. Frugal installed on a ext4 partition.
2. Saved the session (directory).
3. Reboot PC,. OK with the pupsave(directory).
4. Registered kernel_sources-3.4.93-slacko32FD4G.sfs by the boot manager.
5. Reboot PC. Got panic.

Occurs with any sfs.
Loading sfs-on-the-fly is ok. But gets panic at next boot.

[SFR]

During testing my recent changes to installpkg.sh (savefile vs. tmpfs) I noticed, that everything and always gets saved only into tmpfs!
Naturally, thinking that it's something wrong with my code, I used old installpkg.sh and configure.sh, but it made no difference...
After 20 min of scratching my head, while staring at the code, I finally realized that it's because aufs is not compiled as an external module anymore.
And installpkg.sh is checking for it:

Code: Select all

if [ "`lsmod | grep '^aufs' `" != "" ];then

(there's similar mechanism in snapmerge, btw)

So, what we're gonna do? I see 2 scenarios:
1. If there's a way to detect if aufs is built into vmlinuz (dunno how) it would be a matter to add an additional test for it.
2. Don't check for aufs at all (and additionaly remove all stuff related to unionfs, if we're sure the latter won't be used in the future).

Anyway, the question is how many other apps need it?
Scripts from woof-CE:

Code: Select all

# find -type f -exec grep -Hi 'lsmod.*aufs' {} \;
./rootfs-skeleton/bin/initrd_layer_test:[ "`lsmod | grep '^aufs'`" != "" ] && LAYERFS="aufs"
./rootfs-skeleton/usr/local/petget/installpkg.sh:    if [ "`lsmod | grep '^aufs' `" != "" ];then
./rootfs-skeleton/usr/local/petget/installpkg.sh: if [ "`lsmod | grep '^aufs' `" != "" ];then #100426
./rootfs-skeleton/usr/sbin/snapmergepuppy:if [ "`lsmod | grep "^aufs" `" != "" ]; then
# 

Greetings!

[mavrothal]

I finally realized that it's because aufs is not compiled as an external module anymore.
....

So, what we're gonna do? I see 2 scenarios:
1. If there's a way to detect if aufs is built into vmlinuz (dunno how) it would be a matter to add an additional test for it.
2. Don't check for aufs at all (and additionaly remove all stuff related to unionfs, if we're sure the latter won't be used in the future).

Good catch!

Code: Select all

zgrep 'AUFS_FS=y' /proc/config.gz

should do it but for some reason /proc/config.gz is not there
/etc/modules/modules.builtin is another place to check but not as safe as /proc/config.gz.
Though option 2 might be better. Is a long time that puppy stopped using unionfs

[zigbert]

Something has happened to gtk since the alpha



This mis how it looks in the 591

[SFR]

I finally realized that it's because aufs is not compiled as an external module anymore.
....

So, what we're gonna do? I see 2 scenarios:
1. If there's a way to detect if aufs is built into vmlinuz (dunno how) it would be a matter to add an additional test for it.
2. Don't check for aufs at all (and additionaly remove all stuff related to unionfs, if we're sure the latter won't be used in the future).

Good catch!

Code: Select all

zgrep 'AUFS_FS=y' /proc/config.gz

should do it but for some reason /proc/config.gz is not there
/etc/modules/modules.builtin is another place to check but not as safe as /proc/config.gz.
Though option 2 might be better. Is a long time that puppy stopped using unionfs

Yes, I also noticed that /proc/config.gz is not present in k.3.4.x, but it is in 3.10.x.

Yeah, I would vote for 2 either, or eventually:
3. Check for unionfs and if not present, always assume aufs:
lsmod | grep '^unionfs' && unionfs || aufs
but I don't see a point TBH...

Greetings!

[jamesbond]

So, what we're gonna do? I see 2 scenarios:
1. If there's a way to detect if aufs is built into vmlinuz (dunno how) it would be a matter to add an additional test for it.
2. Don't check for aufs at all (and additionaly remove all stuff related to unionfs, if we're sure the latter won't be used in the future).

Let's opt for 1). The check is already done by initrd, this check should not be duplicated in every programs. To cater for full install, perhaps rc.sysinit could check too (because initrd isn't used in full install, innit?) and save the result, say, in PUPSTATE? In woof-next's initrd, aufs is assumed by default, except when overriden by "layerfs=unionfs" on kernel command line. So if you want to have a check, let's do that check (grep -q layerfs /proc/cmdline). You can of course go with /proc/config.gz test, but this assumes that CONFIG_IKCONFIG_PROC is set. Actually, on the second though, for stuff apps like these, what is their business detecting the layerfs system? They should only worry whether they're running on full install, ram layer, or direct savefile, shouldn't they? Then they should look at PUPMODE alone.

[peebee]

5. Reboot PC. Got panic.

Occurs with any sfs.
Loading sfs-on-the-fly is ok. But gets panic at next boot.

I also get kernel panic on reboot if I install any sfs - tried quite a few different ones.

This is a manual frugal install to a subdirectory with the sfs's in the subdirectory. The panic occurs with both the old savefile and the new savedirectory after reboot.

Error messages are the same as SFR's screenie below.

Also, think the removal of broadcom b43 wireless firmware (and others?) is a really retrograde step as it removes one of puppy's great strengths of wifi support OOTB - does the saving of a a few mb's in the iso size really matter these days????

Cheers
peebee