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 28 Feb 2020, 08:25
All times are UTC - 4
 Forum index » House Training » HOWTO ( Solutions )
Porteus Boot for Puppies
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 2 [20 Posts]   Goto page: Previous 1, 2
Author Message
dancytron

Joined: 18 Jul 2012
Posts: 1479

PostPosted: Mon 13 Jan 2020, 20:22    Post subject:  

rcrsn51 wrote:
Interesting. When I messed around with Fred's mk-initrd script, my sense was that the resulting initrd1.xz was kernel-specific.

But yours is generic?


Is there something specific we can test to see if there is some conflict related to the kernel version?

I have it set up and working on radky's Buster Puppy.
Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1439
Location: Smithers, BC, Canada

PostPosted: Mon 13 Jan 2020, 22:35    Post subject: Not kernel specifc  

dancytron wrote:
rcrsn51 wrote:
Interesting. When I messed around with Fred's mk-initrd script, my sense was that the resulting initrd1.xz was kernel-specific.

But yours is generic?


Is there something specific we can test to see if there is some conflict related to the kernel version?

I have it set up and working on radky's Buster Puppy.
Not only is it not kernel specific it works for both 32bit and 64bit. I tried just before posting.
Back to top
View user's profile Send private message 
dancytron

Joined: 18 Jul 2012
Posts: 1479

PostPosted: Mon 13 Jan 2020, 23:27    Post subject: Re: Not kernel specifc  

jrb wrote:
dancytron wrote:
rcrsn51 wrote:
Interesting. When I messed around with Fred's mk-initrd script, my sense was that the resulting initrd1.xz was kernel-specific.

But yours is generic?


Is there something specific we can test to see if there is some conflict related to the kernel version?

I have it set up and working on radky's Buster Puppy.
Not only is it not kernel specific it works for both 32bit and 64bit. I tried just before posting.


Now that you mention it, Radky's Buster Puppy is 32bit.

I'll experiment a little more later and see how much of Fred's DD tools and management scripts work. Things that depend on dpkg and apt won't work, but the other stuff might.
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4289
Location: holland

PostPosted: Tue 14 Jan 2020, 04:26    Post subject:  

Hi jrb and everyone,

Nice initiative !
jrb wrote:
rcrsn51 wrote:
Interesting. When I messed around with Fred's mk-initrd script, my sense was that the resulting initrd1.xz was kernel-specific.

But yours is generic?
I've used several of Fred's initrd's on several different Puppies with several different kernels. They've all worked.

I didn't test yet, but I think that the reason is that the puppy kernels have so much builtin kernel modules (in vmlinuz)
EDIT: To be honest, I'm really not sure, it could be also because the initrd1.xz contains all required modules, e.g. aufs, squashfs)

Here's some info about construction of the porteus-boot scripts:
If you make such folder structure in "rootcopy" and put the scripts inside, it should work)
Scripts for save on EXIT:
/usr/bin/save2flash
/usr/bin/snapmergepuppy

Shutdown scripts: (will call above when EXIT is specified on kernel boot line) (depend on yad)
/usr/bin/wmpoweroff
/usr/bin/wmreboot

Init scripts (also for save on EXIT, but from console, depend on dialog)
/etc/init.d/snapexit
/usr/local/bin/snap-ex (or named earlier 'snap')

/usr/bin/makepfile.sh (savefile create)

Called from rc.local: (mostly for symlink creation in /live (but /live folder must exist then in the OS, if not, add empty "live" folder in "rootcopy"):
/usr/local/bin/mountlink

Fred

_________________
Dog Linux website
Tinylinux blog by wiak
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12976
Location: Stratford, Ontario

PostPosted: Tue 14 Jan 2020, 05:24    Post subject:  

So the initrd1.xz does indeed contain kernel-specific code? But if the target Puppy doesn't need the code, it will just ignore it?
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 2 [20 Posts]   Goto page: Previous 1, 2
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » HOWTO ( Solutions )
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.0474s ][ Queries: 13 (0.0153s) ][ GZIP on ]