Porteus

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...

The v4.11.7/v4.9.34 version "crippled_sources" module can be gotten without compiling.

--------------------------------------------------------------------------------
@fulalas
(1) "crippled_sources" module size was reduced by your script.
This module can be gotten by yourself compiling kernel or by sample module.
For example, by downloading v4.11.7.tar.xz and crippled_sources-4.11.7-64bit.xzm,
you can update kernel and crippled_sources to 64Bit version 4.11.7.

"crippled_sources" module is not included in sample vN.NN.N.tar.xz.
32Bit and 64Bit "crippled_sources" modules are too big
to be included in sample vN.NN.N.tar.xz for none-need users.

(2) pending items
"copy to install directory":
I have to consider for user who doesn't use install directory.

"Build a VirtualBox based on the built kernel":
I think that it beyonds the category of "Kernel Builder" and is in the category of Package management.

--------------------------------------------------------------------------------
@beny
I too would like to study "Dynamic Kernel Module Support (DKMS)" but my power is poor.
I am sorry.

--------------------------------------------------------------------------------
@brokenman
Thank you for your suggestion.
(1) "An automatic kernel updater"
I am waiting for your output.
I have to study more thing from you.

(2) "linuxrc"
"linuxrc" that is used in APorteus,
shell script has been rewritten
and executable entities has been replaced with 32Bit Arch ones.
It can be used for Porteus 3.2, for Nemesis, and for APorteus, depending on spec file.

(3) "module update for the case of the Porteus install"
If I will offer something concerning it, I have to research it.

(4) "deepin"
It has been included in "APorteus ISO Builder" on hidden mode.
I hesitate to progress more for the "back door" suspicion (from Evan information).

--------------------------------------------------------------------------------
@Evan
Thank you for your warning.
Now I hesitate to use DEEPIN.

Ed_P wrote:neko that is an unfounded speculation rather than a proven fact. Do not let it cloud your testing.

So the unfounded speculation that SystemD has a backdoor because it's approved by the NSA is to be avoided and people get their panties in a twist all over it but if people speculate that Chinese software can no longer be trusted because of the new law that states a back door needs to be added then it's just speculation that needs to be a proven fact as somehow the Chinese Government is more trustworthy for making it a public law rather than secret exploiting by the NSA?

I despair at the dumb-ass , back to front and hamfisted logic and reasoning on here at times.

I think that any field has something risk.
And almost risks aren't known which its risk is real or not.

A some package will harm to system under a some case.
If it has a very interest function for somebody,
it is not a problem for him who understands its risk to use it.
But using it is a problem for him who doesn't know its suspected risky at all.

On DEEPIN (and WPS Office), I have hidden it. (didn't delete)
It can be used with a little effort ("how to" is easy and opened.)
This effort will make users aware of the problem.
The latter can used it with the aware.
Of course, the former can also use it.

Thanks.

PS.
I am not native English speaker.
And I have a poor English skill only. (using Google translator)
I am afraid that my real thinking is accepted by you or not.

The kernel of Porteus ISO can be update to version v4.11.8/v4.9.35/v4.4.75/v4.1.42/v3.18.59 without compiling.
And the v4.11.8/v4.9.35/v4.4.75/v4.1.42/v3.18.59 version "crippled_sources" module can be gotten without compiling.

The kernel of Porteus ISO can be update to version v4.11.9/v4.9.36/v4.4.76/v3.18.60 without compiling.
And the v4.11.9/v4.9.36/v4.4.76/v3.18.60 version "crippled_sources" module can be gotten without compiling.

Note:
Kernel version 4.11 line AUFS patch was updated to "aufs4.11.7+".
This update has been already included in "mkKernel-17.07.03-noarch-1.xzm".

We upgrade Kernel, so that the gadget we have works. I have a Mediatek USB WiFi dongle MT7601u.

Linux mac80211-based driver for Mediatek MT7601U USB bgn WiFi dongle

This is a Linux driver for MediaTek MT7601U USB dongle. It was written from scratch based on the vendor GPL-driver. Unlike the vendor driver this driver uses modern Linux WiFi infrastructure and should work flawlessly with NetworkManager, wicd, wpa_supplicant and such. This driver was merged into mainline and is part of official Linux kernel since version v4.2.If you are using Linux 4.2 or later there is no need to install this driver.

The dongle works in v4.12. But from Kernel versions 4.7 onwards, many computers including mine don't power off or reboot,but get stuck in "unmounting all". Only solution is manually press 'power' switch. Linux will warn next time that certain device are not unmounted properly and asks you to file check. This has been reported widely, but subsequent Kernels have not rectified.

With, v4.4.75, my PC boots and shutsdown as intended. But, the VMLINUZ offered by you is not having support for Mediatek mt7601 as the config lines are not enabled.

In v4.12 conf file,

ine 2245 CONFIG_WLAN_VENDOR_MEDIATEK=y
line 2246 CONFIG_MT7601U=m

are there, but

In v4.4.75

line no 2087 CONFIG_WL_MEDIATEK is not set.

My dev set up in a running m/c is not perfect. Can you please make a new vmlinuz v4.4.75 by adding support for this dongle, may be,

@raja
Thank you very much for your pointing an issue up.
I have re-built version 4.4.76 kernel
with the new config that has "CONFIG_WL_MEDIATEK=y" and "CONFIG_MT7601U=m"
If you have a time, please confirm it.