[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: rock64, date is UTC, how to make EST (s/b UTC-5)



On 22/07/18 21:30, Gene Heskett wrote:
On Sunday 22 July 2018 14:58:33 Mark Morgan Lloyd wrote:

On 22/07/18 15:15, Gene Heskett wrote:
On Sunday 22 July 2018 10:11:04 Mark Morgan Lloyd wrote:
On 22/07/18 14:00, Gene Heskett wrote:
I have a bunch of locale related errors too.
Was a stretch-minimal install by ayufan, has xfce for desktop

What am I missing?

The traditional command for that was tzconfig, but these days it
will tell you to run dpkg-reconfigure something...

WARNING: the tzconfig command is deprecated, please use:
    dpkg-reconfigure tzdata

Worked a treat, thank you.

It's regrettable that dpkg-reconfigure doesn't have something like a
--list command which summarises the packages to which it may be
applied, or even a --search which works by analogy with apt-cache etc.

And if my well aged wet ram is to be trusted, it used to do a lot more
than it is now, only setting two items in the locales now.  Or its been
stripped to do the bare minimum on a rock64/arm64. Dunno which, but its
a dissapointment, just like the networking is broken in that it cannot
apply a gateway to a static setup without doing a separate command with
route once its booted. Putting the gateway address into /e/n/i.d/eth0 is
simply ignored. I even moved it to /e/n/i, no effect. Yesterday I tried
changing the static address, took 3 powerdown reboots to actually get
that to take, and 2 reboots to restore the original which was easier
than editing every /e/hosts file on my local network. A networking
restart totally ignores anything you do in /e/n/i.  Sounds crazy and
impossible, but thats how it works here. Depressing is what it is....

What I'd say is that with pukka Debian on PCs and Raspberry Pis (and in the latter case also Raspbian, although note that I'm making a distinction) up to Buster (on PCs) and Stretch (on RPis) /e/n/i works as expected. I have however just dug out this note

# In /etc/NetworkManager/NetworkManager.conf an entry like

# [keyfile]
# unmanaged-devices=mac:b8:27:eb:86:2f:e6

# will prevent a device from being brought (half-)up by Network Manager.

although I can't remember the extent to which I actually needed it in the end.

The TinkerBoard I was testing the other day had an interface naming problem, apparently brought about by the fact that it had all drivers built into the kernel binary rather than stored as modules... presumably the maintainers thought that if they did that it would make the card removable (but see my heads-up about putting it into single-user mode the other day).

NetworkManager is an unremitting nuisance IMO except for the specific case it was designed for, which is a laptop moving between WiFi access points. ModemManager is little better, but regrettably is a prerequisite for usb-modeswitch.

--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]


Reply to: