Porteus

First the question, do you think a first run setup script is a good idea for porteus?
If so should it be run in console or kdialog? (requires booting to KDE)
Lastly what should be included in the setup. So far i have 'changes setup' and 'network setup'

I have almost finished writing one with the following features:

• It looks to see if running from non writeable media and skips setup.
  It dumps a marker file in boot folder which it looks for during startup. If found it skips setup.
  Autosensing of FAT partition after which it will use slaxsave.dat file to save changes and ask what size you prefer

Hi. This theme about changes on MS patriotion?

Hi. This theme about changes on MS patriotion?

It looks at partition porteus is running from. If FAT32 it suggests changes be saved in container file (slaxsave.dat) and does the decompressing and setting up of changes.

How about checking to see if the speakers are muted in alsamixer, and unmuting them if they are?

Thanks. Will do this.

kdialog is good looking and functional but i would vote for console as more universal solution. LXDE users are growing in strength and we should also think about other desktops like XFCE.

of course , if will be kdialog => that's mean ignore lxde users.
console is good, but how about xdialog for both kde and lxde !!

I do not think this script will be important .
but this script should not work if we run Porteus LiveCD or Copy2Ram, this script should work after installed Porteus on HardDisk.

# this script can help in:
* chose layout language, and which buttons 'alt+shift' .
* connect network, LAN or WLAN.
* time zone and date.
* ...etc

fanthom wrote:kdialog is good looking and functional but i would vote for console as more universal solution. LXDE users are growing in strength and we should also think about other desktops like XFCE.

About XFCe...

I know, late reply is late... and I wrote the same already in the slax forum...

My idea/Suggestion: tweaking a standard Porteus into a Porteus with no KDE but XFCe instead means also include all the non KDE programs from the console, like cdrecord, mkisofs and more like that (and manfiles and readmes and setup files), and create that module for each and every Porteus version anew. Same is when someone wants to create a Gnome-Only Porteus.
And technically spoken the users need to download that extra module, although all these programs and manfiles and readmes and setup files are just the same as in the original Porteus ISO...


005-kdeapps.lzm
006-koffice.lzm
can be ommited. Same with 003-lxde.lzm

BUT the non-KDE programs from 004-kde.lzm are needed for any non-KDE porteus as well...

Therefore my idea: to me it sounds easier when we would split the 004-kde.lzm for each any every generic Porteus version - like into:

003-lxde.lzm
004-konsole.lzm (or maybe: 004-programs or any other neat name) [here goes cdrecord, mkisofs and whatnot]
005-kde.lzm (the rest of the original 004-kde.lzm from Porteus 0.9 to 1.0a - but this time really only the KDE stuff)
and the rest of the modules with the according number.


And I think it would be possible to write a script that auto-splits the module... Simply based on a listfile that lists all the path and filenames to be removed from the original 004-kde.lzm


What do you folks think of that idea?

I hope I was able to explain it in an understandable way, since I sometimes have issues doing so in English...

Sorry - it's little bit off topic but important:

@Rava and others
what about merging 004-kde + 005-kdeapps into 005-kde and create 003-multimedia with moved libs+utils (like mplayer, cdrecord) from kde desktop?
it would look like here:
000-kernel
001-core
002-xorg need to export all libs to 003-multimedia
003-multimedia need to import all libs from kde (except of qt and kde specific libs) + optionally: merge 007-firefox
004-lxde
005-kde
006-devel

in this case lxde (as well as Gnome, Xfce, etc) users would have mplayer, cdrecord and other non kde specific utils and libs available by default.

What do you think?

idea to rearrange base modules !

ok , as I read many topics on internet says "LXDE" is the best lightweight desktop currently and faster than XFCE.
-------------

maybe should move KDE applications from "005-kdeapps" to "004-kde" and rename "005-kdeapps" to "005-apps" ,
and this "005-apps" module contain applications which work on both LXDE and KDe , for example: unrar, mplayer, xdialog ... etc.
that's mean if we deleted "004-kde" will not lose applications in LXDE, also if we deleted "003-lxde" will not lose applications in KDE.

regards !

fanthom wrote:Sorry - it's little bit off topic but important:

@Rava and others
what about merging 004-kde + 005-kdeapps into 005-kde and create 003-multimedia with moved libs+utils (like mplayer, cdrecord) from kde desktop?
it would look like here:
000-kernel
001-core
002-xorg need to export all libs to 003-multimedia
003-multimedia need to import all libs from kde (except of qt and kde specific libs) + optionally: merge 007-firefox
004-lxde
005-kde
006-devel

in this case lxde (as well as Gnome, Xfce, etc) users would have mplayer, cdrecord and other non kde specific utils and libs available by default.

What do you think?

You mean, when making an XFCe only Parteus the user would use:
000-kernel
001-core
002-xorg
003-multimedia
007-firefox
00X-xfce

I would keep Firefox (incl. recent Flash) in an extra file since it should be updated when a new version is available (security and vulnerability issues and all that jazz)

Or:
Gnome with LXDE:
000-kernel
001-core
002-xorg
003-multimedia
004-lxde
007-firefox
00Y-gnome

When I got that right then I would say: Yes, let's make it so , but please keep FFx in its own module.

@Rava
yes - that's my intention
do other agrees on this change?

fanthom wrote:@Rava
yes - that's my intention
do other agrees on this change?

Well... I sure do, but with the extra thingy keeping FFx in its own module because of the easier update and it being a vulnerable part of the OS...

And I would help you with splitting up the modules for... say, the Porteus 1.0 beta version. ahem, I meant gamma version of course...
Since that would have been my work to do anyway...

EDIT:\\
let's move discussion up here:
http://forum.porteus.org/viewtopic.php? ... 1949#p1949

fanthom