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 Wed 04 May 2016, 04:09
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
What do these commands supercede so I can edit the source?
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [4 Posts]  
Author Message
musher0


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

PostPosted: Thu 28 Jan 2016, 20:15    Post subject:  What do these commands supercede so I can edit the source?
Subject description: Having to type pdev1=sr0 pupsfs=sr0:/puppy.sfs, etc. for this cd to boot properly
 

Hello all.

As the title says.

As some of you may know a few contributors and I are working on an update
of a Wheezy Pooch loosely derived from a Woof-CE run.

(Long story short: I decided in favor of a very detailed remaster -- with numerous
diff -rq and diff -y checks along the way [not your usual run-of-the-mill bulk-type
remaster] -- because I found the regular woof process to behave quite like "teflon"
regarding the apps that I wanted to include and the upgrades that I wanted to make.
[My opinion only.])


Back on topîc:
A couple of days ago, I created a remaster incorporating the recent findings of jlst and
myself, and burned the iso to DVD.

Now when the DVD launches if I just type < Enter >, the puppy can't find itself
("puppy.sfs not found").

However if I type the full complement of prompt commands, such as
Code:
pdev1=sr0 pupsfs=sr0:/puppy.sfs zdrv=sr0:/zdrv.sfs pmedia=cd pfix=ram
it does find itself and finally boots into the desktop from DVD.

This needs to be addressed, because you can't ask a newbie to type in all that data to
boot a Puppy. If you do, (s)he'll choose on the spot a less difficult distro. So...

~~~~~~~~~~~~~
Tentative explanations (probably wrong, otherwise I wouldn't be asking for help!):

Fact:
As I understand it, those prompt commands take precedence over commands or data
that Puppy fetches within itself to boot properly.

Which means:
if I find and correct those initial commands in one or many files somewhere in the
Puppy, the prompt commands will not be needed, right?

~~~~~~~~~~~~~~
I must add that this experimental Pup is rather in a mongrel state right now, in-between
the Wheezy 3.5.2.9 (very stable, by our friend pemasu) and one Pup with a new kernel
3.12.3. (the goal), part of which has been produced by the Woof process.
~~~~~~~~~~~~~~

Tentative Explanation #1:
The version number produced by the Woof process wasn't consistent between the
kernel and the pup, and I tried to make it consistent "across the board". Maybe this
mongrel likes being a mongrel, he doesn't want uniform version numbers? Smile

I know there are some version numbers in the DISTROSPECS files. one of which is in
/etc and the one in /initrd.

Anywhere else?

~~~~~~~~~~~~~~
Tentative Explanation #2:
At the crash described above, you're in pure init. But there's a text file there, Barry being
always considerate (!), explaining that the "part number" has also been appended to
vmlinuz and initrd.

(Please hear the semi-Ironical tone in this next paragraph...)
We love you, Barry. A crash is a really great time to tell us that you've branded the
Puppies... (if that's what it is). Smile

So I open up vmlinuz and initrd, invent a consistent part number to use across the entire
Puppy and replace the one that's there if I can find it?
~~~~~~~~~~

Tentative Explanation #3:
None of the above. Wink

~~~~~~~~~~~~~~
Many thanks in advance for any pointers.

_________________
musher0
~~~~~~~~~~
"The greatest of minds are the ones that never close." | "Les plus grands esprits sont ceux qui ne se ferment jamais."
(starhawk, Resident Philosopher | philosophe en résidence) Wink

Last edited by musher0 on Thu 28 Jan 2016, 23:41; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
jlst

Joined: 23 Nov 2012
Posts: 205

PostPosted: Thu 28 Jan 2016, 21:44    Post subject:  

Your really don't need pdev1= etc to boot correctly from CD/DVD, just pmedia=cd and that line is already present in the bootloader configuration by default, syslinux or something like that, nowadays I only use grub4dos,I have a working template for cds/dvds that can be added to woof as an alternative to make a puppy ISO, it looks very nice and elegant - navy blue

It looks like you have fairly broken ISO, maybe you should rebuild it? It's a good puppy to test scripts like the one we're testing though
Back to top
View user's profile Send private message 
musher0


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

PostPosted: Thu 28 Jan 2016, 23:36    Post subject:  

Hello jlst.

You wrote:
jlst wrote:
Your really don't need pdev1= etc to boot correctly from CD/DVD, just pmedia=cd and that line is already present in the bootloader configuration by default, syslinux or something like that, nowadays I only use grub4dos,I have a working template for cds/dvds that can be added to woof as an alternative to make a puppy ISO, it looks very nice and elegant - navy blue

It looks like you have fairly broken ISO, maybe you should rebuild it? It's a good puppy to test scripts like the one we're testing though

You feel that grub4dos is a better loader? If you'd like to share your template, I'll
try it and see. I say "try" because the launch commands will be the same. I don't
think the bug has to do with the loader.

We can't stay forever on these bugs.

Thanks in advance.

~~~~~~~~~~
I don't think the ISO file per se is broken. It boots ok with the additional commands
-- provided there are no files with the same name on any partition at top level and
1st sub-dir. --

~~~~~~~~~~
If you mean that the puppy.sfs would be broken, that's nothing compared to when
I started! Twisted Evil

I have the impression that the Wheezy template was left unmaintained since pemasu
left and that maybe someone else introduced changes later without testing.

Neglect, I'm sure; sabotage, I'm not sure, and it would be too big an accusation.

~~~~~~~~~~
For example, there was an xbindkey setting Alt-Ctrl-Backup that sent the Pup in
some sort of neverland hibernation, not back to the initial black console. Took me
awhile to catch that one. (Not the real hibernation, I tested it on my portable and I
couldn't come out of it.)

That's why I say some of the woof template was simply imported by who knows
who and not tested. An experienced Puppyist would have caught that one easily.

So I chucked that xbindkey config. There's now just the default, non offensive, one.
The user who wants to use xbindkey will have to spend some efforts rebuilding the
xbindkey config keeping in mind the usual Puppy key combos.

~~~~~~~~~~
I'm using the diff -rq and/or diff -y a lot on the originating and the "squashfs-ready"
directories to make sure the "squash-ready" dir. has all the edits.

Also I use cp -dpRf between directories, not just cp -a, being careful to copy from
the add-ons/edits directory to the template directory, but semi-final and final visual
checks are always necessary.

Somehow the copy has altered the busybox utility a couple of times even if busybox
is not in the edits dir. Why, I don't know, but I've learned my lesson. If busybox is
altered, at boot the kernel sends a "busybox tainted" message and booting halts.

Also the real less never gets copied over the busybox less link, so those have to be
done manually. A couple of other things: like edited files in the
/root/Choices/ROX-Filer directory need to be copied manually.

I get the feeling any "Puppy system" file has the teflon bug, meaning: automated
copy of any kind doesn't stick on those files.

Fun, fun, fun with the teflon Puppy! (Hearing my ironical tone?) Smile
It's better to laugh than cry, right?

Bye for now.

_________________
musher0
~~~~~~~~~~
"The greatest of minds are the ones that never close." | "Les plus grands esprits sont ceux qui ne se ferment jamais."
(starhawk, Resident Philosopher | philosophe en résidence) Wink
Back to top
View user's profile Send private message Visit poster's website 
musher0


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

PostPosted: Tue 02 Feb 2016, 22:25    Post subject:  

Hello all.

The problem is partly solved. It had to do with the various copies of DISTRO_SPECS
not jiving. Please see here.

BFN.

_________________
musher0
~~~~~~~~~~
"The greatest of minds are the ones that never close." | "Les plus grands esprits sont ceux qui ne se ferment jamais."
(starhawk, Resident Philosopher | philosophe en résidence) Wink
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 1 [4 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Bugs ( Submit bugs )
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.0449s ][ Queries: 11 (0.0029s) ][ GZIP on ]