Porteus

@ Rava Before you ask... ;) Nvidia 304.137 kernel 4.16.2-x86_64 ( porteus-4.0-x86_64-20180415.iso ) http://filehorst.de/d/cfFmfifj as usual.. The File is on a german hosting service so please do as follows to get it. Wait 15 sec > click "Jetzt zur Download-Seite" (means go to download page) > click ...

Rava wrote: ↑

08 Apr 2018, 08:08

I presume cd-diskid is part of Porteus?

Nope, but cd-discid is available from slackonly via USM (~ 16 kB)

To get the (CD) disc-id one can use cd-discid
The output of cd-discid:
8HexDigitID NumberOfTracks Track1StartFrame Track2StartFrame..TrackNStartFrame DiscLengthInSeconds
you need only the 8HexDigitID to query it at
http://www.freedb.org/freedb_discid_check.php

On my system, sudo asks for the guest password
echo guest (or whatever the current password is)

success - patched - compiled - is running... :Yahoo!: https://s9.postimg.org/cp57jdqan/Screenshot.jpg ....but i am too tired at the moment to prepare/upload a module..maybe tomorrow - stay tuned EDIT here we go.. -- nvidia-304.137-kernel-4.15.10-x86_64-don.xzm -- ( built without the 32 bit librarie...

As I said in the first post. > I had it running in porteus 3.2.2 (kernel 4.9) - XFCE,KDE and LXDE < ;) I can compile the 304.137 driver up to kernel 4.14.4 using a patched *.run file. Unfortunately I have not found any patches for newer kernels until now. Kernel 4.14.4 is used in these complete isos...

gotPortee wrote: ↑

26 Mar 2018, 19:11

I wonder if this may also be available in 32?

sure..
http://filehorst.de/d/cCCeBIwE
Same download procedure as described above.
Have fun..

i voted for 24hr
imo, In most countries the 24-hour clock is the standard system used, especially in writing.
Outside of English-speaking countries, the terms a.m. and p.m. are seldom used and often unknown.

Give the user the choice to change it, that way, everybody is happy..

The packages should be available via USM, use usm -s exfat Otherwise go http://packages.slackonly.com/pub/packages/14.2-x86_64/ , download and convert to xzm PACKAGE NAME: exfat-utils-1.2.7-x86_64-1_slonly.txz PACKAGE LOCATION: ./system/exfat-utils PACKAGE NAME: fuse-exfat-1.2.7-x86_64-1_slonly.txz ...

@ n0ctilucient Hmmm...I thought you were going to build a module as you wrote in the 1st post Now... make the module and add it to your Porteus loadout. add it to the iso and burn a CD (or whatever) Otherwise you could surely extract the original modules, search for the files, replace them and rebui...

@ ncmprhnsbl
Aha!, good to know, thanks.

EDIT ...learned something today...thanks! ncmprhnsbl :good: So the simplest way to achieve the goal would be to create a module containing /etc/rc.d/rc.FireWall, make rc.FireWall executable and edit the ALLOWED_PORTS line. Example: Firewall "normal" would be ALLOWED_PORTS="20 21 22 25 80 110 143 44...

You do only need a modified rc.local file to start the firewall. #!/bin/sh # # /etc/rc.d/rc.local: Local system initialization script. # # Put any local startup commands in here. Also, if you have # anything that needs to be run at shutdown time you can # make an /etc/rc.d/rc.local_shutdown script a...

(While booted into Porteus) copy /etc/rc.d/ lrc.local Ok, this might be a typo.. But then With a text editor open /etc/rc.d/rc.local and remove the 1st comment (#) and add -e to the end of the line. What..?? you mean the first line should be !/bin/sh -e ?? Looks to me like a messed up shebang line....

@jssouza

I think we're both capable of imagining scenarios,
advanced and/or complicated setups where it would make sense
doing it this way, the other way around, or totally different.