slacko-5.6 Final - plus testing next

A home for all kinds of Puppy related projects
Message
Author
gcmartin

#421 Post by gcmartin »

nooby wrote:... How do I know which version is best for my computer? ...
Either will produce a very stable operation on your PC. Either will work without fail. System operation for the user is the same as well as the application selection offered.

The ONLY difference, per se, is that PAE can be used, on just about every PC since 1995, but also no matter how much RAM you have from 384MB to as much as you can add to your PC all the way to 64GB. Non-PAE is limited by its inability to take advantage of any RAM beyond 3GB.

Again, either will work on your current system.

Here to help

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#422 Post by musher0 »

Karl Godt wrote:
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 :twisted: :mrgreen:
I was finally the first at something ! :twisted:

KG said:
>Then I went wmexit to prompt and reboot then failed to copy
/initrd/pup_rw into the save-file.


Ah! But the shutdown script is supposed to bounce us out of the bar! show
us the door! kick us out! :) Not allow us to go out in our own good time!
Nah-nah-nah, once you're done, you have maybe 30 seconds left to kiss
the girlfriend good-bye, and that only in GUI mode; then out, out, out
you go!

You shouldn't have had the time to type wmexit and reboot. You weren't
supposed to. Maybe a conflict of powerful commands corrupted your save
file. Typing wmexit and reboot probably interfered while normal creation
of pupsave. My 2¢.

BFN.

musher0
Last edited by musher0 on Sun 24 Nov 2013, 19:13, edited 2 times in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
SFR
Posts: 1800
Joined: Wed 26 Oct 2011, 21:52

#423 Post by SFR »

PPLOG, or actually hiawatha issue - server cannot be stopped in a normal way.

Code: Select all

# hiawatha.run start
Starting webserver: Warning: can't write PID file /usr/var/run/hiawatha.pid.
Hiawatha
#
# hiawatha.run stop
Hiawatha is not running
#
# ps | grep hiawatha | grep -v grep
 9249 webuser    0:00 /usr/sbin/hiawatha
#
'hiawatha' binary seems to be hardcoded to use (non-existant) /usr/var/run/ to store its PID in, whereas 'hiawatha.run' script tries to read from /var/run/.

Code: Select all

# grep -m1 'PIDFILE' /usr/sbin/hiawatha.run 
PIDFILE="/var/run/hiawatha.pid"
It seems to affect only Slacko since 5.5; latest Precise and Raring-3.9.8.1 are fine (PID stored in /var/run/) and transplanting 'hiawatha' bin from there into Slacko fixes that indeed.

Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#424 Post by nooby »

Thanks 01 micko seems to work on my machine too.
Did a frugal install on NTFS HDD made save file.
rebooted and here I am using slacko.

Now I need to find out how to handly that Lupu
put .mozilla on HDD and a lot of other things on hdd too.

This Firefox is 17.0-1 and refuses to go up to FF 25 and beyond :)
.cache if I remember.

Thanks to gcmartin for encouragement
I gave it a chance.and it did work.
Last edited by nooby on Sun 24 Nov 2013, 22:01, edited 2 times in total.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#425 Post by Karl Godt »

Ah! But the shutdown script is supposed to bounce us out of the bar! show
us the door! kick us out! Smile Not allow us to go out in our own good time!
Nah-nah-nah, once you're done, you have maybe 30 seconds left to kiss
the girlfriend good-bye, and that only in GUI mode; then out, out, out
you go!

You shouldn't have had the time to type wmexit and reboot. You weren't
supposed to. Maybe a conflict of powerful commands corrupted your save
file. Typing wmexit and reboot probably interfered while normal creation
of pupsave. My 2¢.
Nope, ran shutdownconfig from urxvt terminal, then wmexit .

shutdownconfig just cre-ates the save-file .

shutdownconfig gets usually called by wmreboot or wmpoweroff .

That way you would not have time to do anything, except pup_event_frontend_d is stubborn and refuses to be killed . In such case I would have had one minute for opening a urxvt console terminal to type
# whoami
Spock
:lol:
«Give me GUI or Death» -- I give you [[Xx]term[inal]] [[Cc]on[s][ole]] .
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#426 Post by musher0 »

Hello, all.

Karl_Godt wrote:
> Nope, ran shutdownconfig from urxvt terminal, then wmexit.
There's an idea. We make a little wrapper, and that's it, problem solved.
No more anti-matter pupsaves. But we wait long enough between the two
so no error occurs.

Or we provide a ready-made zipped pupsave of say 4 Mb's that unfolds/
unpacks at beginning or end of session automatically. At the same time
we copy a pre-fab'd pupsaveresize.txt file to wherever /mnt/home/ is,
this txt file containing a reasonable number, e.g. 380000. So the user
gets in total 384 Mb's as a "starter" pupsave. We warn the user not to
install any pets at this time, we only do configurations on first run.

The latter solution would be like treating diabetes: uncurable, but
controllable. We don't know the cause of the problem, but we solve
it nevertheless.

On the other thread, Karl brought up a possibility that I do not like:
that the rc.shutdown script could be language sensitive. I have to check it
out: does the script run correctly if I specify my language onlyon second
boot, if it is not fed in the configuration during the first session? Maybe
enlist the help of our Hungarian, Argentinian, etc., colleagues to verify
this also.

Also, try the most common: boot from CD proper, then save the
session to disk as a poor-man's (frugal) install. I'm booting now from
hard disk through the grub4dos menu.lst.

Finally, how do we check the possibility that the /etc/rc.shutdown
script is allergic to an e-sata disk.

Is that enough tests for you? :P My thoughts for now.

bye.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#427 Post by bigpup »

Slacko5.6.1 frugal install to HDD.

I had no problem making a save file.
Can not produce the problem.

Doesn't that make it easier to figure out a solution. :lol:

Sure you have a good download of the Slacko iso?
Clean frugal install?
Not installed to a fragmented ntfs formatted partition?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#428 Post by James C »

For what it's worth,no problems creating savefiles here either......on ext3 or ext4 partitions.

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#429 Post by musher0 »

@Jamed C and bigpup:

Thanks for your reports. May I ask additional clarification questions?

I understand that you exited your first session normally and successfully.
Were you using the GUI or the CLI interface?

Do you have "regular" hardware? Did you ask your pupsave file to be
created on an external disk or such?

Do you operate your Puppy system in English or in some other language?
__ If in some other language, did you specify the locale at all during your
first session?

How big is your save-file? Did you modify more than the essential
configs during this first session? I mean: did you also install some
programs?

I don't mean to intrude. Answer only if you like. Hopefully, your answers
to the above questions will help pin-point the bug.

Many thanks in advance. BFN.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#430 Post by James C »

musher0 wrote:@Jamed C and bigpup:

Thanks for your reports. May I ask additional clarification questions?

I understand that you exited your first session normally and successfully.
Were you using the GUI or the CLI interface?

Do you have "regular" hardware? Did you ask your pupsave file to be
created on an external disk or such?

Do you operate your Puppy system in English or in some other language?
__ If in some other language, did you specify the locale at all during your
first session?

How big is your save-file? Did you modify more than the essential
configs during this first session? I mean: did you also install some
programs?

I don't mean to intrude. Answer only if you like. Hopefully, your answers
to the above questions will help pin-point the bug.

Many thanks in advance. BFN.

musher0
Let's see.....

Used GUI

Internal hdd ....ext3 and ext4 partitions

English

Minimum size 512 mb..... sometimes larger.Sometimes I only do the necessary configurations before making the savefile,sometimes I'll go ahead and install my usual pets before making the savefile...no rhyme or reason.No problems either way.

HTH.

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#431 Post by musher0 »

Thanks, James C.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
SFR
Posts: 1800
Joined: Wed 26 Oct 2011, 21:52

#432 Post by SFR »

musher0 wrote:May I ask additional clarification questions?
In all cases initiated via GUI, nothing additional installed, not encrypted:
1. 512MB slackosave-test.3fs on internal HDD (sda2, NTFS), EN locale, PL keyboard.
2. 128MB slackosave-test.3fs on SD Card (sdb1, VFAT), PL locale/keyboard.
3. IIRC a couple of 256-512 2/3fs savefiles in VBox, mixed EN/PL locale/keyboard.
PL uses , (comma) as a decimal separator - that might cause problems in some cases, but not in this one.

HTH
___________

Lack of menu entries after installing some specific .pet packages

This is not new issue, but I have found the power to take a closer look at it at last.
While installing a .pet, 'installpkg.sh' alters "Categories=" line in .desktop files according to apps defined in /usr/local/petget/categories.dat.
Unfortunately in some cases (examples) new entry won't show up in menu (CATEGORY: None).

I think I found the source of the problem. Let's take milkytracker - 'Categories=' line in its .desktop file is changed to 'Categories=X-Multimedia-Sub', but both /etc/xdg/menus/hierarchy and /etc/xdg/menus/puppy-multimedia.menu contain only "X-Multimedia" (without '-Sub' bit) category.
Adding there this '-Sub' and running fixmenus makes the menu entry visible.

I've found two working solutions:

1. Only one file to be altered - to remove all 'Sub' bits in categories.dat, e.g.:

Code: Select all

PKGCAT_Multimedia_Sub=" abraca acidrip arista avidemux-gtk ...
PKGCAT_Fun_Sub=" angrydd barrage bastet billard-gl blockout2 ...
to be just

Code: Select all

PKGCAT_Multimedia=" abraca acidrip arista avidemux-gtk ...
PKGCAT_Fun=" angrydd barrage bastet billard-gl blockout2 ...
2. More files to be altered - to add those 'Sub' bits to appropriate records in hierarchy and all puppy-*.menu files (or safer, as an additional entries), e.g.:
a) hierarchy

Code: Select all

Multimedia :Sub            X-Multimedia,Recorder                               #
to be

Code: Select all

Multimedia :Sub            X-Multimedia,X-Multimedia-Sub,Recorder                               #
b) puppy-multimedia.menu

Code: Select all

  <Menu>
    <Name>Multimedia-Sub</Name>
    <Directory>Puppy-Multimedia-Sub.directory</Directory>
    <Include>
      <Category>X-Multimedia</Category>
      <Category>Recorder</Category>
    </Include>
  </Menu>
to be

Code: Select all

  <Menu>
    <Name>Multimedia-Sub</Name>
    <Directory>Puppy-Multimedia-Sub.directory</Directory>
    <Include>
      <Category>X-Multimedia</Category>
      <Category>X-Multimedia-Sub</Category>
      <Category>Recorder</Category>
    </Include>
  </Menu>
Both approaches seem to work just fine (briefly tested with a couple of apps), but of course it's up to you which one is better (if any :wink: ).

EDIT: attached altered hierarchy and puppy-*.menu files.
EDIT2: fixed typo in puppy-personal.menu. Re-uploaded after 1 download. Sorry...

Greetings!
Attachments
altered_categories_method2.tar.gz
(6.78 KiB) Downloaded 435 times
Last edited by SFR on Tue 26 Nov 2013, 10:35, edited 1 time in total.
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#433 Post by musher0 »

@SFR:
Thanks for your input.

@all:
Mick will tell us more, I'm sure, when his study is over. But from what I
gathered from my exchanges with him and from the feedback, it seems
quite likely that the rare pupsave creation bug is a:
* file system recognition problem in the code
* perhaps linked with a timing thing,
* occurring when large external drives, such as eSATA drives, are used
__ to nest the Puppy.

So this bug affects very few users. No locale is to blame, and the low-
level Linux "sensors" such as blkid indicate the file system of the partitions
correctly. This is what is known for sure at this time about this bug.

In the meantime, I have summarized four work-arounds -- for dummies!
:) I've tried to keep the explanations simple -- at the top of this thread:
http://murga-linux.com/puppy/viewtopic. ... ost#738908.
If you know someone who has this problem, please refer them to it?

As well, if you have suggestions as to the presentation, or other solutions,
please let everybody know in that other thread?

Thanks in advance. BFN.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#434 Post by bigpup »

My making of a save file is close to what others have posted.
Nothing new to add.
occurring when large external drives, such as eSATA drives, are used
__ to nest the Puppy.
Wonder if Puppy being a 32 bit operating system, could be part of the problem dealing with large drives?

Maybe something here is part of the problem.
http://www.ibm.com/developerworks/linux/library/l-gpt/
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#435 Post by musher0 »

Hi, bigpup.

Do you mean you had trouble creating a pupsave on a large external
hard drive? (Your wording makes it unclear in my mind.)

In any case, it occurred to me tonight: what if the busybox blkid --
present in both wanderer's CE3 Puppy and 01micko's new slacko --
was the culprit?

The Lucid "breed" of Puppies offers an actual blkid utility and does not
have the pupsave bug.

Just a thought. It's not that important anymore, since we have relatively
easy-to-use work-arounds now.

BFN.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#436 Post by musher0 »

@bigpup:

Additional thought: if it was a 32-bit vs 64-bit thing, wouldn't we have a
similar bug each time we save to a large external drive on a 32-bit Puppy?
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#437 Post by bigpup »

musher0 wrote:@bigpup:

Additional thought: if it was a 32-bit vs 64-bit thing, wouldn't we have a
similar bug each time we save to a large external drive on a 32-bit Puppy?
Just bringing up ideas to check.
Not sure if this is a specific 32 bit operating system problem or more to do with what partition system is on the HDD and how it is supported by the operating system.

Example:
Once a remote prospect, an important barrier in disk storage has become a reality: the venerable master boot record (MBR) partitioning scheme can't fully handle disks larger than 2.2TB (2TiB). With disks as large as 3TB readily available and with much larger RAID arrays common, alternatives to the MBR partitioning scheme have become important to understand. The heir apparent is the GUID Partition Table (GPT). Learn how to make sure your Linux system is fully prepared for the future of disk storage.
Info from:
http://www.ibm.com/developerworks/linux/library/l-gpt/
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#438 Post by musher0 »

musher0 wrote:Hi, bigpup.

Do you mean you had trouble creating a pupsave on a large external
hard drive? (Your wording makes it unclear in my mind.)

In any case, it occurred to me tonight: what if the busybox blkid --
present in both wanderer's CE3 Puppy and 01micko's new slacko --
was the culprit?

The Lucid "breed" of Puppies offers an actual blkid utility and does not
have the pupsave bug.

Just a thought. It's not that important anymore, since we have relatively
easy-to-use work-arounds now.

BFN.

musher0
Hello, bigpup.

I did another test and actually, using the actual blkid utility instead of the
busybox one did solve the pupsave-creation bug at the code level. So we
now have 4 work-arounds and one real code solution. I gather Mick will
find an elegant way to integrate this solution in his next slacko.

Concerning the new GPT disk paradigm you mentioned -- It's good to
think ahead. But, speaking for myself, at present I have 22 % occupation
of a total 1.128 Tb disk capacity. I have about 10 Puppies on there, plus
XP, and 3 other Linux distros -- not to mention about 100 G worth of back-
ups. I feel it's a bit early for me to be concerned, since I've got 68 %
wiggle-room left. I suppose I'll cross that bridge when I get there -- in a
couple of years.

I'm sure I'm not the only Linuxian taking pleasure in "beating the system"
-- i.e. pushing an older machine to the max before considering buying
newer hardware. It's one of the strengths of Linux generally, and Puppy
has achieved resplendent results in this area. Let's hope BK's successors
-- the new Puppy "guard", so to speak -- will maintain that philosophy.

BFN.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#439 Post by 01micko »

Hello friends!

I am building another now, made some relevant commits to woof, put blkid in the template is one (TY musher0), and also added some new ideas, some from Mr KRG. There are a few more from zigbert too, hope they work fine for you. Also added bugfixes for hiawatha, categories and other files (TY SFR).

My intent is to get slacko 5.7 out soon, then leave slacko alone for awhile and help pemasu port wheezy to woof-CE. I have already built raspberry pi (ZAP6) with debian wheezy armel bins and that pretty much worked so I'll add the infrastructure included there and get pemasu's advice as needed (when he has time, he's a busy guy ATM).

I think Upup will remain in petty good shape, oldyeller has his OVprecise using woof_CE, I urge you to test that too at your convenience.

As usual, when I get closer with these woof bugs, I'll get a non-PAE kernel out too. The only reason this one is PAE is that's what I had in my config at the time!

I'll build video drivers too, so it wont be a 'half arsed' release. I take some pride in my work!

If I get time after that, I'll do updates on thin and phat slacko variants. But as you can appreciate, there is a lot to do with woof alone. I wouldn't mind stepping back from slacko dev all together and letting some one else have a go.. but who would stick up their hand? You? [ :lol: ].

The next will be released in delta form only at first, full iso later, and I'll probably start a new thread as it will be "official alpha" or maybe I'll just leave the delta, squash a heap of bugs then go with a full iso for beta as the one after.. I struggle a bit with bandwidth here...[ Oh.. sheet.. can I use the term 'alpha' ? :lol: ].

Thanks everyone for reports and fixes.

Cheers!
Puppy Linux Blog - contact me for access

User avatar
mister_electronico
Posts: 969
Joined: Sun 20 Jan 2008, 20:20
Location: Asturias_ España
Contact:

hi

#440 Post by mister_electronico »

It may be possible that Pi Rasperry worked with Slacko? I'm looking to buy a Pi Rasperry soon.

Greetings.

Post Reply