Just keeping track of some stumbling blocks encountered (knowing that much might be intentional to keep the system "lean" or as an incentive for "learning" ;-) - but best solutions everyone needs anyway could of course be listed here by many contributors, as well as deep-linked to in other threads they've popped up it)...
Installing various distributions (ARM and Intel/AMD) within a few days, I've noticed some defaults could be added (looking at Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi for the examples below) where things take inordinately long to search & set up otherwise:
Neither /usr/bin/tzselect nor dpkg-reconfigure tzdata, even when they have been found, say they set the TZ for more than the current user (even recommending to add exports to the ~/.profile) - this could be prompted for system-wide, have one recommended way of setting it (possibly as simple as echo 'Continent/Capital' >/etc/timezone ?), or be preset to a usable default for root (all the more since ntpdate seems to be installed already) - which one is the intended "standard approach"?
Several key components (incl. Perl needed all the time as part of package management) complain with respect to locale/lang settings - not sure how this is best avoided (not by setting everything I guess, as LC_ALL for instance is discouraged):
Shouldn't the LED go dark (echo 0 >/sys/class/leds/status:green:health/brightness) on halt, to signal when it's safe to pull the plug (or light up then if it was off during normal operation?), cf. http://midnight-coder.blogspot.de/2013/12/pogoplug-e02-configure-leds.html ?
Curiously there is no default /etc/crontab nor an apparent process that would use it, according to ps aux|grep cron and dmesg|grep which also returns empty while I'd expect something like "Starting periodic command scheduler: cron." - as per http://forum.doozan.com/read.php?2,12096,16414#msg-16414 it should be there?
There's no "less", easily installed no less. ;)
Surprisingly the barrage of ssh hacking attempts (several per second especially from high-bandwidth Asian netblocks) I've always seen on Arch (and Ubuntu) as soon as port 22 has to be exposed beyond the LAN has started much later&lighter according to logread Debian @ 3.16 - just a lucky coincidence, or is there any more aggressive filtering/greylisting in place on this one (and which settings can long-term users recommend for a public ssh port) ?
On the other hand there are dire warnings on regular connects from within the LAN (where the provider's crappy router admittedly is a poor resolver that requires clients to keep their local peers on /etc/hosts or fixed IPs):
Installing various distributions (ARM and Intel/AMD) within a few days, I've noticed some defaults could be added (looking at Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi for the examples below) where things take inordinately long to search & set up otherwise:
Neither /usr/bin/tzselect nor dpkg-reconfigure tzdata, even when they have been found, say they set the TZ for more than the current user (even recommending to add exports to the ~/.profile) - this could be prompted for system-wide, have one recommended way of setting it (possibly as simple as echo 'Continent/Capital' >/etc/timezone ?), or be preset to a usable default for root (all the more since ntpdate seems to be installed already) - which one is the intended "standard approach"?
Several key components (incl. Perl needed all the time as part of package management) complain with respect to locale/lang settings - not sure how this is best avoided (not by setting everything I guess, as LC_ALL for instance is discouraged):
root@debian:~# man
man: can't set the locale; make sure $LC_* and $LANG are correct
What manual page do you want?
root@debian:~# perl -v
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_PAPER = "de_DE.UTF-8",
LC_ADDRESS = "de_DE.UTF-8",
LC_MONETARY = "de_DE.UTF-8",
LC_NUMERIC = "de_DE.UTF-8",
LC_TELEPHONE = "de_DE.UTF-8",
LC_IDENTIFICATION = "de_DE.UTF-8",
LC_MEASUREMENT = "de_DE.UTF-8",
LC_TIME = "de_DE.UTF-8",
LC_NAME = "de_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
This is perl 5, version 14, subversion 2 (v5.14.2) built for arm-linux-gnueabi-thread-multi-64int
(with 88 registered patches, see perl -V for more detail)
Shouldn't the LED go dark (echo 0 >/sys/class/leds/status:green:health/brightness) on halt, to signal when it's safe to pull the plug (or light up then if it was off during normal operation?), cf. http://midnight-coder.blogspot.de/2013/12/pogoplug-e02-configure-leds.html ?
Curiously there is no default /etc/crontab nor an apparent process that would use it, according to ps aux|grep cron and dmesg|grep which also returns empty while I'd expect something like "Starting periodic command scheduler: cron." - as per http://forum.doozan.com/read.php?2,12096,16414#msg-16414 it should be there?
There's no "less", easily installed no less. ;)
Surprisingly the barrage of ssh hacking attempts (several per second especially from high-bandwidth Asian netblocks) I've always seen on Arch (and Ubuntu) as soon as port 22 has to be exposed beyond the LAN has started much later&lighter according to logread Debian @ 3.16 - just a lucky coincidence, or is there any more aggressive filtering/greylisting in place on this one (and which settings can long-term users recommend for a public ssh port) ?
On the other hand there are dire warnings on regular connects from within the LAN (where the provider's crappy router admittedly is a poor resolver that requires clients to keep their local peers on /etc/hosts or fixed IPs):
Mar 23 00:03:01 debian auth.info sshd[5465]: Address 192.168.2.101 maps to localhost, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT![/quote]