xenialPup-7.0.6 32-bits with kernel 4.1

A home for all kinds of Puppy related projects
Message
Author
musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#151 Post by musher0 »

Thanks for the good wishes, including the "young" part! ;)

Like you, I think that going back to any WhineDose incarnation is not worth
the trouble on any hardware, while there are Linux's around.

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

User avatar
glene77is
Posts: 196
Joined: Tue 17 Aug 2010, 22:09
Location: Memphis, TN, USA
Contact:

#152 Post by glene77is »

Musher
Do you think Xenialpup 64 bit could run on a 2001 HP 32 bit computer ?
Have always run 32 bit Linux, but future developments are going to 64 bit.

Here, I use grub4dos .
Ever since I compared Ubuntu vs Puppy, about seven years ago,
and switched to the compacted system files of Puppy,
I have used grub4dos.
Puppy Linux is more fun than a barrel of M$ monkeys :P
www.geocities.WS/glene77is
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.

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

#153 Post by musher0 »

Hi glene77is.

I am afraid i can be of little help concerning 64-bit Puppies. The only one
I have used is Just_Lighthouse_64-604, by forum member Dry_Falls, and
it is fabulous!

I tried a xenialPup64 once, but its performance was sluggish on my set-
up (please see attached description). So that was that, I removed it.

A sixty-four-bit Pup has the same apps as its 32-bit counterpart. If it does
not offer the speed advantage -- or maybe a needed driver written for a 64-
bit PC--, IMO, installing it is not worth the trouble.

BFN.
Attachments
lshw-short-musher0.zip
(907 Bytes) Downloaded 446 times
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
glene77is
Posts: 196
Joined: Tue 17 Aug 2010, 22:09
Location: Memphis, TN, USA
Contact:

#154 Post by glene77is »

Musher,
I have been noticing that the subroutine in sfs_load "waitsplash"
does not do anything.
I have tried running the line
/usr/lib/gtkdialog/box_splash -text "$* $(gettext "Wait a moment ...")"
at the end of the rc.shutdown program.
( end of the shutdown is where I test routines).

. /usr/lib/gtkdialog/box_splash -text "$* $(gettext "Wait a moment ...")"

What is the "$*" , a variable ?

If you could, please, suggest a correction (or tutorial text)
on this simple routine.
BASH has been an interesting, if convoluted, experience.

As a background,
I spent several decades writing commercial relational-databases
in the highly structured world of FoxPro and T-SQL.
BASH is not so highly structured.



...
Puppy Linux is more fun than a barrel of M$ monkeys :P
www.geocities.WS/glene77is
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.

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

#155 Post by musher0 »

glene77is wrote:Musher,
I have been noticing that the subroutine in sfs_load "waitsplash"
does not do anything.
I have tried running the line
/usr/lib/gtkdialog/box_splash -text "$* $(gettext "Wait a moment ...")"
at the end of the rc.shutdown program.
( end of the shutdown is where I test routines).

. /usr/lib/gtkdialog/box_splash -text "$* $(gettext "Wait a moment ...")"

What is the "$*" , a variable ?

If you could, please, suggest a correction (or tutorial text)
on this simple routine.
BASH has been an interesting, if convoluted, experience.

As a background,
I spent several decades writing commercial relational-databases
in the highly structured world of FoxPro and T-SQL.
BASH is not so highly structured.
...
Hi glene77is.

Reading your background, I feel you must be way ahead of me on so
many computing subjects. You are a professional and I am only an
"amateur" (hopefully in the positive sense of the word). As a university
student, I tried APL (unsuccessfully!) for a few months, then many years
later Atari Basic and TurboBasic, then with Puppy, bash (and a bit of ash).

I haver never ventured into gtkdialog coding, so I cannot help you,
unfortunately.

The simplest thing to do IMO would be to mention this oversight directly
to the author of sfs_load, "shinobar". AFAIK, he has not posted on this
board for a long time. Try PM'ing him anyway? Who knows, maybe he's
still around, lurking ?!

Other that that, off the top of my head, I'd say your go-to persons for
gtkdialog code would be forum members "MochiMoppei" and "wiak".
Perhaps send them a PM? There are other competent gtkdiapog coders
on this board, but their names escape me at this time.

Also, there are a few gtkdialog threads on the forum: perhaps browse
through them and / or repost your question in one of them.

Best of luck. Sorry I cannot be of more help...

~~~~~~~~~
PS. I almost forgot to mention that one sure way of drawing attention to
the problem, and potentially a solution to it, is to create a separate thread
for the problem.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
glene77is
Posts: 196
Joined: Tue 17 Aug 2010, 22:09
Location: Memphis, TN, USA
Contact:

#156 Post by glene77is »

Musher,
Thank you for the informative and tempered response.
We are who we are.
Your suggestion to post in a new topic is appropriate.
I have found a tutorial on GTK,
and (functionally) this is not a serious problem.
I did resolve the problem of "where" Xenial is slowing down.

Wished I were a young man and a serious student, again.
That is what got me into radio electronics and Linux.
BASH is a bitch , but there is much more BASH code in this river
... the learning curve into complex functions
is steeper than first appears.
Copying previous working system code is a good first step.
I have found several good tutorials.

Thanks again,
and I hope you continue your serious interest
in these technologies.

My website is www.GeoCities.WS/glene77is
Puppy Linux is more fun than a barrel of M$ monkeys :P
www.geocities.WS/glene77is
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.

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

#157 Post by musher0 »

Hello all.

Pet archives for text editors:

cudatext-1.55 ( url] https://en.wikipedia.org/wiki/CudaText [/url])

AND

joe-4.6 ( url] https://en.wikipedia.org/wiki/Joe's_Own_Editor [/url])

for xenialPup-7.0.6 (a 32-bit PuppyLinux) are now available for download
and install from: http://augras.eu/puppy_linux/?dir=musher0/Editeurs

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

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#158 Post by Dry Falls »

glene77is wrote:Do you think Xenialpup 64 bit could run on a 2001 HP 32 bit computer ?
As far as I know, trying to boot a 64bit os on a 32 bit box will break the processor! The obverse is, on the other hand, ok.

df

ps, thanks for the compliment, Musher. 604 is a bit buggy. In some ways, JL64 just keeps getting worse! but I'm trying.
BASH is a bitch , but there is much more BASH code in this river
... the learning curve into complex functions
is steeper than first appears.
Copying previous working system code is a good first step.
is an understatement!

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

#159 Post by musher0 »

Hello, bash haters! ;)

I beg to disagree with both of you!

Bash is a fine programming environment. It's dynamic (as in "runtime"), it
can call into play any GNU utility, plus the richness of awk, the ANSI
escape codes, and even incorporate a few short C one-liners.

(Before you tag ANSI escape codes as passé, please read recent reports
about it. You will find that ANSI can now give access to 24-bit colors.
I repeat: 24-bit colors. Now tell me, what is passé about 24-bit colors?) :)

If you write your bash script with the attitude: "Yerk, this is bash code",
you won't get far. But give it a fighting chance, and you might be happily
surprised by all it can do for you.

Finally, if you write bash code, do not hesitate to use a worthy terminal
for it: by that I mean urxvt-9.2* compiled with "everything" (sic). I have
tried quite a few other terminals, and nothing compares to recent urxvt
versions. (This is not a sales pitch, I'm serious.)

BFN.
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

#160 Post by musher0 »

Hello all.

I forgot to mention it in my previous post:

AFAIK (you can research the Web to double-check, but I think the following
statement will stand the test),

there is a consensus among developers to the effect that bash has
the best string|variable processing capacity in the business -- bar none.


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

User avatar
glene77is
Posts: 196
Joined: Tue 17 Aug 2010, 22:09
Location: Memphis, TN, USA
Contact:

#161 Post by glene77is »

Musher,
Thank you for your patience.
I have a positive attitude about BASH working right and effectively.
... I am also realistic about the layers of script development
since my days with Unix , SCO-Unix and KornShell in the 1990's.
Not that I was great with KornShell
... being a FoxPro specialist
working on relational database developments in SQL.

Very recently, with my XenialPup 7.0.8 on several PC's,
I was working through some BASH in the early startup routines
for XenialPup, and found a point where "SH" was called,
and then several lines later "BASH" was called and used thereafter.
I call that expert code work
... knowing the nuances of an earlier
version requires talent and experience.
I tip-my-hat to the author of that code block
... but , I also find it frustrating to follow ,
a good bit up-hill.
It just takes more time and effort for this old guy
than it used to, 40 years ago !

I always say
"Puppy Linux is more fun than a barrel of M$ monkeys ! "


dry falls
" The obverse is, on the other hand, ok. "
I like the "reverse English format", a little like Shakespeare.

"the best string|variable processing capacity "
and I am slowly becoming more proficient with this,
although my code is second-hand, not very creative.



To All,

I have implemented a logging system ( /bin/echo > /logfile.txt ) .
which shows me the sequence of subroutine calls
( function() plus date-time-stamp ).

It appears that some subroutines in "sfs_load" are never called,
at any time during a session. Not during startUP nor during shutDN.

I have timed the "sfs_load" and the "fixmenus" time requirments.
I have a sequential logfile.txt which allows me to trace the calls,
and inspect the occurances and time-requirements.

For the "sfs_load" and "fixmenus" , which were my first interest,
some subroutines are never called. Perhaps they are "legacy" code.

As for "run-time" requirements,
which was a complaint in prior postings of this thread,
I note the following:

It seems that from one PC to another, the time requirements change.
As I watch the screen display, and inspect the logfile.txt
they total about 30 seconds to 40 seconds.
I was surprised to see that "fixmenus" may be called a second time
during startUP, if I have just done a backup / rename of the ramsavefile.
"sfs_load" takes 20 to 25 seconds, and "fixmenus" usuall 7 seconds.
The time required depends on which PC is being used.
The Dell with a dual-core is faster crunching code,
but the file handling is slower.
The HP (2001) is slow on code crunching,
but the file handling is faster.

None of this is cut-in-stone,
Your Milage May Vary.
Puppy Linux is more fun than a barrel of M$ monkeys :P
www.geocities.WS/glene77is
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.

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

#162 Post by musher0 »

Thanks, glene77is.

I may be interested in this time-logging script of yours for sfs_load.

Maybe I'm looking in the wrong direction, but I'm trying to understand if we
can revive the old sfs loading type (using the version number of the Pup)
that existed in the early Puppies 4* versions.

Do you think you could make a copy available? Here or wherever.

TIA.
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

#163 Post by musher0 »

Hello Glen and all.

Please note that from now on I will be servicing questions in English for the
"xenialPup-7.0.6 32-bits with kernel 4.1" from the Puppy section of an outside
forum. Please leave me a note and/or your question by PM, and I will give you
its coordinates.

For reasons I do not wish to expand upon, I have decided to limit my visits on
this murga/Puppy forum to information search only.

Thank you for your understanding.
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

#164 Post by musher0 »

Hello all.

For those of you who find annoying that all system and GTK error and
warning messages from this ubuntu-derived pup are logged in tmp/xerrs.log,
here is a solution in three parts: two scripts and one add-on to your
~/.bashrc file.

https://augras.eu/puppy_forum/index.php ... 105.msg345
(All this page is devoted to this problem).

You will find similar introduction and comments in English here:
http://softwarefreedom.jcink.net/index.php?showtopic=59
You are invited to discuss these scripts, etc. on the software-freedom forum.

Unfortunately, this jcink forum cannot process attachments, so the files and
illustrations are on the augras forum. Sorry for the inconvenience.

However the comments in the scripts themselves are both in FR and EN.
I apologize in advance to those of you who are not internationalists.

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

User avatar
glene77is
Posts: 196
Joined: Tue 17 Aug 2010, 22:09
Location: Memphis, TN, USA
Contact:

#165 Post by glene77is »

Musher,
""" time-logging script of yours for sfs_load. """

Simple approach.
(0)
In the rc.sysinit program, at the top, init the logging file Only One Time !
with a simple write :

############################################
logfunkupinit() {

### run spec_set() prior ( for me, it loads declares/assigns variables.

GaeLogFunkUp="/GAE-log-funk-up.tmp" ### logging-output-file.txt
lcFileStr="/GAE-log-funk-up.tmp"
### "/" is always available to puppy running in RAM.
### convenient location. Later, I copy contents to "/mnt/home".

/bin/echo -e "===========================" > ${lcFileStr}

### dts (date-time stamp) on all lines written into the log-file.

lcDtsLogxit="`date -R | cut -f 2-5 -d ' ' | cut -f 1 -d '.' | tr '[a-z]' '[A-Z]'` z"

lcMsgLogxit="logfunkupinit: rc.sysUP . 'INITZ' . ${GaeSysBuild} "
/bin/echo -e "$lcMsgLogxit" >> ${lcFileStr}

### identify the
### (1) current subroutine (2) file doing the writing (3) dts :
lcMsgLogxit="logfunkupinit: rc.sysUP . 'INITZ' . ${lcDtsLogxit} "
/bin/echo -e "$lcMsgLogxit" >> ${lcFileStr}
/bin/echo -e "=======================" >> ${lcFileStr}

} ### logfunkupinit




#############################################
(2) Insert this "Library Subroutine" in the first lines of each file to be logged.
This example is for "sfs_load", and it titled "logfunksfs" .

Script for "fixmenus", and all other files is similar ,
just ID each program: "sfs_load","fixmenus", "rc.sysUP", "rc.sysDN", etc.
Each of these programs makes many calls to its own "logfunk???"
This example is for "sfs_load", and it titled "logfunksfs" .


logfunksfs() {

### (1) incoming parameter message,
lcMsglogfunk="'$1'"

### (2) date-time-stamp
lcDtslogfunk="`date -R | cut -f 2-5 -d ' ' | cut -f 1 -d '.' | tr '[a-z]' '[A-Z]'` z"

### (3) logging target file
Gaelogfunkup="/GAE-log-funk-up.tmp"

### build final string to write
### (1) insert current subroutine , ie, "sfs_load" or "fixmenus", etc.
### (2) param msg
### (3) dts (date-time-stamp)

lcMsglogfunk="sfs_load: '$1' : ${lcDtslogfunk} "

### ( ) echo out to logging file.
echo -e "$lcMsglogfunk" >> ${Gaelogfunkup}

} ### end logfunksfs
###...........................................................................

I plan to post to my website.
Last edited by glene77is on Thu 09 Jan 2020, 03:57, edited 2 times in total.
Puppy Linux is more fun than a barrel of M$ monkeys :P
www.geocities.WS/glene77is
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.

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

#166 Post by musher0 »

Hi Glen.

Thanks for the logging code.

As to your 256 G Sandisk "locked" problem, I'd post it on its own thread in
the forum. You have a much greater chance of drawing attention from
people if it has its own title in the threads list -- than buried here.

As for me, I am pretty much clueless (with a couple of exceptions)
concerning hardware. So... no, I won't give you a bash one-liner for this,
I'm not that sure of myself!!! ;)

However, my initial instinct would be to answer: have you tried to change
the properties of the partition through the ROX-Filer ? Please see attached
capture.

That panel can be obtained by typing Ctrl-P in /mnt; then a crosshair
appears, and then you click on the desired partition with this crosshair.

You should be able to change (tick / un-tick) any of the boxes. But don't
mess with it. The example presented allows read-write-and-execute for
anything on this ram1 partition (in other words: it is the default, as it
should be for regular use partitions).

Perhaps you need to do this from the Puppy or OS the crash occurred on.
(Note the "perhaps".)

I'd also suggest a poweroff and reboot of your Pup with the drive connected.
Sometimes, this by itself is enough to reset the normal partition defaults.

Poweroff, not just reboot. As in:
-- poweroff everything, including turning off the monitor, the speakers, and
any outside drive;
-- wait a couple of minutes;
-- turn everything on again, and then reboot as you normally do.

IHTH.
Attachments
partition-properties.jpg
(84.37 KiB) Downloaded 1328 times
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
glene77is
Posts: 196
Joined: Tue 17 Aug 2010, 22:09
Location: Memphis, TN, USA
Contact:

#167 Post by glene77is »

Musher
Thanks for the tips.
Have tried most, and will go through all again.

Always a possibility,
I may have mounted it away from the fan,
and the 256 GB flashdrive got hot with mass copying.
Normally, I keep the large flashdrives by the fan,
hanging on a USB multiport. Otherwise, they get hot on mass copying.
When I say 'mass copying',
I refer to a mass copy of my 'backup' 256 GB
onto a new 256 GB.

Have gone back to the Hard-Drive and installed puppy distros for :
Lupu 525, Slacko 57, Slacko 632, Tahr 605, Xenial 708.
Have set up Directory version and/or the 4fs version
and plan to have both versions available from menu.lst.
Most function OK now.

I have found I like developing/mucking/tinkering in the Directory version.
I like the security made available by skipping the save2flash function.
When I make a mistake in codework, I just break-out and "reboot"
which reloads the prior version and I can start again.

Since I do frequent save2flash and then xarchive the savefiles
( which include a date-time-stamp in their name )
I noticed that the 256 GB flashdrives can get hot.
So, I hang then from a USB multiport, over the computer fan.



For developing a 4fs version,
to include custom display tracking and logging functions,
I use this technique :
(1) I have been able to load the 4fs version into Geany
( all relevant programs like rc.sysinit, rc.shutdown, sfs_load, fixmenus)
(2) then import (via Geany ) from the Directory version.

It is basically a Careful "copy/paste all" method.
WHEN I do a
(1) Geany "save"
(2) "save2flash"
THEN the 4fs file updates all index and file lengths.

I found an un-suspected feature
when setting pmode = ataflash or atahd or usbflash.
In general :
(1) "ataflash" or 'usbflash' requires a Linux ( ext2,3,4 partition) Directory ,
and allows the 'asktosave' to control saves.
(2) "atahd" can use the current hard-drive NTFS partitiion,
in a 4fs savefile, with 'auto save' .

This little discovery allows me to run Xenial ( both 4fs and Directory)
on my hard-drive system computer.
Prior to this, I had to always run the 4fs version on the hard-drives.



#==============================================================================
#&&& Xenial 7.0.8 GAE sample Log Method
#==============================================================================

### Assume that in rc.sysinit, you echo a little string > to clear/init the LogFile.

### Insert this "sample Library Subroutine"
in the first lines of each file to be logged.
### Each running script file will call itw 'own' logfunk???"
which inserts the script name.
### This example is for "sfs_load", and it titled "logfunksfs" .

### Script for "fixmenus", and all other files is similar ,
### just ID each program: "sfs_load","fixmenus", "rc.sysUP", "rc.sysDN", etc.
### Each of these programs makes many calls to its own "logfunk???"
### This example is for "sfs_load", and it titled "logfunksfs" .

#~ logfunksfs() {

### (1) name of current running script ;
ie, rc.sysUP, rc.sysDN, sfs_load, fixmenus .
#~ lcNameStr="sfs_load"

### (2) incoming parameter message,
#~ lcMsgStr="'$1'"

### (3) date-time-stamp
#~ lcDtsStr="`date -R | cut -f 2-5 -d ' ' | cut -f 1 -d '.' | tr '[a-z]' '[A-Z]'` z"

### (4) logging target file
#~ GaeLogFunkUp="/GAE-log-funk-up.tmp"
### filename copied from /etc/rc.d/GAE/GAE-SPEC
#~ lcFileStr="${GaeLogFunkUp}"

### build final string to write
#~ lcMsgStr="$lcNameStr : $lcMsgStr : $lcDtsStr "

### ( ) echo out to logging file.
#~ echo -e "$lcMsgStr" >> ${lcFileStr}

#~ } ### end logfunksample
###...........................................................................




I don't think I am presenting anything really 'new' for you,
just a 'sharing' exercise.
As always, YMMV ( your milage may vary ) .
Puppy Linux is more fun than a barrel of M$ monkeys :P
www.geocities.WS/glene77is
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.

User avatar
glene77is
Posts: 196
Joined: Tue 17 Aug 2010, 22:09
Location: Memphis, TN, USA
Contact:

#168 Post by glene77is »

Guys,
I have resolved "my" problems with HardDrive Xenial 7.0.8
not reading a Directory SaveFile.

My old eyes did not see the difference between "," or "."
and sometimes I just imagined that there was a "," or "." written in place
--- yuk!. :shock:

So, Xenial frugal alongside M$XP :
(1) The SaveFile.4fs are installed on sda1 ( format NTFS )
(2) The SaveFile Directory are installed on sda5 ( format EXT2 )

I find that Xenial is the more tolerant of errors,
compared to Slacko 632.
YMMV !

Thanks for a place to write my little adventures.
Puppy Linux is more fun than a barrel of M$ monkeys :P
www.geocities.WS/glene77is
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.

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

#169 Post by musher0 »

Hi glen!

Thanks for the infos.

And thanks for the thanks about the writing space! (Although those should
actually be directed to forum moderator Flash and forum owner John Murga.)

BFN.
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

#170 Post by musher0 »

Hello all.

I recompiled the Sound eXchange (aka sox or SoX) version 14.4.2 (2015;
latest v. as of this writing) for xenialPup-706. It is available at:
https://augras.eu/puppy_linux/musher0/x ... 14.4.2.pet

Those of you who do not know SoX, please head for:
http://sox.sourceforge.net

In short, SoX is a sound suite in CLI that can generate sounds, play a wide
range of music formats, and process tags of music pieces. But please go
read the docs? No summary can do it justice.

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

Post Reply