Porteus/Arch aka Sensei (Porteus w/pacman package manager)

[blue4meridian]

Salutations...

Yes, on my machine I have made it possible to send the video and sound to HDMI when HDMI is plugged in. I don't use it though. I prefer the video to go to the monitor but the sound to stay on the laptop (kickass Harman Kardon speakers). It is really not so difficult to script this, but there is some buginess when scripts are run via udev.

This is exactly the solution I'm interested in. Unfortunately... I don't have the skill set.

Best Regards...

[francois]

Rava, I use grub legacy.

But stifiling porteus-archlinux hybrid is exactly like porteus in terms of installation on a usb with syslinux.

The most recent porteus-sensei is based on 3.17.0-porteus.

[Rava]

The most recent porteus-sensei is based on 3.17.0-porteus.

Okay, the newest ones for x86-64 have this time stamp: 2014-04-11

Are these the ones you meant?

[francois]

Sorry for my ignorance, but how do you get the stamp?

[Rava]

Sorry for my ignorance, but how do you get the stamp?

I open the iso, copy the files and make a ls -l on the files.

[blue4meridian]

Salutations...

Ok... LxQt/Kwin is more or less finished. However... w/out eye candy. 191 packages. I'll render the module tonight.

Best Regards...

Posted by 100.1.102.215 via http://webwarper.net
This is added while posting a message to avoid misusing the service

[blue4meridian]

Salutations..

On startup LxQt/Kwin complains that the package version is too recent.

Best Regards...

Posted by 100.1.102.215 via http://webwarper.net
This is added while posting a message to avoid misusing the service

[stifiling]

i put together an updated as of 9-26-2015 Sensei 64-bit. it's barebones though, only 000-kernel.xzm, and 001-core.xzm. this way u build the system *exactly*, as fat, or as skinny as *you* want it. toughest part will probably be connecting to the internet to install with pacman, the stuff you want. easiest way is hardwiring/ethernet. could also connect to your wifi with wpa_supplicant.

after connecting online, you'd probably want xorg and this is installed by:

Code: Select all

pacman -Sy

Code: Select all

pacman -S xorg-server xorg-xinit xf86-input-keyboard xf86-input-mouse xf86-video-vesa

for your specific video card you could instead of installing xf86-video-vesa, install xf86-video-intel or xf86-video-ati or xf86-video-nouveau

after that you can install your favorite DE

Code: Select all

pacman -S xfce4

you can install the whole xfce, or pick the parts of it you want. or install any other DE or WM you want.

if xfce is the DE you chose to install, next you'd run the command

Code: Select all

nano .xinitrc

when nano opens the .xinitrc file, type in:

Code: Select all

exec startxfce4

close nano with Ctrl+x, press Y for yes, and press Enter to save the file. then run the command:

Code: Select all

startx

that should start xfce.

this is just a base and maybe some of the users will create and share the DE's and other custom modules. LXQT that blue4meridian's been pecking around with should install much more easily now.

Sensei-v3.1-x86_64.iso 77 MB
md5sum = 2e7d3f0b85a765dd8c9ba08776e9daa6

[blue4meridian]

Salutations...

Outstanding! Thanks stifiling.

Best Regards...

Posted by 100.1.102.215 via http://webwarper.net
This is added while posting a message to avoid misusing the service

[Rava]

for your specific video card you could instead of installing xf86-video-vesa, install xf86-video-intel or xf86-video-ati or xf86-video-nouveau

No nvidia? O___o

[stifiling]

well the closed source nvidia driver isn't in the arch repos...that's one of the packages that would be installed from the AUR using yaourt. this is a kernel module compiled from the AUR though. targeted at an arch linux kernel. but since we're not using an arch kernel, this means it takes a bit of adjustments to get it to compile using yaourt.

kernel modules like nvidia, virtualbox, etc., are probably easier compiled the traditional way. and then making a .xzm module or .pkg.tar.xz file and sharing it. so that the next user interested in it wouldn't have to go through those troubles.

[Rava]

kernel modules like nvidia, virtualbox, etc., are probably easier compiled the traditional way. and then making a .xzm module or .pkg.tar.xz file and sharing it. so that the next user interested in it wouldn't have to go through those troubles.

Ahhh okay, well, funny enough, I used to be one of the users compiling the nvidia drivers for upcoming Porteus versions, back when it was, like version 0.8 or 0.9 or such. But there was some tricky thing, something you had to either tweak, or take care about somehow. Sadly, I was stupid enough to not document what the tricky thing was, and quite later, when I tried to compile a nvidia driver once again, I did fail, due to having forgotten how to deal with the tricky part...

So... when I have time, I will try to compile it for the recent x86-64 version you just posted above, but me thinks I am too busy with RL stuff right now...

[neko]

@stifiling
I converted "your 64bit ISO" to "32bit ISO".

Sensei-v3.1-i486.iso (68 M)
http://www.mediafire.com/download/7hla5 ... 1-i486.iso
md5sum: 98a67988fbfe817c5b4ae50897bb973f Sensei-v3.1-i486.iso

Thanks.

[francois]

@stifiling:

Thanks for providing this minimalist porteus-archlinux clone. Download:
http://sourceforge.net/projects/senseig ... urce=files


@rava and bluemeridian:

Essentially archlinux is an obligatory DIY distro, which essentially refer their members to read the wiki and to RTFM (read the fine manual).

Which means that they have put a great deal of effort on wikis. These wiki are almost the best there could be on linux, they are constructed on the KISS philosophy. Provided that porteus would switch to archlinux, this would save us an enormous amount of work. All we would have to provide is our most friendly forum (with minor exceptions).

Thus usually, you will find with search words on internet nvidia wiki archlinux or nvidia wiki virtual box for example.

archlinux nvidia wiki:
https://wiki.archlinux.org/index.php/NVIDIA#Installing

archlinux virtualbox wiki:
https://wiki.archlinux.org/index.php/VirtualBox

I have build vbox recently thru archlinux, you have to do it the arch wiki way or you will get into problems.

[stifiling]

Rava,
Keep your head up man. that's gotta be a tough place at this time. i lost mom myself last year.

neko,
that 32-bit clone went real well. wondering how you did it. where'd u get the 3.18 kernel...you compiled it? few things about it though...in the 000-kernel.xzm, there's some firmware missing out of /lib/firmware. iwlwifi for one, my wifi module is iwl3945 and won't work w/o that firmware. also, after getting it online, when trying to do

Code: Select all

pacman -Sy

it's giving off the errors because in the /etc/pacman.conf file, line #80 is pointed @ [Sensei64], where it should be just [Sensei]. also lines #99, 100, 101..the multilib stuff...should be commented out, or deleted.

after that, when trying to install with

Code: Select all

pacman -S

for the first time, you'll notice how it's pretty much trying to reinstall the whole complete core again. bash, and everything else..which is already there. this is because pacman doesn't know it's there. pacman keeps track of what's already been installed by checking the folder /var/lib/pacman/local. in the 32 bit clone, this folder doesn't exist. in the 64 bit one i uploaded...u'll see this folder does exist, and is full of folders. these folders are pretty much flags to let pacman know, these dependecies are already installed.