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 Thu 19 Sep 2019, 00:17
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
BionicPup32 (UPupBB) (15 September 2019)
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 38 of 46 [678 Posts]   Goto page: Previous 1, 2, 3, ..., 36, 37, 38, 39, 40, ..., 44, 45, 46 Next
Author Message
B.K. Johnson

Joined: 12 Oct 2009
Posts: 757

PostPosted: Tue 26 Mar 2019, 14:40    Post subject:  

@peebee
Re bionicpup32-8 k4.9.163, do you plan on making a pet available for rtl8812au, as was done for k4.9.96 during the upupbb testing phase? Could you? TIA

_________________
B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM

Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3987
Location: Worcestershire, UK

PostPosted: Tue 26 Mar 2019, 15:39    Post subject:  

wanderer wrote:
but i can't find out how to install dillo

Should be in universe....
https://ubuntu.pkgs.org/18.04/ubuntu-universe-i386/dillo_3.0.5-4build1_i386.deb.html

pkgs.org is always a good place to go.....

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Back to top
View user's profile Send private message Visit poster's website 
mavrothal


Joined: 24 Aug 2009
Posts: 3057

PostPosted: Tue 26 Mar 2019, 15:42    Post subject: Re: BionicPup32 (UPupBB) (March 2019)
Subject description: Woof-CE 32bit build using Ubuntu Bionic Beaver (18.04) components
 

peebee wrote:

The Ibiblio version will always be the latest with all known bugs squashed

You better make sure that would be able to determine which ibiblio 8.0-uefi version is used because otherwise resolving issues can become problematic.
Maybe a /etc/builddate or an /etc/updateverion file or something like it.
In general, I think that having different things under the same name is not a recommended practice.

_________________
== Here is how to solve your Linux problems fast ==
Back to top
View user's profile Send private message 
wanderer

Joined: 20 Oct 2007
Posts: 1112

PostPosted: Tue 26 Mar 2019, 15:44    Post subject:  

thanks peebee

like i said beautiful work

thanks for making it


wanderer
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3987
Location: Worcestershire, UK

PostPosted: Tue 26 Mar 2019, 15:45    Post subject: Re: BionicPup32 (UPupBB) (March 2019)
Subject description: Woof-CE 32bit build using Ubuntu Bionic Beaver (18.04) components
 

mavrothal wrote:
You better make sure that would be able to determine which ibiblio 8.0-uefi version is used because otherwise resolving issues can become problematic.
Maybe a /etc/builddate or an /etc/updateverion file or something like it.
In general, I think that having different things under the same name is not a recommended practice.

They are not the same name deliberately....
See /etc/system_build_date ......

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Back to top
View user's profile Send private message Visit poster's website 
bigpup


Joined: 11 Oct 2009
Posts: 12570
Location: S.C. USA

PostPosted: Tue 26 Mar 2019, 19:57    Post subject:  

peebee,

The Distrowatch announcement is out about Puppy 8 release.
https://distrowatch.com/?newsid=10501
They have the info about Bionicpup64 8.0, but not your Bionicpup32 8.0

Give them some info!

Oh, I see, if you go to some of their links you get 32bit info.

A download link on that first Puppy Linux topic for the 32bit would be good to have.
Plus a few words about there being a 32bit version.

You have made it to osdisc.com
https://www.osdisc.com/products/puppy
That is better than Distrowatch Laughing Very Happy
They too seem to need a little info update about Bionicpup32 8.0

_________________
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 Shocked
YaPI(any iso installer) http://www.murga-linux.com/puppy/viewtopic.php?t=107601
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3987
Location: Worcestershire, UK

PostPosted: Wed 27 Mar 2019, 03:07    Post subject:  

bigpup wrote:
The Distrowatch announcement is out about Puppy 8 release.

I don't know who wrote the DW words - I certainly wasn't asked to contribute....

I suspect that a new thread authored by "Lobster" has been used..........
http://www.murga-linux.com/puppy/viewtopic.php?t=115733

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Back to top
View user's profile Send private message Visit poster's website 
bigpup


Joined: 11 Oct 2009
Posts: 12570
Location: S.C. USA

PostPosted: Wed 27 Mar 2019, 09:46    Post subject:  

Someone at Distrowatch usually does the info statements, but they base it on what they are given when you submit a new Linux OS for them to consider posting about.

Probably 666philb gave them info for Bionicpup64 8.0

You as the developer of Bionicpup32 8.0 need to give them info for it.

Distrowatch Distribution Submission info page.
https://distrowatch.com/dwres.php?resource=submit
I would make sure you tell them this is the 32bit version of Puppy Linux 8.

_________________
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 Shocked
YaPI(any iso installer) http://www.murga-linux.com/puppy/viewtopic.php?t=107601
Back to top
View user's profile Send private message 
B.K. Johnson

Joined: 12 Oct 2009
Posts: 757

PostPosted: Wed 27 Mar 2019, 15:54    Post subject:
Subject description: Hmmm! Release with new kernel untested
 

Just an observation! No response necessary.
But the logic escapes me. upupbb goes through the entire testing phase from upupbb-18.05+0 to upupbb-18.05+28 with k4.9.96.
Testing is done, bionicpup32-8 and bionicpup64-8 (the post test versions) are released with k4.9.163 (no testing). Hmmm!

_________________
B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM

Back to top
View user's profile Send private message 
Marv


Joined: 04 May 2005
Posts: 1189
Location: SW Wisconsin

PostPosted: Wed 27 Mar 2019, 23:20    Post subject: multi-pup throughput observation  

Don't know quite where to put this as it is a cross-pup cross kernel comparison but it started with upupbb so my ramble goes here... Ok to move it or I can just delete it if it's inappropriate.

Hardware: My usual i5 based laptop, Grub4Dos installs on a Samsung 850 evo SSD. 4Gb memory.

Observation triggering testing. Over a number of kernels and pups tested pretty thoroughly over time (4.9.96, 4.9.134, 4.9.163 (32b), 4.20.xx through 5.04 (64b) in upupbb, upupcc, LxPupBionic, LxPupSc, and LxPupSc64 a consistent pattern began to emerge wrt perceived SFS load times. In particular my 76 Mb Slimjet ones. LxPupSc64 always seemed fastest (no real surprise) and upupbb always slowest by a lot. upupcc always felt 'snappier' than upupbb, but the timed difference between those two was another surprise. hdparm results over a long time have been pup and kernel invariant and the memory is tested and the same in all cases.

Today I timed the first loads (roughly counting seconds). I then tested disk and memory throughput using dd in each of the above pups with most of the above kernels swapped in. I had been doing dd tests manually but found a script which matches my manual times pretty well and really speeds up the testing. It is attached as a false gz, Author credits at top of script.

Two surprises. One, that results were very nearly kernel invariant. Two, that the big differences were in HDD throughput, not memory throughput. ie:
Code:
     Pup         SFS load time       Mem I/O Gb/s     HD I/O Gb/s

LxPupSc64        4 sec                    2.3                    2.2
LxPupSc          4 to 5 sec               2.3                    2.2
upupcc            9 sec                      2.2                    2.1
LxPupBionic      NA                        2.15                  1.2
upupbb            17 sec                   2.0                    1.15


Several reps and several kernels represented in each of the above rows. Variability on repeat tests was 0.1 or less as was the kernel-to-kernel variability within a pup.

I have no clue at all as to the why, nor do I expect one. What it does for me is to quantify my gut feeling and give me an excuse to ride the faster horse Wink It also gave more time mashing the kernels above, all of which remain rock solid on my pups and hardware.
memspeed_tester.sh.gz
Description  False gz. Remove, inspect and make executable.
gz

 Download 
Filename  memspeed_tester.sh.gz 
Filesize  2.95 KB 
Downloaded  46 Time(s) 

_________________
Pups currently in kennel Very Happy LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64, LxPupBionic and upupdd for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
Back to top
View user's profile Send private message 
glene77is


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

PostPosted: Thu 28 Mar 2019, 12:27    Post subject:  

UpupBB Bionicpup32 ok here.
Interesting code work in UpupBB.
More organized than prior versions of puppy.
Using the # 2 8 version of .ISO.
The run-time is longer during "sysinit".
The run-time is longer during "save2flash"


I enjoy tracing the running code ...
to wit, I wrote a short "signature" into the header of
"rc.sysinit", "rc.shutdown", "sfs_load", "fixmenus".
Like this:

### === Signature

lcMsgStr="rc.sysinit $1"

/bin/echo -e "\\033[13G\\033[1;37m * \\033[1;31m $lcMsgStr \\033[0;39m" > /dev/console

### end: Signature

This little trace shows during startup and shutdown,
and there are many dozens of other little tracers like this
ticking-up and displaying the real-time / colorful flow of the code.
Back in 1979, I wrote in four different assembler languages,
and 'tracers' like this were the only way to survive !

Have Slacko, Tahr, UpupBB installed and running identically.
Early on, I wrote these tracing "flow notes"
into a progressive log file with the real-time date-time-stamp .
I found the log files interesting to review,
and helped me keep tabs on the time required
to run through "sfs_load" and "fixmenus".

I notice that "fixmenus" run
may be called 3 times during the system init.

I noticed that "sfs_load" may be called multiple times,
and now ( in # 2 8 ) there are two "exit" checks
in the header of "sfs_load".

[ When I run and watch the tracing on Tahrpup,
I notice that "sfs_load" may be called after the last line of code
in "rc.sysinit".
But, No such curiosity flushing a stack with UpupBB. ]

In UpupBB, "sfs_load" ,
there are two short blocks of code doing
an "exit" check in the header of "sfs_load".
"sfs_load" is called and may "exit" for two different reasons.
The tracer showed each time "sfs_load" started,
and another showed each time it did an "exit".
Other tracer lines showed exactly what was being loaded
and the progression of initializing during "sfs_load"
and the interplay with "fixmenus" .

I noticed in UpupBB that the audio player intro plays most of the time.
This is a neat way to cover the long initialization routines
that occur after "sysinit" has finished its code run.
When I introduced this type of audio code at the tail-end of "sysinit"
it played sometimes.

Next are two Little , and Non-Fatal, problems.

Little Problem (1)
"pmcputemp" does not work properly.
My PC is a 2005 HP and does not do temp monitoring. .
On initial "bootup" the "pmcputemp" pops up
with an error message.
I use File Find to locate and rename the offending script.
Will only come up again
IF I revise the systems files from a new .ISO.
Guess I should write a little script to rename the file.

Little Problem (2)
Executing "save2flash" will cause a little "green" window
in the bottom tray to start flashing "red",
This which means that
(1) the savefile has been renamed during run-time
or
(2) has become 'unknown'.
In testing this little problem,
the savefile is not disconnected ... just flashes red.
Sometimes, like right now ,
the little "red" flashing window has disappeared.
This is not "fatal" as I know about the integrity of the "savefile",
and maintain progressive backups of the "savefile" .

To PeeBee, you have a lot of talent.
Thanks for this latest version.

_________________
Puppy Linux is more fun than a barrel of M$ monkeys Razz
www.geocities.WS/glene77is
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.
Back to top
View user's profile Send private message Visit poster's website 
bigpup


Joined: 11 Oct 2009
Posts: 12570
Location: S.C. USA

PostPosted: Fri 29 Mar 2019, 14:58    Post subject: Re: BionicPup32 (UPupBB) (March 2019)
Subject description: Woof-CE 32bit build using Ubuntu Bionic Beaver (18.04) components
 

peebee wrote:
mavrothal wrote:
peebee wrote:
BionicPup32 on SourceForge

BionicPup32 on Ibiblio

It would appear that the ibiblio and SourceForge base ISOs are different (8.0-uefi vs 8.0+0-uefi) and the ibiblio one is not "updatable". Is this the case?
I do not know if this indeed is the case and if it is intentional but does not sound very nice if true. Specially if the one in ibiblio has know bugs.

Intentional.
The Ibiblio version will always be the latest with all known bugs squashed - i.e. curently is 8.0+1 so indeed different to 8.0+0 which is the "base" iso.....there is a text file on ibiblio that gives the md5s

The ibiblio version is not directly updateable - the base iso would be needed from SF - or the ibiblio iso can be renamed and a "reverse-update" applied.

I am not seeing what you say here.
Quote:
The Ibiblio version will always be the latest with all known bugs squashed - i.e. currently is 8.0+1

The iso at ibiblio is bionicpup32 8.0-uefi.iso

Quote:
The ibiblio version is not directly updateable

True, but it never seems very long before they get the update posted at ibiblio.
Usually within 24 hours of giving them the new version iso, program pet, changed software, etc.....

If you are going to offer a delta that is going to change the iso name.
ibiblio should now be offering that newly named iso for download.
The older iso should no longer be listed at ibiblio.

Ibiblio is being used as the official Puppy repository.

_________________
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 Shocked
YaPI(any iso installer) http://www.murga-linux.com/puppy/viewtopic.php?t=107601
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 12570
Location: S.C. USA

PostPosted: Fri 29 Mar 2019, 15:56    Post subject:  

Bionicpup32 8.0+1

menu>System>System Update

A information window pops up, but does not stay visible long enough to read it.
Could it be made to start the browser and go to the update web page, after you click on the OK button on this info window Idea

_________________
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 Shocked
YaPI(any iso installer) http://www.murga-linux.com/puppy/viewtopic.php?t=107601
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3987
Location: Worcestershire, UK

PostPosted: Sat 30 Mar 2019, 06:31    Post subject:  

bigpup wrote:
Bionicpup32 8.0+1

menu>System>System Update

A information window pops up, but does not stay visible long enough to read it.
Could it be made to start the browser and go to the update web page, after you click on the OK button on this info window Idea

Will do:
/usr/bin/sys_update_upupbb.sh

line 2: remove -timeout 6
line 13: remove &

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Back to top
View user's profile Send private message Visit poster's website 
glene77is


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

PostPosted: Sat 30 Mar 2019, 17:25    Post subject:
Subject description: UpupBB U-Light Browser
 

PeeBee,
Thanks for including the FireFox "U-Light" Browser.

(1) I extracted your code into a file.sfs
(2) now have it installed and running in
UpupBB, and Tahr 605, and Slackopup 632.
(3) I placed it at /root.

cul
Glen

_________________
Puppy Linux is more fun than a barrel of M$ monkeys Razz
www.geocities.WS/glene77is
glene77is --- {^,^} --- electricity is shocking, Memphis, TN, USA.
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 38 of 46 [678 Posts]   Goto page: Previous 1, 2, 3, ..., 36, 37, 38, 39, 40, ..., 44, 45, 46 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.0972s ][ Queries: 13 (0.0249s) ][ GZIP on ]