On Tuesday 29 November 2016 03:39:51 Thomas Lübking wrote: > On Mon, Nov 28, 2016 at 11:59:26PM -0500, Gene Heskett wrote: > >root 797 0.0 1.9 271380 33600 tty7 Ssl+ 20:50 > >0:02 /usr/lib/xorg/Xorg -core :0 -seat > >seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch > > > >gene 4114 0.0 0.0 5564 908 pts/8 S+ 23:48 0:00 > >grep --color=auto listen > > > >builders took advantage of that to get rid of 100k of object code. > > So I have challenged the odroid people to actually make it work. > > Got any clue on this or just a hunch? There's an explicit nolisten > switch that didn't end up there magically but will oc. prevent tcp > access for sure. > > >That server starts automatically. > > That's the "problem" - ask the odroid people about "automatically" > (i've no experience with that system, sorry) > > >The line that starts it, xinit/xsessionrc specifically says -listen > > tcp as an argument for /usr/bin/X > > I doubt the call is simply altered from listen to nolisten. > Pass it some unexpected bullshit argument ("-gnarf") and see whether > that has some impact - otherwise i'd say whatever starts X in that > environment doesn't care about xinit/xsessionrc at all. > > Cheers, > Thomas
Well, the droid may have a place sometime in the future, but at the moment it has been such a pain in my rear that it was popped of the panel, disconnected from the psu, and tossed on a high shelf. I had been instructed to originally install the jessie-lite version of raspian, but I went back to the site and pulled the full install image, and wrote that to the u-sd card. sync'd it, then unplugged it and plugged it back in and the automount dutifully mad it available as /media/usb1 and /media/usb2. So I dived into the /etc directory and installed my network setup, and made myself user 1000:1000, changing the name pi to gene anyplace I found it, making me the first user like I shoulda been in the first. And of course I forgot to make the network stuff immutable, so N-M destroyed it, as usual. A couple root sessions with nano, followed by some chattr +i on resolv.conf and interfaces fixed all that up. I'll have to see if I can remove that POS, but at least it can't cripple me again. This boots to a gui they call PIXEL, fair, needs some colors adjusted. I upgraded it to the latest, then installed synaptic since I couldn't make out which end of the horse their package manager was faceing me. I had saved the ~/linuxcnc directory out, and wrote it back to my new $home directory, and I installed the bleeding edge linuxcnc. modprobed the spi stuff into memory, fired up linuxcnc, and the interface card responded properly to the spi from linuxcnc, reporting a full list of its capabilities. So I loaded up a program to carve a chess pawn, homed it and hit the r key. And was blown away, it was running at about a 20 frame/second display rate! With nothing plugged into the droid, the raspi 3b was doing it all. No worries about whether or not x was listening on a tcp port (its not according to htop). Put the modprobed stuff into the load list file in /etc/modules. Rebooted, and it still Just Works(TM). I am indeed pleased. I might even sleep well tonight. Now to get the rest of it built & wired up. And in about 30 minutes amanda will see if it can back that puppy up. The checker didn't fuss, so I believe that will work. Only one problem, which I'll pose as a separate post. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s