Hello Maurice!

23 Nov 14 21:54, you wrote to me:

 MK> The RasberryPi gurus recommend that distribution.  Myself I'd be inclined
 MK> to go with the slackware based one and see what damage I could cause with
 MK> that on a commanline based system.  :::evil grin:::

 After installation I disable autostart of X, en enable ssh.

 MK> Near as I can tell the lack of VGA output would make the above
 MK> interesting
 MK> and as of this writing am not sure what I could get working graphically on
 MK> the commandline using the hdmi output.  I had a heck of a time getting
 MK> inteldrmfb and mplayer to cooperate.  Still haven't been able to get sound
 MK> working over that interface but that isn't all that big a deal since I can
 MK> still get sound outputting independently of hdmi.  I hear the nouveau
 MK> (Nvidia) based ones might be a better option in this particular case (hdmi
 MK> audio output).

 If you want to see what it can to, there is an install image with XBMC.
 Worls great sound goes to the monitor using the hdmi. If you Telly allows it
 you can use the remote control to command your XBMC on the Raspberry.

 KvE>> It is quite easy.

 MK> Other than the need for a DOS based partition for booting, it is not
 MK> unlike the way I have been doing all sorts of flashdisk based systems for
 MK> ~15 years now.  I did have to succumb to a DOS partition for an efiboot
 MK> thingy recently on an i5 based system recently but so far that has been
 MK> the only one.  :::knock on wood:::

 MK> I have been toying with the idea of a RasberryPi with a usb GPS reciever
 MK> that pulses to build an el-cheapo timeserver just for fun.  Maybe some
 MK> day.

 I have a link somewhere, where this is done. there is also a company that
 builds a special "shield" with a GPS receiver for this purpose.

 Before all this was availabel, I went the easy way, I just plugged a usb-gps
 mouse into my server. Gpsd puts the time in shared memory and the ntpd
 finds it there. It cannot compete with a tier one server, but it works.

# ntpdc -p
     remote           local      st poll reach  delay   offset    disp
=======================================================================
=SHM(0)          127.0.0.1        2   16    0 0.00000  0.000000 3.99217
*chime3.ipv6.sur 2001:980:42ea:1  1 1024  377 0.01894 -0.000118 0.13953
=tt52.ripe.net   2001:980:42ea:1  2 1024  377 0.02138  0.001263 0.12230

 The first line is Shared memory, that is written by GPSD.

 You will probably understand why I chose time servers that offered IPv6.
 IPv4 could he be better as that pipe is faster, soo the delay will be
 less.

Kees

--- FPD v2.9.040207  GoldED+/LNX 1.1.5