Nostalgia: kde porteus 3.1 next to perfection

[francois]

Just a thought fleeing thru my mind: kde porteus 3.1 is so perfect for my needs. What could I ask more?

Thanks fanthom.

[kalo86]

You are right! Pity for me that I cannot make boot properly Porteus v3.1 on my new machine with an integrated Intel HD graphics 520.... Otherwise it could be amazing...

[francois]

@kalo:
I am still interested to learn to build a modified kernel. Maybe we should both work on it. See the search for thread on building a kernel that I have done a few months ago:
viewtopic.php?f=114&t=5047

We could try it each on our side. Maybe you can boot porteus 3.1 from virtualbox to build your more recent kernel.

[kalo86]

Hi francois,

Years ago I enjoyed to compile new kernels from zero by following the guide on the Porteus web site.
Then I remember that brokenman has a particular script which needs to be executed from the compiled kernel folder to obtain the kernel headers (not a must but if you want to play with modified/patched wifi drivers you need to have kernel heards, maybe you just know it).
The procedure is simple, I think it can be done easily since I managed to run Porteus v3.1 x86_64 in text mode (I cannot boot in graphical mode because the issue in inside the xorg module).

A question: why do you need to compile a new kernel? There is a tool from user neko that updates the vmlinuz, initrd.xz and 000-kernel.xzm module in a simply way.
With a new kernel I did not solve the boot issues, but at least I can start Porteus in text mode.
Regards,

kalo86

[francois]

I just forgot about building a kernel for now.

[kalo86]

Me too, don't worry! :-)

[francois]

It was just to understand how one can build a kernel, to get to know a little more about what is going on under the hood, see:
viewtopic.php?t=5047

I thought that using the porteus kernel with archlinux would result that most of the drivers running under porteus would just simply work under arch linux. I tried to do that under vbox to have a simpler working environment facilitating rebooting of the machine (vbox).

[Bogomips]

^ It's not overly complicated, in fact seems less daunting than setting up a makefile. Just a little bit fiddly, that's all. So for your normal run of the mill kernel, last time I made one, the sources need to be downloaded, then pay special attention to the README. Finally the config procedure leads you through all that you want and don't want in the kernel, after which you just have to sit back and wait while it compiles. Last thing to do is to check all the output. 8)

[francois]

I understand that there is no trauma to do so. As this seem to be part of your building blocks thread, I hope to find time to do it.

[Bogomips]

I understand that there is no trauma to do so. As this seem to be part of your building blocks thread, I hope to find time to do it.

It would certainly help both of us for starters if you could see if you could compile the aufs standalone module for kernel 4.1.15. All responses please to my thread, as we do not want to be seen to be going off topic, having to be showing an example.

[Jack]

Just a thought fleeing thru my mind: kde porteus 3.1 is so perfect for my needs. What could I ask more?

Thanks fanthom.

I feel the way with 3.1 Mate. It might be on my thumb drive for a long time. One thing I did do is make a copy of my change directory for a backup. And thanks to the Portues team for it.

[Vic]

I was reluctant to commit to full time use of anything other than Windows. Porteus 3.1 KDE changed that. I love how Porteus "just works" , but I love more how it is so flexible with my limited knowledge. With a little searching, I am able to solve any problem (challenge) and have more fun than I ever had with Windows. Thanks to everyone for the FUN!

Vic