Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 16 Oct 2018, 00:17
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
xenialPup-7.0.6 32-bits with kernel 4.1
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 11 of 12 [169 Posts]   Goto page: Previous 1, 2, 3, ..., 9, 10, 11, 12 Next
Author Message
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Tue 22 May 2018, 20:23    Post subject:  

Thanks for the good wishes, including the "young" part! Wink

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
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
glene77is


Joined: 17 Aug 2010
Posts: 136
Location: Memphis, TN, USA

PostPosted: Thu 31 May 2018, 18:48    Post subject:
Subject description: 64 bit Xenialpup on a 32 bit computer
 

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 Razz
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.
Back to top
View user's profile Send private message Visit poster's website 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Thu 31 May 2018, 19:24    Post subject:  

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.
lshw-short-musher0.zip
Description 
zip

 Download 
Filename  lshw-short-musher0.zip 
Filesize  907 Bytes 
Downloaded  39 Time(s) 

_________________
musher0
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
glene77is


Joined: 17 Aug 2010
Posts: 136
Location: Memphis, TN, USA

PostPosted: Wed 06 Jun 2018, 10:42    Post subject:
Subject description: Xenial Pup sfs_load
 

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 Razz
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.
Back to top
View user's profile Send private message Visit poster's website 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Sat 09 Jun 2018, 18:15    Post subject:
Subject description: Xenial Pup sfs_load
 

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
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
glene77is


Joined: 17 Aug 2010
Posts: 136
Location: Memphis, TN, USA

PostPosted: Sat 09 Jun 2018, 20:49    Post subject:
Subject description: Xenial Pup sfs_load
 

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 Razz
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.
Back to top
View user's profile Send private message Visit poster's website 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Sun 22 Jul 2018, 02:02    Post subject:  

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
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
Dry Falls

Joined: 16 Dec 2014
Posts: 571
Location: Upper Columbia

PostPosted: Sun 22 Jul 2018, 12:54    Post subject:  

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.
Quote:
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!
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Sun 22 Jul 2018, 16:37    Post subject:  

Hello, bash haters! Wink

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?) Smile

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
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Tue 24 Jul 2018, 01:22    Post subject:  

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
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
glene77is


Joined: 17 Aug 2010
Posts: 136
Location: Memphis, TN, USA

PostPosted: Fri 03 Aug 2018, 22:49    Post subject:  

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 Razz
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.
Back to top
View user's profile Send private message Visit poster's website 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Fri 03 Aug 2018, 23:31    Post subject:  

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
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Sat 04 Aug 2018, 05:23    Post subject:  

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
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Wed 08 Aug 2018, 22:33    Post subject:  

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?topic=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
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
glene77is


Joined: 17 Aug 2010
Posts: 136
Location: Memphis, TN, USA

PostPosted: Sat 08 Sep 2018, 03:20    Post subject:
Subject description: Logging Bash script
 

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.

_________________
Puppy Linux is more fun than a barrel of M$ monkeys Razz
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.

Last edited by glene77is on Fri 14 Sep 2018, 13:14; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 11 of 12 [169 Posts]   Goto page: Previous 1, 2, 3, ..., 9, 10, 11, 12 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1070s ][ Queries: 13 (0.0396s) ][ GZIP on ]