Porteus

nice one, thanks Ed

Ed_P wrote: ↑

07 Dec 2019, 19:22

Does Porteus have an irc app?

there are a few.. hexchat is what i'm using for now.. it's pretty straightforward

(but only for this tty, all other are still showing porteus login. if you press enter without logging in, it refreshes to the correct hostname ...pretty much what happens when slim has it's second attempt.. there's more to this, but i'm at a loss as to how hostname is handled without the 'hostname'...

at the the start up, after the modules are loaded and welcome message, there is a tty login prompt(show briefly before X starts or stops there if cheatcode 3 is used)
what does it show? default is: porteus login: should be: <newhostname> login:
or ctrl+atl+fn to another tty

i've made an irc chat channel on freenode #porteuslinux for anybody who is into that kind of thing.
i try to log in daily, so if you have some query or looking for help, grab your favourite chat client and stop by..

ok.. have found some fixes for what i'm experiencing at least.. and here's a module of it: 09-hostname-patch-for-p4.0.xzm it contains hostname from slackware current and /etc/rc.d/rc.M with this section: # Set the hostname. if [ -r /etc/HOSTNAME ]; then /bin/hostname $(/bin/cat /etc/HOSTNAME) & else...

pretty sure bluez was in 4.0 too

shouldn't need bluez since it's included in 002-xorg .. bluez-firmware could be handy tho .. didn't appear to need it for my hardware..

fyi libnm is part of the NetworkManager package in porteus
libnm-qt is some qt bindings for it

and BLUETOOTH (Post by ncmprhnsbl #74885)

here you go: test it out, if it works for you i'll add it to the bundles collection.. blueman-2.0.8-x86_64-xfce4.xzm md5sum 532586b867497db0f9b3bc82638a76f7 so, be sure to have the daemon running either by cheatcode: bluetooth or in the settings centre >second tab at the bottom on starting the bluet...

rchase wrote: ↑

03 Dec 2019, 05:07

The daimon is preesent in XFCE, but I have not been able to use bluetooth in it.

most likely missing a python part ... i'm close to getting on to it for you

further test: kde and nvidia driver: now behaves like all the others ie. baulked start (but doesn't mind changing hostname in X) not suggesting drivers per se but there seems to be different outcomes with different driver/DE combos .. i'm interested in this "Display Name: <hostname>:0" what set this...

if using the nvidia driver is affecting this at all well.. preliminary test with nvidia driver shows no difference here ie. still getting the hang.. although, now , if i change HOSTNAME the present X session is broken: guest@doobie:~$ su Password: root@doobie:/home/guest# echo floobie > /etc/HOSTNA...

if using the nvidia driver is affecting this at all .. this line in nvidia settings>X Server Information: Display Name: <hostname>:0 (where <hostname> is whatever is set as hostname)
i need to compile the nvidia driver for 4.0 to test this ..

Is this "hang of the x login" DE specific? If yes, which one? good question. i did some tests and for me: all DEs except KDE display this behaviour with modified HOSTNAME.. this machine uses the radeon driver. what difference the nvidia driver could make i have no idea.. and what is different with ...

@donald hmmm, i've followed your instructions: setup changes, edit HOSTNAME, xauth list ,copy cookie code to xauth add, reboot .... no discernable change.. i'll just add that the DE does eventually start(as it does without doing any of the above), but this is because slim gives up waiting and has an...