ok, my friend, i assume that i don't explain the thing correclty that is why you don't understand what i mean, no fight against you ok :).
about /tmp. on my system
% stat /tmp
Fichier : '/tmp'
Taille : 4096 Blocs : 8 Blocs d'E/S : 4096 répertoire
Périphérique : 803h/2051d Inœud : 5898241 Liens : 28
Accès : (1777/drwxrwxrwt) UID : ( 0/ root) GID : ( 0/ root)
Accès : 2016-06-28 05:21:08.715205623 +0400
Modif. : 2016-06-28 05:35:49.895232178 +0400
Changt : 2016-06-28 05:35:49.895232178 +0400
Créé : -
apparently equal between us, but
% stat /tmp/.X*-lock
Fichier : '/tmp/.X0-lock'
Taille : 0 Blocs : 0 Blocs d'E/S : 4096 fichier vide
Périphérique : 803h/2051d Inœud : 5898256 Liens : 1
Accès : (0444/-r--r--r--) UID : ( 0/ root) GID : ( 100/ users)
Accès : 2016-06-27 07:43:23.015183385 +0400
Modif. : 2016-06-27 07:43:23.015183385 +0400
Changt : 2016-06-27 07:43:23.015183385 +0400
Créé : -
Fichier : '/tmp/.X1-lock'
Taille : 11 Blocs : 8 Blocs d'E/S : 4096 fichier
Périphérique : 803h/2051d Inœud : 5898262 Liens : 1
Accès : (0444/-r--r--r--) UID : ( 1000/ obarun) GID : ( 97/ input)
Accès : 2016-06-28 05:21:08.745205625 +0400
Modif. : 2016-06-28 04:42:41.818469440 +0400
Changt : 2016-06-28 04:42:41.818469440 +0400
note gid from .X1-lock
% stat /tmp/.*-unix
Fichier : '/tmp/.ICE-unix'
Taille : 4096 Blocs : 8 Blocs d'E/S : 4096 répertoire
Périphérique : 803h/2051d Inœud : 5898258 Liens : 2
Accès : (1777/drwxrwxrwt) UID : ( 1000/ obarun) GID : ( 100/ users)
Accès : 2016-06-27 06:50:00.835026352 +0400
Modif. : 2016-06-28 04:42:58.468469941 +0400
Changt : 2016-06-28 04:42:58.468469941 +0400
Créé : -
Fichier : '/tmp/.X11-unix'
Taille : 4096 Blocs : 8 Blocs d'E/S : 4096 répertoire
Périphérique : 803h/2051d Inœud : 5898243 Liens : 2
Accès : (1777/drwxrwxrwt) UID : ( 0/ root) GID : ( 100/ users)
Accès : 2016-06-26 21:37:22.780296756 +0400
Modif. : 2016-06-28 04:42:41.898469441 +0400
Changt : 2016-06-28 04:42:41.898469441 +0400
Créé : -
% stat /usr/bin/X*
Fichier : '/usr/bin/X' -> 'Xorg'
Taille : 4 Blocs : 0 Blocs d'E/S : 4096 lien symbolique
Périphérique : 803h/2051d Inœud : 658959 Liens : 1
Accès : (0777/lrwxrwxrwx) UID : ( 0/ root) GID : ( 0/ root)
Accès : 2016-06-27 09:32:48.510903867 +0400
Modif. : 2016-06-09 10:05:57.000000000 +0400
Changt : 2016-06-27 09:32:44.627570614 +0400
Créé : -
Fichier : '/usr/bin/Xorg'
Taille : 2266696 Blocs : 4432 Blocs d'E/S : 4096 fichier
Périphérique : 803h/2051d Inœud : 658960 Liens : 1
Accès : (2755/-rwxr-sr-x) UID : ( 0/ root) GID : ( 97/ input)
Accès : 2016-06-27 09:32:48.510903867 +0400
Modif. : 2016-06-09 10:05:58.000000000 +0400
Changt : 2016-06-27 09:32:44.744237279 +0400
Créé : -
Rootless only works with video drivers that support kernel mode-setting (KMS), it's the case for you? i don't know, that is for why i ask to you to test with an iso (runit or s6, don't matter). i'm not telling you to reinstall the thing from the iso because this don't change anything.
2. Compare the iso filesystem with my filesystem (very time consuming as I wouldn't know what to look for)
you're right , it's time consuming, but this allow you to justly know if a trouble exist very quickly. A trouble exist? ok, bad news, need to search on filesystem.Same thing with the iso, this doesn't work? ok, the filesystem is not the trouble. Do you understand why i'm talking about iso? but maybe i'm wrong.
Take a look at my pacman -Qkk and say otherwise
hmm, i don't see xorg on the list
on my system
obarun@ obarunS6 [1] ~ % sudo pacman -Qkk xorg-server-nosystemd | egrep "backup|warning|error"
avertissement: xorg-server-nosystemd : /usr/bin/Xorg (Les GID ne correspondent pas)
avertissement: xorg-server-nosystemd : /usr/bin/Xorg (Les permissions ne correspondent pas)
Q: Why would xorg produce /obvious/ permission errors if it was my hardware?
my bad, by hardware i mean drivers issue. for example openchrome drivers doesn't support X rootless.
Yet you insinuate since the new s6 iso /work/ with xorg-rootless as opposed to runit, it would work if I install from it. Just notice how you do this agian with the word "compared"
obsolutly not, works on runit iso too
So tell me eric, lets just assume the iso works,which it will because you've made alot of changes since then you even admit you could not upgrade from the repos you had to use the cache instead.
nope, the change on the iso concern : theme for openbox and some program replacement. but the "base" system is the same. bit, i have a very poor connection, so downloading the same package is a waste of time and the cache on my system is already up to date. So why i need to download again the same packages? taking the cache allow my to gain a time.
i need to make a new iso release for runit, not for changing thing (well, i will change probably the theme :) ) but to follow the new packages version (kernel, video drivers, etc). i certainly make it this week.
Obviously it is a hardware issue! (its not)
again my bad, drivers issue can be (pershap).
let's just FORGET my update about xorg in BOLD text on TOP
Again, my bad, i not seen it.
It was a clear /concern/ of keeping things as they are. and yet you got mad. WHY?
because you have made a tirade about s6 but for why? i don't know, just because i'm ask you to test with s6 iso? my thought is : make a test from an iso already up to date is better than make a test from an iso which is not up to date. runit iso or s6 iso are the same appart , obviously, the init system and the service manager, but all the package concerning the "base" (so xorg, mesa, drivers, X program) are the same. So testing from one or other it's the same, not?
Managed by? you mean the opposite, because if svcscan ever "managed" s6-serv it would be documented on the offical site, not obarun. But it isn't, instead s6serv is *instructing* svscan to manage services differently then how it is documented to manage services, in s6-rc. Something that modifies a software to do different tasks other then what was documented originally is a hack. case closed. If I need to manages services like runit. I'd use just use runit until s6 proves it self more. or I get tired of runit, which ever. Or maybe you can search "site:skarnet.org "s6serv"" into any given search engine and just tell me if you find anything at all.
ok, i assume again that i do not explain correctly the thing. what i mean by s6-serv? we have two sort of service e.g. cups-s6rcserv and cups-s6serv(note : the name is abitrary here like cups-runitserv). This is the same service but those two package install thing differently. cups-s6rcserv install file which will managed by s6-rc and cups-s6serv install file which will managed by s6-svc. here when i said managed it mean, user management. So an user which want to change the status of a s6rcserv service take the s6-rc program and an user which want to change the status of s6serv service take the s6-svc program. (in reality, s6-svc can managed the both :), in fact s6-svc sends commands to a running s6-supervise process, see below).
so now, a service (whatever s6rcserv or s6serv) is monitored by s6-supervise. then a collection of s6-supervice (called a sevice directory or scan directory) is monitored by s6-svscan . So s6-svscan start and monitor a directory which contain a group of service monitored by s6-supervise.
With s6-rc we can have two sort of "service" : oneshot or longrun. A longrun is the exact equivalent of a service in the supervision sense. It is defined by a service directory, with a run script and optional other data. So, according to this, an longrun s6rcserv service need to be declare on a scan directory monitored by s6-svscan.
a oneshot is managed by the program s6-rc. s6-rc can manage an longrun or oneshot s6rcserv service. s6-svc can manage a longrun s6rcserv but cannot manage an oneshot s6rcserv service.
All service managed by s6-rc need to be initiate by s6-rc-init which need to be started on a directory managed by s6-svscan.
We can have a multiple collection of svcan directory (not the case with runit, only one directory is permit e.g. /var/service).(one of the "dumb" reason)
So, a svcan directory is started at boot time by the pid 1 on /run/boot/service then ,during the stage2, s6-rc-init initialize tool for the s6-rc system (note: remember , s6-rc tool need to be initiate under an svcan directory). then s6-rc start and managed a collection of s6rcserv service.
During this collection of service, a longrun service called switch-svcan (note : the name is abitrary) is started. This longrun start an another s6-svcan program which managed the scan directory /boot/user/service. then an another s6-rc-init program initiate a collection of s6rcserv service.
So now we have two scan directory one on /run/boot/service and the other on /run/user/service. on /run/boot/service we have a collection of s6rcserv managed by s6-rc AND a collection of s6serv managed by s6-svc because this two program need to be declare on a svcan directory which are managed by s6-svscan.
on /run/user/service we have an another collection of s6rcserv managed by s6-rc AND a collection of s6serv managed by s6-svc.
in fact /run/boot concerns service needed for the boot and /run/user concerns service needed by the user. So service for boot and user are completly separate and it's an better way than runit :).(another one of the "dumb" reason). so now on /run/user i can have a s6rcserv AND a s6serv service.
Where is the hack here? All this thing come from the source of s6 supervison suite, i do not change anything on the program as anopa as maded. Just i use the feature provide by laurent :). This is just the top of the "iceberg".
allow me to show you what "just werks" means
my bad, i was assumed that was a type syntax error :(
you would be calm and collected in replying
done, i hope :)
'what ever works from the iso works everywhere' right?
justly not, this is why i ask you to test my friend, can be works on my hardware but maybe not on your hardware
ow many people tested xorg-rootless again? two? maybe three? how many people have obarun? How many people still have traditional xorg?
all the people which use obarun doesn't come here :). some people prefer to mail me directly, so...
i have an another user which that doesn't work too and you know what.. he is on radeon pffff. I have not tested yet on the portable on my wife with radeon too. i need to make it.
i hope i answered at your question correctly, if is not the case tell me :).
Sorry for the last post, i have completly crashed my system saturday during a test (two day to repair it pff) and when i see your tirade about s6 i saw red lol.
Please do not mix X rootless and s6 haaaaaa (i've already made the same thing on this post lol)