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 Fri 25 Jul 2014, 13:39
All times are UTC - 4
 Forum index » Advanced Topics » Hardware
Issue that would arise in problem reporting for PRECISE ISOs
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [10 Posts]  
Author Message
gcmartin

Joined: 14 Oct 2005
Posts: 4088
Location: Earth

PostPosted: Thu 31 Jan 2013, 22:45    Post subject:  Issue that would arise in problem reporting for PRECISE ISOs
Subject description: How to tell *which* iso I'm talkiing about?
 

Barry announce a kind of combining efforts for Precise.

The upcoming Precise release is a first of its kind, in Puppyland. It will bring great innovations forward in this combined announcement. Although its not official in how this is to be released, just looking at today's forum shows us several distro offerings from the combined efforts of both BarryK and Pemasu. It is these 2 developer's efforts over 2012 that has moved Puppy into a site of innovation. I say this because these 2 people have directly made it possible to run a Puppy on a 32bit platform and have it use ALL of your RAM for the workload you put your machine through. And, these 2 have also not forgotten those who have PCs as they also continue to provide a distro which runs on PCs that are purposeful built and do not contain the memory addressing firmware built into most PCs since 1995. Although this is a very small number of PCs, the conscious attention paid by BarryK and Pemasu is a testament to the kind of people that work within the Puppyland sphere. As such, this necessitates the need for them to build separate versions for each distro they create for community use.

As we approach the upcoming release date, I would like to call to attention a problem that affect support of the different distros about to be released under the same monocle. I'll summarize the simple problem and offer an idea that could/would assist in minimize the problem's impact while making clear the issues they share.

Problem
There will be no less than 2 and possibly more of Precise(s). Thus, there will be forum efforts to address finding and issues in its use. Assuming only 2, when someone reports a problem there is no formal way to ID the distro that the problem is reported under. Thus, any user could inadvertently report a problem as, incorrectly, the "other" distro. (We have already seen this when there are 2)

Idea
This indirectly addresses a simple way for users to "see" which distro that they are using and should be reporting, should they exercise some measure of accuracy. HARDINFO that Kirk introduced 2-3 years ago, where it identifies on its 1st 2 pages the specific distro that is running in the system. This makes it simple and easy for development to ask the user which disto he has and almost make it fool-proof for him to report the distro which is running. I'm not sure what effort was involved to provide this level of detail, then or now, but, suffice it to say, it useful for ID purposes.

One case of its need in PUPs (minor idea)
I have just started to use Puppy (FATDOG) as a VM Host. If the speed remains as fast as it is (i'm currently running 5 different Puppy distros in this implementation), should I notice a problem and want to report, I do NOT have a simple step to report the distro that is running in the Virtual machine. I also have had this problem running the 5 PCs that I do when I testing several distro in the same time frame. If I stop for dinner, or family time, and come back I sometimes mistake one machine for another; necessitating the need to open the CD/DVD drawer to physically see which one I'm running. There are also other fields in HARDINFO that also are useful. HARDINFO screens from FATDOG are contained below for your review.

The idea is one to make it even easier for users to accurately identify feedback appropriate to the distro they are reporting on. Yet at the same time, making it clearer to development which distro is being reported based upon system's information.

Here to help
Hardinfo page1.png
 Description   Page 1
 Filesize   58.93 KB
 Viewed   535 Time(s)

Hardinfo page1.png

Hardinfo page2.png
 Description   Page 1
 Filesize   66.13 KB
 Viewed   543 Time(s)

Hardinfo page2.png

Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3355
Location: Oregon

PostPosted: Thu 31 Jan 2013, 23:39    Post subject:  

One other thing that bugs me is a Puppy distro in progress that only uses one topic to cover them all with an updated release for testing being in the same thread maybe 100+ messages into the thread.
And I think it would be better to create a new bug report thread for each phase of a version.

Of course in reporting a bug, for example, slacko 5.4.0, the version should be specified so the creator knows which version the bug relates to.
Back to top
View user's profile Send private message 
Q5sys


Joined: 11 Dec 2008
Posts: 1047

PostPosted: Sat 02 Feb 2013, 17:04    Post subject:  

8-bit wrote:
One other thing that bugs me is a Puppy distro in progress that only uses one topic to cover them all with an updated release for testing being in the same thread maybe 100+ messages into the thread.
And I think it would be better to create a new bug report thread for each phase of a version.

Of course in reporting a bug, for example, slacko 5.4.0, the version should be specified so the creator knows which version the bug relates to.


That's developer related. Example, TazOC has created a new thread for every new version he's put out. He simply makes a edit to the original post of the old topic pointing to the new one. He also makes a final post in the old thread pointing to the newer version.
Kirk and JamesBond have done the same with FatDog, and I plan to do the same with Slackbones when the times comes...

So the 64bit community is following this methodology (if you dont mind the term).
While I cant speak for the 32bit devs, I dont think they have any major opposition to this... but then again I might be wrong. Hopefully they'll chime in.

I agree that a new version should have a new thread to keep everything so that everything is on topic. Older topics in theads that apply to the newer version can always be linked. If only you could symlink posts... sadly quoting and linking is the best we can do.

_________________



My PC is for sale
Back to top
View user's profile Send private message 
Flash
Official Dog Handler


Joined: 04 May 2005
Posts: 10930
Location: Arizona USA

PostPosted: Sat 02 Feb 2013, 21:14    Post subject:  

For what it's worth, people post bug reports all over the forum, sometimes with no indication of which version of Puppy they're talking about, and I have no way to move them to the appropriate thread, even if I know what that is. Confused
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 2044
Location: The Blue Marble

PostPosted: Sun 03 Feb 2013, 08:42    Post subject:  

Quote:
I have just started to use Puppy (FATDOG) as a VM Host. If the speed remains as fast as it is (i'm currently running 5 different Puppy distros in this implementation), should I notice a problem and want to report ...
Sorry for being off-topic. This is interesting, do you have any screenshots of 5 Puppy VMs running under Fatdog? Would be a good advertisement for Fatdog Smile
_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13
Back to top
View user's profile Send private message 
Monsie


Joined: 01 Dec 2011
Posts: 633
Location: Kamloops BC Canada

PostPosted: Mon 04 Feb 2013, 04:28    Post subject: Issue that would arise in problem reporting for PRECISE ISOs  

Quote:
gcmartin wrote:
Idea

This indirectly addresses a simple way for users to "see" which distro that they are using and should be reporting, should they exercise some measure of accuracy. HARDINFO that Kirk introduced 2-3 years ago, where it identifies on its 1st 2 pages the specific distro that is running in the system. This makes it simple and easy for development to ask the user which disto he has and almost make it fool-proof for him to report the distro which is running. I'm not sure what effort was involved to provide this level of detail, then or now, but, suffice it to say, it useful for ID purposes.


This is a good idea, but unfortunately HardInfo does not report this information in all Puppy breeds... for example: in Wary Puppy, the operating system is reported as Unknown distribution. Since others have mentioned this in the past, I've assumed (perhaps incorrectly) that it is a bug in HardInfo but maybe the bug is specific to certain Puppies.

An alternative might be to use Lighthouse sys-info --assuming that it is in all Puppies. It works for me anyway.

Monsie

_________________
My username is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.
Back to top
View user's profile Send private message 
drblock2

Joined: 19 Jan 2009
Posts: 137

PostPosted: Fri 08 Feb 2013, 09:14    Post subject: Distro Information  

Try this:

Code:
#!/bin/sh

# Get puppy version and kernel

cat /etc/DISTRO_SPECS | grep  DISTRO_NAME
cat /etc/DISTRO_SPECS | grep  DISTRO_VERSION
cat /etc/DISTRO_SPECS | grep  DISTRO_KERNEL_PET


Kernel information included as some Puppies are issued with more than one kernel to accommodate both older and newer machines.
Back to top
View user's profile Send private message 
gcmartin

Joined: 14 Oct 2005
Posts: 4088
Location: Earth

PostPosted: Tue 05 Mar 2013, 02:12    Post subject: This version of Hardinfo shows which PUP is running on PC  

Puppy member @Rodin.S published an upgrade to Hardinfo for 32bit PUPs, last week 2013-02-23

That Hardinfo versions shows which PUP is running in the "top 2 pages" of the on-screen report.

Here to help.

_________________
Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engine or use DogPile
Back to top
View user's profile Send private message 
Monsie


Joined: 01 Dec 2011
Posts: 633
Location: Kamloops BC Canada

PostPosted: Tue 05 Mar 2013, 03:44    Post subject: Issue that would arise in problem reporting for PRECISE ISOs  

gcmartin,

Update:

I am currently running and testing Wary 5.5 and I note that HardInfo now correctly identifies the Operating System "OOTB". I am assuming that this works for Racy 5.5 also.

Monsie

_________________
My username is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.
Back to top
View user's profile Send private message 
gcmartin

Joined: 14 Oct 2005
Posts: 4088
Location: Earth

PostPosted: Tue 05 Mar 2013, 22:12    Post subject:  

Slacko V5.5 ihas also using a much current version, as well. Official versions are showing up with HARDINFO improvements. Thanks goes to @Rodin.S for recognizing community benefit and helping. As well as to the developers who make this happen within distros.
_________________
Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engine or use DogPile
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [10 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware
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.0862s ][ Queries: 13 (0.0089s) ][ GZIP on ]