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, 23:17
All times are UTC - 4
 Forum index » House Training » Beginners Help ( Start Here)
boot parmaters, case wrong on wiki?
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [2 Posts]  
Author Message
s243a

Joined: 02 Sep 2014
Posts: 2073

PostPosted: Mon 08 Jan 2018, 02:58    Post subject:  boot parmaters, case wrong on wiki?  

I think the case is wrong on the boot parmaters given in the puppylinux wiki:

Snapshot 07 Jan 2018
http://puppylinux.org/wikka/BootParametersPuppy?time=2015-11-09+08%3A17%3A03

Many of the headings show mixed case but if we look at the example on the top part of the wiki article psubdir is in lower case even though the heading below shows it as mixed case.

I think that this works as follows. The boot process simply exports the paramaters given to either the kernal or initrd to lower subprocesses.

Then in /initrd/init these boot parmaters are mapped to equivalent variables in the /initrd/init script.

Lines 836 to 862 are shown below of initrd/init for tahrpup:
Code:

#pmedia= usbflash|usbhd|usbcd|ataflash|atahd|atacd|atazip|scsihd|scsicd|cd
[ $pmedia ] && PMEDIA=$pmedia #boot parameter, broad category of boot media. ex: cd.
[ $psubdir ] && PSUBDIR=$psubdir #boot parameter, directory for puppy files. ex: puppy220
[ $psavemark ] && PSAVEMARK=$psavemark #100913 partition number that has/will-have save-file.

[ $PSUBDIR ] && [ "${PSUBDIR:0:1}" != "/" ] && PSUBDIR="/${PSUBDIR}" #add leading /.

[ $pdev1 ] && PDRV=$pdev1 #boot parameter, partition have booted off. ex: hda3
#100915 requested by technosaurus (formats get changed further down)...
[ $pdrv ] && PDRV=$pdrv #format partition:<path><filename> ex: sda2:/slacko/puppy_slacko_6.3.0.sfs
[ $pupsfs ] && PDRV=$pupsfs
[ $zdrv ] && ZDRV=$zdrv #ex: sda2:/slacko/zdrv_slacko_6.3.0.sfs
[ $fdrv ] && FDRV=$fdrv
[ $adrv ] && ADRV=$adrv
[ $ydrv ] && YDRV=$ydrv
#<partition>:<filename>, for savefile/savefolder. <partition> can be a name or Label or UUID
[ $psave ] && PSAVE=$psave #ex: sdb4:/puppy/tahr/tahrsave or smark or 49baa82d-8c69:tahrsave
#list of kernel modules to load, ex: pimod=hid-logitech-dj.ko,kernel/drivers/hid/hid-multitouch.ko
[ $pimod ] && PIMOD=$pimod
#specify partition for Underdog Linux (refer also underdog.lnx).
[ $underdog ] && UNDERDOG=$underdog
#[ $pdebug ] && PDEBUG=$pdebug
PDEBUG=1
TOTAL_SIZEK_SFS_RAM=0

# show menu with pupsaves
[ $psavemenu ] && PSAVEMENU=$psavemenu


Notice that on the right of each statement all the variables are lower case.

Another error that I believe is in the wiki is that it says

Quote:

Psubdir
Specifies ({device}{type}/path) the location of boot files in the boot partition. If not specified init will look in / and /boot, order-unknown. As of puppy 3.00 this parameter also restricts the boot search for pup_save files: only those in a matching directory will used. This can be used to allow multiple-puppy installation on the same partition to be used without risk of using the wrong one in error. Also see Psubok.
Example- psubdir=boot/puppy216


but if I look at the code above I don't see any reference to the device for the psubdir boot parmater. There is a separate parameter for the device called pdrv.

I was looking at this code because tahrpup couldn't find the save folder on my external hard drive "sdd4" even though this is the drive that grub booted off. I know this because I can see that it is still mounted when the desktop first apears but shortly after it is unmounted automatically.

There is a paramater called pdev1 that is supposed to give the device that puppylinux booted off and assign it to pdev. However, this parameter does not seem to be being passed the the init script. At least it doesn't apear that way in my case. I wonder if this parmater varies depending on the bootloader that was used. I'm trying grub4dos but maybe this would be the correct parameter for syslinux.

Anyway if my assumptions are right and the article is not locked I can fix the wiki article. I need to verify first though before I make any changes.
Back to top
View user's profile Send private message Visit poster's website 
jafadmin

Joined: 19 Mar 2009
Posts: 908

PostPosted: Thu 11 Jan 2018, 08:00    Post subject:  

Yeah, those doc cases are misleading. The grub parameters sent in are all lower case, and that code assigns their values to init variables that are all upper case.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [2 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Beginners Help ( Start Here)
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.0322s ][ Queries: 11 (0.0067s) ][ GZIP on ]