open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=2939, ...}) = 0 -read(3, "# Locale name alias data base.\n#"..., 4096) = 2939 -read(3, "", 4096) = 0 +read(3, "# Locale name alias data base.\n#"..., 1024) = 1024 +read(3, "nd for the time being for\n# back"..., 1024) = 1024 +read(3, "59-1\ngalego\t\tgl_ES.ISO-8859-1\nga"..., 1024) = 891 +read(3, "", 1024) = 0 close(3) = 0
first major difference: locale not set.
--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Sun, Jun 3, 2018 at 10:56 AM, Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
On Sun, Jun 3, 2018 at 9:27 AM, Felix Miata mrmazda@earthlink.net wrote:
deloptes composed on 2018-06-03 09:26 (UTC+0200):
Luke Kenneth Casson Leighton wrote:
you could instead put the two files side-by-side in xterms of identical height and do page-down page-down page-down instead.
there is kdiff3 for that
It does a nice job of showing off differences. I see lots of differences related to which fonts are or are not installed, and the different hostnames and various addresses, but I fail to ID any missing bit to ID why 760's 'tdecmshell fonts' fails and 780's succeeds.
you'll be looking for the first "major" obvious difference. "the font is missing" is f****g useless: you already know that. it will be something like a directory name, or a .so missing, or a .so loaded from a *different directory* or... a config file that is missing or... basically something right at the start.
by the time you get to "the fonts are not loaded"... well... you already know that, so you're clearly *not* looking for that...
... *UNLESS*....
the locations where each system is *looking* for the fonts is different. *that* is something you will want to know.
track and *interpret* the differences... don't just go "errr there are differences". work backwards for what the *important* differences are.
l.