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 18 Jul 2018, 20:25
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
kernel compiling in woof-ce
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 35 of 36 [527 Posts]   Goto page: Previous 1, 2, 3, ..., 33, 34, 35, 36 Next
Author Message
rockedge


Joined: 11 Apr 2012
Posts: 625
Location: Connecticut, United States

PostPosted: Mon 04 Jun 2018, 19:11    Post subject:  

I have compiled a 4.17 pae enabled kernel but I had to use the aufs=4.16 as the kernel-kit script could not find a version for 4.17

I am about to test it out with a 32bit Bionic build from woof-CE..just waiting for the ISO to finish writing...
Back to top
View user's profile Send private message Visit poster's website 
peebee


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

PostPosted: Tue 05 Jun 2018, 04:25    Post subject:  

rockedge wrote:
I have compiled a 4.17 pae enabled kernel but I had to use the aufs=4.16 as the kernel-kit script could not find a version for 4.17

I am about to test it out with a 32bit Bionic build from woof-CE..just waiting for the ISO to finish writing...

With a new kernel version it is usually best to use the 4.x-rcN aufs branch until the specific branch for the new kernel becomes available.....I've done a 64-bit kernel-kit build in that way.

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
smokey01


Joined: 30 Dec 2006
Posts: 2740
Location: South Australia

PostPosted: Tue 05 Jun 2018, 06:28    Post subject:  

rockedge wrote:
I have compiled a 4.17 pae enabled kernel but I had to use the aufs=4.16 as the kernel-kit script could not find a version for 4.17

I am about to test it out with a 32bit Bionic build from woof-CE..just waiting for the ISO to finish writing...


I discovered the same problem and did the same as you.

Maybe next time I will try peebee's suggestion and use the 4.x-rcN aufs branch.

_________________
Software <-> Distros <-> Tips <-> Newsletters
Back to top
View user's profile Send private message Visit poster's website 
rockedge


Joined: 11 Apr 2012
Posts: 625
Location: Connecticut, United States

PostPosted: Wed 06 Jun 2018, 01:21    Post subject:  

I will also try a version with peebee's suggestion...meanwhile I have the finished pup running the 4.17 kernel
bb1805k417.png
 Description   
 Filesize   55.65 KB
 Viewed   411 Time(s)

bb1805k417.png

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


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

PostPosted: Sun 10 Jun 2018, 18:13    Post subject:  

Now available:
https://github.com/sfjro/aufs4-standalone/tree/aufs4.17

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
rockedge


Joined: 11 Apr 2012
Posts: 625
Location: Connecticut, United States

PostPosted: Sun 10 Jun 2018, 22:18    Post subject:  

thanks peebee....I am compiling a kernel 4.17 in 2 slightly different versions as I type using this aufs
Back to top
View user's profile Send private message Visit poster's website 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1528

PostPosted: Tue 12 Jun 2018, 15:11    Post subject:  

stemsee wrote:
This kernel package contains 4.16.13 - x86_64 sources and huge
Based on easy config.
https://drive.google.com/drive/folders/1QtlfCnP0Dc8ndQkvcu2ZHRAP9-sQ1Wre

I tried compiling 4.14.49 in slacko64 with the easy config too and it's working. Thanks for the tip Wink

https://www.mediafire.com/folder/6y6wboz3u0ik3/x86_64#kwx434mu7g3yk
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2256
Location: In The Way

PostPosted: Tue 12 Jun 2018, 17:18    Post subject:  

Welcome Sailor Enceladus

I added some code to use the next aufs version down if latest not found ... so for 4.17 it will try 4.16 automatically.

Also with single . kernels 4.16 or 4.17 the kernel gets expanded to 4.17.0, got that sorted.

I also found two typos in the nubuild.sh script from my latest sukk download.

I compiled 4.17 and 4.17.1 no probs.
Back to top
View user's profile Send private message MSN Messenger 
mikeslr


Joined: 16 Jun 2008
Posts: 2473
Location: 500 seconds from Sol

PostPosted: Tue 12 Jun 2018, 18:44    Post subject:  

Hi All,

peebee wrote:
Now available:
https://github.com/sfjro/aufs4-standalone/tree/aufs4.17


As someone who has put to use several of the kernel packages (vmlinuz & associated modules/drivers) but has limited knowledge of what's actually involved, it had been my impression that in compiling a kernel for use with Puppies, aufs was necessarily incorporated into the vmlinuz as part of the compile process initiated by the script. Of course, I may have gotten the foregoing assumption partly or entirely wrong.

Inherently, a more modular approach might be advantageous: an independent aufs --easier to compile and test-- which might be usable with (in?) other than one puppy vmlinuz, perhaps enabling the use of kernels published by Linux.org without having to 'start from scratch'. Does any of the foregoing make sense? And is that what peebee has done?

If so, could the aufs be used like other sfses --zdrv.sfs, fdrv.sfs-- or is the aufs still an intermediate component later to be combined into the vmlinuz?

mikesLr
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2256
Location: In The Way

PostPosted: Tue 12 Jun 2018, 19:05    Post subject:  

The kernel sources are patched with patches from aufs sources. Then the kernel source is compiled with aufs capability. Aufs can be built as modules, but for most puppes it is built into the kernel at compile time, for booting purposes loading and layering the main.sfs and kernel-modules.sfs before performing a switchroot into the mounted layered filesystem. The aufs-utils are built from source and added to the kernel-modules.sfs.

Peebee has built the latest kernel 4.17, for which the aufs sources on github did not yet have a branch for. They are maintained by a Japanese person. Aufs has not been accepted into the mainline kernel by Torvalds (linux kernel king), but overlayfs has been accepted.

So Peebee compiled the 4.17 kernel using the aufs.x-rcN branch; while others used the 4.16 branch with the 4.17 kernel as there is not too much difference.

Using modules compiled with one kernel on another kernel is usually problematic, though there is some limited portability, but usually doesn't work!
Back to top
View user's profile Send private message MSN Messenger 
peebee


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

PostPosted: Wed 13 Jun 2018, 01:54    Post subject:  

Adding to stemsee's excellent explanation....

@gyro has a project which is progressing very successfully to replace aufs with overlayfs - http://www.murga-linux.com/puppy/viewtopic.php?t=110636 - as a fallback if the Japanese guy "Junjiro. R. Okajima" ever stops developing aufs - my kernels (and others) have overlayfs configured so they can be used with @gyro's experiments.....

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
stemsee

Joined: 27 Jun 2013
Posts: 2256
Location: In The Way

PostPosted: Sat 16 Jun 2018, 04:40    Post subject:  

I have been testing this on BionicDog, the devx of which is empty in terms of kernel compiling deps, luckily the script installs fakeroot, kernel-package, headers, etc but, unlike previous debiandog, does not compile as make-kpkg not found!

Well, a few fixes in place but more to do! Good for building single package at a time.
nubuild.sh.gz
Description  nubuild script
gz

 Download 
Filename  nubuild.sh.gz 
Filesize  21.26 KB 
Downloaded  28 Time(s) 
Back to top
View user's profile Send private message MSN Messenger 
Dry Falls

Joined: 16 Dec 2014
Posts: 564
Location: Upper Columbia

PostPosted: Wed 20 Jun 2018, 04:14    Post subject:  

Quote:
does not compile as make-kpkg not found!

These newer scripts put the kernel headers in the kernel sources module. I miss having it in the kernel modules sfs. Put it there manually. Probably a good idea NOT to put it in devx, but why doesn't woofCE place it in the zdrive?

This new script continues with some errors (mostly typos) from the previous, although both work. Here are some changes I made you might be interested. Removed "carriage returns" (unwrapped lines) and fixed some tar options. Also removed a hyphen so that md5sum works on huge package. One tar still returns an error message during the aufs build:
Quote:
Creating the Aufs sources tarball
tar: Cowardly refusing to create an empty archive
Try 'tar --help' or 'tar --usage' for more information.
Extracting the Aufs sources
and later
Quote:
Failed to patch the aufs-util sources.
tar: ../aufs-util: Cannot open: Is a directory
tar: Error is not recoverable: exiting now
aufs-util is in dist
diffing.txt.gz
Description  real gz. click to unzip
gz

 Download 
Filename  diffing.txt.gz 
Filesize  702 Bytes 
Downloaded  21 Time(s) 
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2256
Location: In The Way

PostPosted: Wed 20 Jun 2018, 10:01    Post subject:  

I will check out your scipt Dry Falls. The headers are supposed to go in the devx! I opted for the kernel-modules.sfs, against 01micko's advice, having no automatic way to put them in any given devx (wherever it resides on the hdd). So this time, I put them in the sources.sfs, in error, mixing up sources for devx!

Jamesbond had clarified that there are two types of header files, one of which is for development, those that are in the package with kernel sources. Probably should build their own headers.sfs package.
Back to top
View user's profile Send private message MSN Messenger 
Dry Falls

Joined: 16 Dec 2014
Posts: 564
Location: Upper Columbia

PostPosted: Mon 25 Jun 2018, 14:30    Post subject:  

stemsee wrote:
The headers are supposed to go in the devx! I opted for the kernel-modules.sfs, against 01micko's advice, having no automatic way to put them in any given devx
My opinion: you were right in the first place. If in the zdrive or initrd, they take precedence during bootup (>switchroot) so you've got the right modules loaded no matter what is in the devx which loads later. (As you've discovered, you can use the devx from another distro to access some programs). If they are located in the devx, you will have to remaster that file for every kernel change. If they are in the kernel sources sfs, you will have to load it with the devx every time you want to compile. We're only talking 1 megabite (compressed) so there isn't really a "keep the size down" argument available. It's not just an issue of remastering the devx but eliminating all that bandwidth usage uploading the devx over and over for every kernel change. I appreciate that speculations on bandwidth/cloud usage are the only thing keeping wall street afloat (and therefore, the general economy), but that's their problem, not mine. When you think about it, all so-called security issues boil down to moving money. It's for the greater good (but never mine!)

df
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 35 of 36 [527 Posts]   Goto page: Previous 1, 2, 3, ..., 33, 34, 35, 36 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
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.0570s ][ Queries: 12 (0.0052s) ][ GZIP on ]