Re: po...@lists.debian.org

[Larry Dighera]

On Sat, 09 Jan 2021 12:03:50 -0600, John Hasler  wrote:

>Anyone can run an NNTP server.  While it once required a VAX
>with a T1 to act as a Usenet "backbone" site any desktop with broadband
>can easily handle it now.


Indeed.  In the early '80s I ran a usenet HHTP node under Xenix using B News
(written in shell script).  ...

Re: po...@lists.debian.org

[Larry Dighera]

Sir,

Are you suggesting that the usenet be re-invented?  :-(

Usenet is a decentralized e-mail based network system of communication
conceived around the time that ARPANET was initiated ('70s) that has no
central administrative body, and thus cannot be suppressed.  Because of this
inherent inability to monetize it, ISPs dropped bundling usenet as part of
their subscriber services about a decade ago, similar to Verizon's dropping
Yahoo Groups December 15, 2020.  You may be familiar with Google Groups that
carries a free usenet feed.

Today, usenet still exists albeit a skeleton of its former incarnation.
There are free News Network Transfer Protocol (NNTP) servers available such
as nntp.aioe.org and  free-usenet.com, and paid servers like
news.giganews.com.  There are free news reading clients such as Thunderbird
and Forte Agent, and the venerable rn for *nix platforms.

So, what you seek has existed for decades, and is still viable as a forum
for free speech as it always has been.  

Here's a clue: https://www.google.com/search?client=none=usenet

Best regards,
Larry Dighera




On Saturday, January 9, 2021, 6:27:08 AM PST, Marek Mosiewicz
 wrote: 
>
>In case commercial social networks will not protect freedom of speach [sic]
>there is always option to use mailing lists.
>
>In fact I can imagine Twitter or Facebook as web based mail client
>which aggregates urls for messages publicated on anywhere in Web.
>
>Everbody who observes somebody will receive email with link to message.
>Likes and comments are also mails (the can even be signed).
>
>Webserver which serves given message will receive like and comment
>mails and presnet it. Yo can see source of mail e.g for like AND verify
>that like was realy given by ckecking GPG signature of sender.
>
>
>Cheers,
>  Marek Mosiewicz
>  http://marekmosiewicz.pl
>
>
>

Fw: Temporary color prompt in bash script

[Larry Dighera]

 On Mon, 02 Sep 2019 08:48:50 +0200, Computer Planet

 wrote:

>Is It possible to print of a string at the exit of a bash script?

Have a look at `man bash` and search for 'trap.'

 trap [-lp] [[arg] sigspec ...]
              The command arg is to be read and executed when the
shell receives signal(s) sigspec.  If arg is absent
              (and  there  is a single sigspec) or -, each specified
signal is reset to its original disposition (the
              value it had upon entrance to the shell).  If arg is the
null  string  the  signal  specified  by  each
              sigspec  is ignored by the shell and by the commands it
invokes.  If arg is not present and -p has been
              supplied, then the trap commands associated with each
sigspec are displayed.  If no arguments are  sup-
              plied  or  if  only  -p is given, trap prints the list
of commands associated with each signal.  The -l
              option causes the shell to print a list of signal names
and their corresponding numbers.  Each  sigspec
              is  either  a signal name defined in , or a
signal number.  Signal names are case insensitive
              and the SIG prefix is optional.  [...]  

Re: [OT] Breaking WPA2 by forcing nonce reuse

[Larry Dighera]

On Mon, 16 Oct 2017 15:42:09 + (UTC), Curt  wrote:

>https://www.krackattacks.com/
>
> Our attack is especially catastrophic against version 2.4 and above of
> wpa_supplicant, a Wi-Fi client commonly used on Linux. Here, the client will
> install an all-zero encryption key instead of reinstalling the real key. 
>
>Uh-oh.

 Latest Intel drivers:
https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00101=en-fr
for M.2 devices.

NetGear firmware updates:
https://kb.netgear.com/49498/Security-Advisory-for-WPA-2-Vulnerabilities-PSV-2017-2826-PSV-2017-2836-PSV-2017-2837

Re: Log Xsensors Core Temperature Data

[Larry Dighera]

On Thu, 05 Oct 2017 12:11:33 -0400, "Stephen P. Molnar"
 wrote:

>Is there a way to log the time and temperature data for the CPU from the 
>xsensors app?
>
>Or, a;alternately, is there an app that will allow me to save the CPU 
>core time temperature results?
>
>Thanks in advance.


I have no personal experience with this, but it would seem a simple
matter to write a small shell script to periodically read the
temperature device in /dev and write the data to a file.  Once the
sampled data are available, Linux has a rich set of tools to parse the
data and report whatever you desire.

Alternatively, the technique employed by xsensors could be extracted
from the source code as a basis for a temperature recording program.

Just my 2¢.

Re: An answer to "Gave up waiting for suspend/resume device"

[Larry Dighera]

On Sat, 23 Sep 2017 04:42:07 + (UTC), Mark Luxton
 wrote:

>RE:Re: Gave up waiting for suspend/resume device
>
>  
>|  
>|   |  
>Re: Gave up waiting for suspend/resume device
>   |  |
>
>  |
>
> 
>
>Try:Use blkid to determine the UUID of your swap partition, and while at it, 
>make sure all other partitions have correct UUID's in /etc/fstab. Also can use 
>lsblk -f to find the UUID's.
>
>Put the correct UUID's into /etc/fstab, especially swap, for this error.
>
>Put the correct UUID for swap into /etc/initramfs-tools/conf.d/resume.
>
>Run sudo update-initramfs -u
>
>Reboot. Fixed my triple boot of Stretch all with this error, as the swap file 
>had changed.
>Truly, Mark Luxton

Note what occurs when there is no image in the swap FS and initramfs
is expecting to find one.  

Re: Recommended editor for novice programmers?

[Larry Dighera]

On Sat, 2 Sep 2017 20:34:27 -0500, Mario Castelán Castro
 wrote:

>Assuming that people in the OP's library is representative of the
>general population, then most people in that library will never “develop
>a greater interest in computers” like you and me. Run-of-the-mill users
>do not care if software is very powerful, configurable, reliable, or
>other technical merits. They want something that is so simple to use
>that they will never need to even glance at the manual. Microsoft and
>Apple deliver that and that is why they have had so much commercial success.


If the OP wants to provide a GUI editor that resembles MS Write, with
which his attendees would likely be familiar, he might resort to Libre
Office https://www.libreoffice.org/ .  Libre Write
https://www.libreoffice.org/discover/writer/ is part of what is
essentially a free MS Office Suite, and runs on many platforms.  But
it's not a programmer's editor.  (If this has already been mentioned
in this thread, please forgive me.)

Re: Recommended editor for novice programmers?

[Larry Dighera]

On Sat, 2 Sep 2017 20:46:33 -0400, rhkra...@gmail.com wrote:

>I do occasionally use vi (when 
>I'm stuck with no other editor), but I wouldn't wish either on a novice 
>programmer.  Further, I don't think they have any advantage over a good GUI 
>editor with features like a scripting language, keyboard macros, outlining / 
>folding, syntax highlighting, and such.

The vi (visual interface) editor was used by AT (the developers of
Unix under government contract) service personnel to administrate the
US telephone network over dial-up connections.  As there was no mouse
support in those early days, vi was designed to be used entirely from
the keyboard, a feature touch-typists will appreciate because it
doesn't require reaching for a mouse and abandoning the home-row hand
positions.  

With regard to the missing features being lamented above:
https://www.ibm.com/developerworks/library/l-vim-script-1/index.html
http://www.thegeekstuff.com/2009/01/vi-and-vim-macro-tutorial-how-to-record-and-play/
https://majutsushi.github.io/tagbar/

For syntax highlighting, simply write: "Esc:syntax on" to activate the
builtin.

Error! Bad dkms.conf file after apt-get upgrade

[Larry Dighera]

Hello all,
After running 'apt-get install upgrade' the system reported the data below.
How can I overcome this issue?  

Is it just a matter of loading a proper dkms.conf file, perhaps from another 
Stretch installation, or is there an official dkms.conf file that I can 
download somewhere, or is it a matter of removing the dkms package and 
reinstalling it, or repairing/reinstalling it?

I am grateful for any assistance/insight into this issue you are able to 
provide.  ADVthanksANCE.
Best regards,Larry

===
Fri Aug 11 08:26:01 PDT 2017

Setting up linux-image-4.9.0-3-amd64 (4.9.30-2+deb9u3) ...
Progress: [ 89%]
/etc/kernel/postinst.d/dkms:
/usr/sbin/dkms: line 485: .: /var/lib/dkms/rtl8814/4.3.21/source/dkms.conf: 
cannot execute binary file
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 8
dpkg: error processing package linux-image-4.9.0-3-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for hicolor-icon-theme (0.15-1) ...
Progress: [ 90%]
Setting up git (1:2.11.0-3+deb9u1) ...
Progress: [ 92%]
Progress: [ 93%]
Setting up linux-headers-4.9.0-3-amd64 (4.9.30-2+deb9u3) ...
Progress: [ 95%]
/etc/kernel/header_postinst.d/dkms:
/usr/sbin/dkms: line 485: .: /var/lib/dkms/rtl8814/4.3.21/source/dkms.conf: 
cannot execute binary file
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 8
Failed to process /etc/kernel/header_postinst.d at 
/var/lib/dpkg/info/linux-headers-4.9.0-3-amd64.postinst line 11.
dpkg: error processing package linux-headers-4.9.0-3-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-4.9.0-3-amd64
 linux-headers-4.9.0-3-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)


Upgrade Debian system before continuing (apt-get install dist-upgrade) [Y/n]? ^[
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up linux-headers-4.9.0-3-amd64 (4.9.30-2+deb9u3) ...
Progress: [  0%]
/etc/kernel/header_postinst.d/dkms:
/usr/sbin/dkms: line 485: .: /var/lib/dkms/rtl8814/4.3.21/source/dkms.conf: 
cannot execute binary file
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 8
Failed to process /etc/kernel/header_postinst.d at 
/var/lib/dpkg/info/linux-headers-4.9.0-3-amd64.postinst line 11.
dpkg: error processing package linux-headers-4.9.0-3-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up linux-image-4.9.0-3-amd64 (4.9.30-2+deb9u3) ...
/etc/kernel/postinst.d/dkms:
/usr/sbin/dkms: line 485: .: /var/lib/dkms/rtl8814/4.3.21/source/dkms.conf: 
cannot execute binary file
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 8
dpkg: error processing package linux-image-4.9.0-3-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-headers-4.9.0-3-amd64
 linux-image-4.9.0-3-amd64
E: Sub-process /usr/bin/dpkg returned an error code 
(1)===

Re: Driver/firmware for Realtek RTL8814U WiFi USB Adapter?

[Larry Dighera]

On Fri, 7 Jul 2017 20:39:41 -0400, you wrote:

>Hi Larry,
>
>Sorry for sending you down a rabbit hole.  The reason the DKMS steps
>didn't work is that the git repository for the rtl8814au lacks the
>configuration file(s) for DKMS.  Specifically, if you check your logs,
>you'll see that if failed to locate DKMS.conf.  I thought it would work
>because the rtl8814au driver appears to be based off the driver here:
>https://github.com/gnab/rtl8812au.  That driver does have the
>configuration files to support DKMS (Makefile.dkms and dkms.conf).  I
>don't know enough about DKMS to modify the configuration files in the
>above repository to make it work with the rtl8814au git repository.
>
>Fortunately, you can still compile the package for your existing
>kernel.  The only downside of this step is that you will need to
>re-compile the drivers if you install a new kernel which is not ABI
>compatible.  For example, the current Stretch kernel for AMD64 is
>linux-image-4.9.0-3-amd64 (4.9.30-2+deb9u2).  Thus, it should work with
>any future kernel starting with linux-image-4.9.0-3, but if you see
>4.9.0-4, you would likely have to recompile.  I haven't actually tested
>this, but it's what I've read.
>
>In any case, since you've already installed the build dependencies, you
>just need to do the following:
>
>#Clone the git repository (again) - Might as well work from a fresh
>directory
>git clone https://github.com/astsam/rtl8812au.git
>cd rtl8812au
>
>#Compile driver for your hardware
>make RTL8814=1
>
>#Install Module
>make install
>
>#With Wifi adapter connected, load Module  (If this fails, reboot and it
>should load the correct module.)
>modprobe 8812au
>
>Regards,
>
>Jason
>

Hello Jason,

After spending way too much time attempting to install the Realtek
RTL8814 driver module with DKMS, I took your advice and successfully
built and loaded it with the commands you kindly provided above. 

My AMD_X86 system has an Intel 3168NGWG WiFi and BlueTooth PCIe card
installed, so I have been using it.  After loading the 8812au module,
WiFi will no longer connect while in CommandLine mode, but when
running in X11 mode, WiFi still works fine with the Intel adapter.  I
haven't tried removing the Intel iwiwfi module, as lsmod reported
three items associated with it, and I'm unfamiliar with that sort of
configuration.  I suspect removing the Intel iwiwfi module and loading
the 8812au module may overcome that issue.

The new device naming conventions are driving me mad.  I can no longer
'ls -l /dev/w*' to list the wireless devices, and don't know where to
find them anymore, although 'find' does help.  Unfortunately 'find'
didn't find a second (consecutively numbered) WiFi device, nor did
'ip' nor 'iwconfig'.  Of course the new 8812au USB adapter is still
listed in the 'lsusb' output as before loading the new module.  

So currently, while I now have the 8812au driver module active, I'm
still unable to use the new Comfast CF-917AC WiFi USB adapter
hardware, and without a device name for it, I'm at a loss to diagnose
the issue further.

Thank you for submitting the Feature Request to have the driver
included in the Debian package repository, and all your very detailed
and assistance.  

I'll attach a notes text file (kali_driver.txt) of related information
in the hope you may find it of interest.

Best regards,
Larry

http://git.kali.org/gitweb/?p=packages/realtek-rtl88xxau-dkms.git;a=summary

git clone git://git.kali.org/packages/realtek-rtl88xxau-dkms.git

Cloning into 'realtek-rtl88xxau-dkms'...
remote: Counting objects: 538, done.
remote: Compressing objects: 100% (332/332), done.
remote: Total 538 (delta 196), reused 536 (delta 196)
Receiving objects: 100% (538/538), 2.44 MiB | 1.56 MiB/s, done.
Resolving deltas: 100% (196/196), done.
warning: remote HEAD refers to nonexistent ref, unable to checkout.
---

See also: 
http://git.kali.org/gitweb/?p=packages/realtek-rtl88xxau-dkms.git;a=commit;h=becf0914a1def4ea55a475aa7325c60c64450ac1

http://git.kali.org/gitweb/?p=packages/realtek-rtl88xxau-dkms.git;a=blob;f=debian/realtek-rtl88xxau-dkms.dkms;h=0bf2e4bfdf3472da1fa915587fda4201ac0632b3;hb=becf0914a1def4ea55a475aa7325c60c64450ac1

dkms.conf 
PACKAGE_NAME="realtek-rtl88xxau"
PACKAGE_VERSION="#MODULE_VERSION#"
CLEAN="make clean"
BUILT_MODULE_NAME[0]=8812au
DEST_MODULE_LOCATION[0]="/updates"
MAKE[0]="'make' && 'make' RTL8814=1"
BUILT_MODULE_NAME[1]=8814au
DEST_MODULE_LOCATION[1]="/updates"
AUTOINSTALL="yes"


debian/rules
http://git.kali.org/gitweb/?p=packages/realtek-rtl88xxau-dkms.git;a=blob;f=debian/rules;h=62cd0ee2e90cd5777cfb9a100632ef8539f9d695;hb=becf0914a1def4ea55a475aa7325c60c64450ac1

   1 #!/usr/bin/make -f
   2 
   3 VERSION=4.3.21~20170330
   4 
   5 %:
   6 dh $@ --with dkms
   7 
   8 override_dh_dkms:
   9 dh_dkms -V $(VERSION)
  10 
  11 override_dh_fixperms:
  12 dh_fixperms
  13 find debian/realtek-rtl88xxau-dkms/usr/src -type f -exec chmod -x 
{} \;
 

Re: Driver/firmware for Realtek RTL8814U WiFi USB Adapter?

[Larry Dighera]

>On Wed, Jul 5, 2017 at 2:41 PM, Larry Dighera <ldigh...@att.net> wrote:
>
>> Which Debian Stretch package provides firmware for the Realtek
>> RTL8814U chip?  In particular, the Comfast CF-917AC 1750Mbps USB3
>> adapter: https://www.amazon.com/dp/B01B75MHR0 .
>>
>> Kali Linux supports the RTL8814 natively:
>> https://www.kali.org/news/kali-linux-20171-release/ .  Further, there
>> are some clues here: https://bugs.kali.org/view.php?id=3260
>> https://github.com/diederikdehaas/rtl8812AU
>> https://github.com/astsam/rtl8812au
>> https://github.com/lwfinger/rtlwifi_new
>>
>> But, I'm looking for an "official" Debian firmware package.
>>
>> I wasn't able to find the rt8814 mentioned here:
>> https://www.debian.org/distrib/packages nor here:
>> http://linux-wless.passys.nl/query_chipset.php?chipset=Realtek
>> nor here: https://wireless.wiki.kernel.org/en/users/drivers
>>
On Wed, 5 Jul 2017 18:57:44 -0400, Jason Wittlin-Cohen
<jwittlinco...@gmail.com> wrote:

>I have the Edimax EW-7822UAC (2x2 802.11ac) which uses the rtl8812AU
>chipset.  I can confirm that the firmware-realtek package does not contain
>support for the rtl8812AU chipset, and presumably also does not
>support the RTL8814U
>chipset.  Neither are listed on https://wiki.debian.org/rtl819x.  In
>contrast, Ubuntu and its derivatives, such as Mint, do package this
>driver.  For example, see
>https://packages.ubuntu.com/xenial/kernel/rtl8812au-dkms.
>
>Fortunately, I was able to compile and install the rtl8812AU driver from
>https://github.com/diederikdehaas/rtl8812AU without difficulty.  I have
>been using this wireless card on a desktop system with Stretch.  It has
>been reliable and I had no problem configuring it with networks running
>WPA2-PSK and WPA2-Enterprise (EAP-TLS).  I'm getting speeds around 300
>Mbit/sec @ 65-70 dbm when connected to a Ubiquiti AC-LR.  In contrast, Mint
>installed the driver for me without issue but had constant issues with
>EAP-TLS due to bugs in network-manager.
>

Hello Jason,

Thank you for the information you have provided.  

Is there a chance the rtl8814AU driver might be available as a backport?

I was hoping that I wouldn't have to compile the driver, but your experience
has left little doubt that it will be necessary.  Although I have
successfully built several Software Defined Radio applications, I've never
been successful in building drivers.  Will ModuleAssistant
<https://wiki.debian.org/ModuleAssistant> assist in building the driver?  Or
is there another "assistant" package that may be of help?  

Best regards,
Larry

Driver/firmware for Realtek RTL8814U WiFi USB Adapter?

[Larry Dighera]

Which Debian Stretch package provides firmware for the Realtek
RTL8814U chip?  In particular, the Comfast CF-917AC 1750Mbps USB3
adapter: https://www.amazon.com/dp/B01B75MHR0 .  

Kali Linux supports the RTL8814 natively:
https://www.kali.org/news/kali-linux-20171-release/ .  Further, there
are some clues here: https://bugs.kali.org/view.php?id=3260
https://github.com/diederikdehaas/rtl8812AU
https://github.com/astsam/rtl8812au
https://github.com/lwfinger/rtlwifi_new

But, I'm looking for an "official" Debian firmware package.  

I wasn't able to find the rt8814 mentioned here:
https://www.debian.org/distrib/packages nor here:
http://linux-wless.passys.nl/query_chipset.php?chipset=Realtek
nor here: https://wireless.wiki.kernel.org/en/users/drivers

Re: Remotely exploitable bug in systemd (CVE-2017-9445)

[Larry Dighera]

On Sat, 1 Jul 2017 16:36:41 -0400, you wrote:

>Howdy! CVE-2017-9445 is a remotely exploitable bug in systemd. It was
>first announced to the public about four or five days ago, not sure
>when it would have been announced to the security team.
>
>Am I correct in interpreting this:
>https://security-tracker.debian.org/tracker/CVE-2017-9445
>as meaning a fix to it still isn't in sid, and therefore is not
>yet in the process of percolating down to stretch?
>
>Is there a preferred way of temporarily mitigating the problem?
>Remote exploitation that you can trigger by forcing a program to DNS
>queries seems kind of bad.
>
>Perry


https://security-tracker.debian.org/tracker/CVE-2017-9445
NameCVE-2017-9445
Description In systemd through 233, certain sizes passed to
dns_packet_new in systemd-resolved can cause it to allocate a buffer
that's too small. A malicious DNS server can exploit this via a
response with a specially crafted TCP payload to trick
systemd-resolved into allocating a buffer that's too small, and
subsequently write arbitrary data beyond the end of it.

Notes:
[stretch] - systemd  (Minor issue, systemd-resolved not
enabled by default)

Re: [Stretch] apt-get has no updates?

[Larry Dighera]

On Fri, 30 Jun 2017 16:31:37 -0400, you wrote:

>> Someone else mentioned unattended upgrades, which is a thing I have
>> never used, and which is also a thing I would disable if I ever found
>> it running.  But that's just me.
>
>I would like to do that but don't know how. Anyone caring to enlighten 
>me without me having to bother poor old Mr. Google yet again - it would 
>be appreciated. :)

Perhaps you'll find this useful:

===
# auto-update-on-off.sh This script will enable and disable
unattended-updates
#
# LGD: Thu Jun  1 15:00:09 PDT 2017
#

[[ $# != 1 ]] && echo -e "\n\t\"$@\" Unknown\n\tUsage: $0 
\n\t\tWhere:  e = Enable\n\t\t\td = Disable\n\t\t\ts = Status" >&2 &&
exit 1 

FILNAM="/etc/apt/apt.conf.d/10periodic"
OFF="APT::Periodic::Unattended-Upgrade \"0\";" 
ON="APT::Periodic::Unattended-Upgrade \"1\";" 

status(){   # Get current status
  if [[ -s "$FILNAM" ]] ;then   # Does file exist with >0 file
length?
[[ $(grep -qs 1 "$FILNAM") ]] && STATUS=Enabled
[[ $(grep -qs 0 "$FILNAM") ]] && STATUS=Disabled
  else
STATUS="Not Configured (Disabled)"
  fi
  return $STATUS
}


case $1 in 
  -[sS]*) status; echo "Current $0 status: $STATUS">&2;exit 0   ;;
  -[dD]*) echo "$OFF" >/etc/apt/apt.conf.d/10periodic   ;;
  -[eE]*) echo "$ON"  >/etc/apt/apt.conf.d/10periodic   ;;
  *) echo -e "\n\t\"$@\" Unknown\n\tUsage: $0  \n\t\tWhere:  e
= Enable\n\t\t\td = Disable\n\t\t\ts = Status" >&2 && exit 1 
esac  

=

Re: Debian 9 - eGalax-Touch

[Larry Dighera]

On Wed, 21 Jun 2017 18:43:11 +0200, you wrote:

>Can somebody tell me, what I have to do, to get this device useable?

Perhaps there's a clue here: http://www.eeti.com.tw/drivers_Linux.html

Re: [Stretch]Typing ""clear" on terminal restricts the scrollback to only a screenful

[Larry Dighera]

On Tue, 20 Jun 2017 17:20:25 +0530, you wrote:

>Any pointers?

Try: tput clear

Re: Discovering alternative commands

[Larry Dighera]

On Thu, Jun 01, 2017 at 07:22:36AM -0500, Richard Owlett wrote:
> 1. what other commands should I look at?
Perhaps you'll find something useful in this little script I wrote:
# show_drives.sh    Display Labels and UUIDs of media
# LGD: Wed May 24 06:35:20 PDT 2017
# Re-write Fri Jun  9 04:31:03 PDT 2017
# Written as an exercise in shell script programming.  ldigh...@att.net 
#

trap "setterm -foreground white;echo;exit 1" ERR INT QUIT EXIT TERM        # 
trap -l will display signals (bash only)

set "lsblk -f" "lsblk -a" "fdisk -l" "findmnt -A" "findmnt -D" "findmnt -D -A" 
"df -Th"    # Put commands in the environment as positional parameters to 
execute

# Prompt user for input
PRMPT="Enter to continue [Q]: "
WAIT(){
  ### ksh 'read' syntax: ksh man page line 2227 (vname?prompt)  
  [[ $(echo $SHELL |grep ksh) ]] && READ="read -n 1 REPLY?\"${PRMPT}\""        
# ksh read syntax
   bash 'read' syntax: bash man page line 4335 (-p prompt)  
  [[ -n $BASH ]] && READ="read -n 1 -r -p \"${PRMPT}\""                # bash 
read syntax (-r, no varname)
  eval ${READ}                                    # Issue prompt for next page
  [[ $REPLY != [Qq]* ]] && setterm -foreground white && return            # 
Return to caller
  [[ $REPLY == [Qq]* ]] && setterm -foreground white                # User 
request to quit received
  echo;exit
}

# Dynamically generate header and footer lines equal to the length of the 
longest line of the output of the current command with the command-name 
centered in the middle of the header line
GENLIN(){
  CMDLEN=$(echo "$1"|wc -m)                            # The length of the 
current command
  LEN=$(eval "$1"|wc -L)                            # The length of the longest 
line generated by the current command passed as an argument to this function
  MIDLIN=$((( ($LEN / 2) - $(echo $1|wc -m)+2 )))                # The 
mid-point of the line at which to place the current command in the header
  [[ $2 != "end" ]] && LEN=$((( $LEN - $CMDLEN )))                # Deduct the 
length of the command line from the header length for footer
  for i in $(seq $LEN) ;do                            # Loop through the 
commands
    echo -e "=\c"                                # Print each line characters
    [[ $i == $MIDLIN && $2 != "end" ]] && echo -e " $1 \c"    # Print the 
command-name in the middle of the header line
  done
  echo
}

CURROW=$(stty -a |grep rows|awk -F \; '/rows/ {print $2}'|tr -d '[a-z A-Z]')    
# Get the number of terminal rows/lines (cursor row position at bottom of 
screen)
[[ -n $BASH ]] && CURROW=$((( $CURROW - 1 )))                    # fucking bash 
:-)
while : ;do
  GENLIN "$1"                                    # Print output header line 
  eval "$1"                                    # Print command output
  GENLIN "$1" "end"                                # Print output footer line
  echo
  shift                                        # Get the next command to run
  [[ -z $1 ]] && { echo;exit ;}                            # Exit when command 
list is exhausted
  setterm -foreground green;WAIT;setterm -foreground white            # Color 
prompt for user input
  tput cup $((($CURROW - 1))) 0                            # Over-write the 
prompt line
done

exit 0



show_drives.sh
Description: application/shellscript

Re: How to Install to HDD from LIVE USB Flash Drive?

[Larry Dighera]

On Wed, 24 May 2017 14:43:16 +0200, err...@free.fr wrote:

>On 05/24/2017 02:16 PM, Larry Dighera wrote:
>> I just burned Debian-live-testing-amd64-lxde.iso
>..
>> Is anyone able to offer a pointer to the method of installing to HDD from
>> the live USB image?
>> 
>> ADVthanksANCE 
>> 
>Hello larry
>
>you need to boot from your usb stick:
>
>like this:
>https://www.debian.org/releases/stable/amd64/ch05s01.html.en#usb-boot

Hello,

Thank you for your kind response to my query.  

I did attempt to install from another Live image, but it hung while
attempting to install dual-boot as I recall.

The good news is, that installing 'firmware-testing-amd64-DVD-1.iso'
from this page
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-dvd/
worked perfectly.  I chose the Graphical Custom Install option, and
was able to specify an unallocated partition on my SSD for Stretch,
and the installer was smart enough to use the swap partition on
another drive used by an earlier Jessie installation.  

Best regards,
Larry

How to Install to HDD from LIVE USB Flash Drive?

[Larry Dighera]

I just burned Debian-live-testing-amd64-lxde.iso
https://cdimage.debian.org/mirror/cdimage/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-lxde.iso
from
https://cdimage.debian.org/mirror/cdimage/weekly-live-builds/amd64/iso-hybrid/
to a 16GB SD card, and was hoping to be able to install it on a partition on
the m.2 SSD next to dual-boot Win10. 

I read on one of the Debian.com pages
https://www.debian.org/CD/live/index.en.html , that there's supposed to be a
"launcher on the desktop that can be used to install while running the live
image." Unfortunately, I didn't find one.

I Googled, but was unable to find any information on how to install from the
live system.

Is anyone able to offer a pointer to the method of installing to HDD from
the live USB image?

ADVthanksANCE 

Re: Questions after doing update and upgrade on Stretch

[Larry Dighera]

On Sun, 21 May 2017 09:35:55 -0500, you wrote:

>> Check with blkid that sda5 has this UUID.
>
>Gparted reports that UUID for /dev/sda5

'lsblk --fs' provides a human-friendly "graphical" tree view that
includes UUID and LABEL of each partition on each disk.

Re: Bug#860543: 'Gave up waiting for suspend/resume device'

[Larry Dighera]

Hello Ben,

Thank you for your prompt response to my inquiry, and your kind assistance.

My comments in-line below:


On Sat, 13 May 2017 00:40:47 +0100, Ben Hutchings <b...@decadent.org.uk>
wrote:

>On Fri, 2017-05-12 at 21:26 +0000, Larry Dighera wrote:
>> Dear Mr. Hutchings,
>> Todays update appears to have caused my Debian Stretch Linux system
>> to fail to boot with this error message: 
>> 
>>     "Gave up waiting for suspend/resume device..."
>
>That (by itself) does not indicate a boot failure; it only means that
>resume from disk (hibernation) won't work.  
>

Previous to the update, hibernation worked.  

>
>Do any messages appear afterward?
>

Yes.  There is a bit after that.

"Gave up waiting for root file system device"
or

"Gave up waiting for suspend/resume device"

Then some suggestions presumably about how to address the issue:

"Boot Args. Cat /proc/cmdline"
something about "check root delay" perhaps not long enough... 
missing modules..."
"UUID 2d182fb2... doesn't exist."

>
>> The Grub menu is still accessible, but I'm clueless how to return the
>> system to operational status.
>> Please provide complete step-by-step instructions to restore
>> successful system booting through the Grub menu.  
>
>One of the 'recovery mode' item under Advanced Options will enable
>verbose logging to the screen and will perhaps get you to a shell.
>

Unfortunately, selecting the 'recovery mode' grub menu option is useless.
There is something about 'busybox' and a '(initramfs)' prompt(?), but the
system fails to respond to keyboard or mouse input at that point.  So
'recovery mode' appears to be useless.

However, by entering 'e' at the grub menu, I can edit the 'command line.  At
your suggestion above, I changed 'quite' to 'verbose', but nothing seems to
have changed when rebooting.

By entering 'c' at the grub menu, I can get a 'Grub>' prompt from which I am
able to 'ls' and 'cat' and probably a hundred or more other commands that
can be displayed with the 'help' command.  It is necessary to enter 'set
pager=1' to see them before they scroll off screen.  Entering 'help
' provides some additional terse (cryptic) information about the
command.

I don't find any sort of editing command, and redirection '>>' attempts
fail.  

Can you give me a clue to necessary commands to go about returning my system
to operational status from this 'Grub>' prompt?  

>
>In any case, you should open a *new* bug report rather than appending
>to this one.
>
>Ben.

It was not my intent to open a bug report at all.  I apologize for any issue
I may have caused.

In the information at this link:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860543 you stated:

"Is there a resume device specified in
/etc/initramfs-tools/conf.d/resume and does it exist?"

I found /etc/initramfs-tools/conf.d/resume.  It contains the single entry:

"RESUME=UUID=f5aa19f3-7707-4bab-bd18-15d6124a0147"

I have no idea where to find that file/device/?.

I just want my system to boot again.  Please assist me in reaching that
goal.

Best regards,
Larry

PS:
On that page, you also stated: 

> ...
> /etc/initramfs-tools/conf.d/resume exists and did not contain a valid
> device. The problem still persists, if I enter a valid UUID, or remove
> the file.

This issue should only affect systems that have a nonexistent device
specified in the configuration, or that have a swap device that isn't
suitable as a resume device because it's not set up early enough.
Previously we would only look for the resume device once, so this
didn't hurt, but it also meant that resume was broken on some systems.

Unfortunately, as you've seen, there isn't currently a way to
completely disable use of a resume device when building the initramfs. 
It *is* possible to do so at boot time (kernel parameter 'noresume' or
'resume=').

I think I need to add:

- The option to disable use of a resume device in the configuration
  (e.g. RESUME=none)
- A warning on upgrade if the configured resume device doesn't exist or
  is unlikely to be available

Ben.

Is that what I need to do?  If so, please provide step-by-step keystrokes I
need to enter at the "Grub>" prompt. 

'Gave up waiting for suspend/resume device'

[Larry Dighera]

Dear Mr. Hutchings,
Todays update appears to have caused my Debian Stretch Linux system to fail to 
boot with this error message: 

    "Gave up waiting for suspend/resume device..."
The Grub menu is still accessible, but I'm clueless how to return the system to 
operational status.
Please provide complete step-by-step instructions to restore successful system 
booting through the Grub menu.  

As the eMMC flash memory on which the Linux system resides in soldered to the 
PC board, mounting it on another system for editing is not feasible.  

REF: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860543

Thank you for your assistance.
Best regards,Larry Dighera

Console fonts SOLVED :-)

[Larry Dighera]

I gave up on Jessie, and installed Stretch as you and others in the 
debian-users mailing list advised. 

Installing Debian Stretch (testing) from this link: 

 on the Udoo X86 required placing the rtl8168g-2.fw driver in the root 
directory of the USB ISO installation medium to support the Edimax Nano 150Mbps 
Wireless 802.11b/g/n USB Adapter. 
The driver was downloaded from this page:
 https://packages.debian.org/source/stretch/firmware-nonfree
  
http://http.debian.net/debian/pool/non-free/f/firmware-nonfree/firmware-nonfree_20161130.orig.tar.xz

The specific 'rtl8168g-2.fw' driver required was extracted from the compressed 
tar archive with 7-Zip.

Stretch runs great! 

Re: Console fonts

[Larry Dighera]

On Tue, 2 May 2017 20:22:01 -0500, David Wright <deb...@lionunicorn.co.uk>
wrote:

>On Tue 02 May 2017 at 12:20:01 (-0700), Larry Dighera wrote:
>
>> Yes.  It's a new single-board computer platform that began shipping ~April
>> 14, 2017.  I can personally confirm that Tails Linux X11 runs fine on this
>> platform, and the manufacturer (Udoo) claims to have successfully installed
>> Debian.  
>[...]
>> Given the Udoo team claims to have installed Debian on their hardware, and
>> Tails Linux runs on it, I'd prefer to sort out the issues, and see if I
>> (we?) can effect a useable system.
>
>I'm sorry if everyone knows which Debian (jessie, stretch, sid)
>and kernel version that the Udoo team installed. My deduction
>from the lines above was that the OP ran Tails¹, not that the
>Udoo team ran Tails.
>

That is correct.  I apologize for any ambiguity.

>
>Hence my thinking that there might be a reference to what the
>Udoo team installed that I (and perhaps others) hadn't seen.
>Sorry to mystify anyone.
>
>¹
>http://distrowatch.com/table.php?distribution=tails
>
>Cheers,
>David.

While I am currently unable to locate the post asserting the Udoo team
successfully installed Jessie, this post from a Udoo user alludes to a
successful Jessie install:
http://www.udoo.org/forum/threads/no-audio-output-on-linux-over-hdmi.6803/

On the other hands, there is a user also encountering the blank-screen
syndrome with Jessie on the Udoo X86 platform:
http://www.udoo.org/forum/threads/linux-xfce-debian-jessie-blank-screen.6854/

And another who found stretch more stable than Jessie:
http://www.udoo.org/forum/threads/debian-jessie-linux-os-installation.6819/#post-26261

I believe this may have been where I saw the mention of Debian on the Udoo
X86 platform: http://www.udoo.org/docs-x86/Software_&_OS_Distro/Linux.html

When/if I receive a response to my inquiry from the Udoo support team
regarding which Jessie distribution they installed, I'll post it here.

Larry

PS: It is the integrated Arduino hardware and very low power requirement
that make this new platform interesting to me for portable/battery-power
use.  

Re: Console fonts

[Larry Dighera]

On Tue, 2 May 2017 18:46:34 -0500, David Wright <deb...@lionunicorn.co.uk>
wrote:

>On Tue 02 May 2017 at 12:20:01 (-0700), Larry Dighera wrote:
>> On Sun, 30 Apr 2017 21:34:14 -0400, Felix Miata <mrma...@earthlink.net> 
>> wrote:
>> >
>> >Even if OP can get the ttys working to his liking, I still think it's very
>> >likely a lost cause trying to use Jessie on his hardware. Stretch is very 
>> >near
>> >ready to release, and probably OP's better next move.
>> >
>> 
>> In this message thread:
>> http://www.udoo.org/forum/threads/debian-jessie-linux-os-installation.6819/
>> others have also suggested Stretch.  I looked at the existing bugs:
>> https://bugs.debian.org/release-critical/other/testing.html
>> https://bugs.debian.org/release-critical/
>> 
>> Release-critical bugs status
>> 
>> Tue May 2 17:00:00 UTC 2017
>> 
>> Total number of release-critical bugs: 1649
>> Number that have a patch: 271
>> Number that have a fix prepared and waiting to upload: 38
>> Number that are being ignored: 78
>> Number concerning the current stable release: 699
>> Number concerning the next release: 149
>> 
>> 
>> The reason for installing Debian was because I have been impressed with its
>> stability and few update issues compared to other Linux flavors I've used,
>> so I was/am reluctant to overwrite Jessie with Stretch.
>
>Scaling up the words of that ridiculous advert:
>699 (stable/jessie) is greater than 149 (testing/stretch).
>
>But, seriously, those figures need a lot of interpreting.
>

Are you intimating that the current stable Debian release (Jessie) contains
~4.5 times the number of release-critical bugs of stretch!?  

>
>> Given the Udoo team claims to have installed Debian on their hardware, and
>> Tails Linux runs on it, I'd prefer to sort out the issues, and see if I
>> (we?) can effect a useable system.
>
>Reference? It's worth posting exactly what they installed;
>distribution, kernel version, etc.
>

I have submitted that question to the Udoo support team, and am awaiting a
response. 

Also, there is a post here
http://www.udoo.org/forum/threads/debian-jessie-linux-os-installation.6819/#post-26261
that indicates that "Debian Stretch
(debian-stretch-DI-rc3-amd64-xfce-CD-1.iso from
[https://cdimage.debian.org/mirror/cdimage/stretch_di_rc3/amd64/iso-cd/]) is
working much better for me than Jessie..."

>
>Cheers,
>David.

Thank you for your interest in this issue, and your kind support.

Best regards,
Larry

Re: Console fonts

[Larry Dighera]

Hello Felix,

Thank you for your informative response to my issue.

My comments in-line below:


On Sun, 30 Apr 2017 21:34:14 -0400, Felix Miata <mrma...@earthlink.net>
wrote:

>Larry Dighera composed on 2017-04-30 16:40 (UTC-0700):
>[...]
>Previously, in OP https://lists.debian.org/debian-user/2017/04/msg00534.html :
>http://www.udoo.org/
>***
>   Without anything there indicating date of release, that URI strongly 
> suggests
>to me nevertheless that his hardware is newer than Jessie can be expected to
>support.
>

Yes.  It's a new single-board computer platform that began shipping ~April
14, 2017.  I can personally confirm that Tails Linux X11 runs fine on this
platform, and the manufacturer (Udoo) claims to have successfully installed
Debian.  

Specs are here: http://www.udoo.org/new-resources-udoo-x86/
Intel® Celeron® N3160, Quad Core @1.6GHz (Turbo Boost 2.24GHz), 2MB
Cache, 6W TDP.
Integrated Intel® HD Graphics controller
Three independent display support
HW decoding of HEVC(H.265), H.264, MPEG2, MVC, VC-1, VP8, WMV9,
JPEG/MJPEG formats
HW encoding of H.264, MVC and JPEG/MPEG formats
Video Interfaces
HDMI connector
2 x miniDP++ connectors
Video Resolution
Up to 3840 x 2160 24bpp @ 30Hz, 2560 x 1600 24bpp @60Hz
CIR (Consumer InfraRed) Sensor
Arduino 101 compatible shield
Integrated 6-axis combo sensor with accelerometer and gyroscope


Here is data from Debian Jessie on the Udoo X86 platform:

--- System Information
Kernel name:Linux 
Network node Hostname:  UdooX86Debian 
Kernel release: 3.16.0-4-amd64 
Kernel version: #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
Machine hardware name:   
Operating system:   

--- OS Release ---
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/;
SUPPORT_URL="http://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

  CPU Information -
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):4
On-line CPU(s) list:   0-3
Thread(s) per core:1
Core(s) per socket:4
Socket(s): 1
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 76
Model name:Intel(R) Celeron(R) CPU  N3160  @ 1.60GHz
Stepping:  4
CPU MHz:   499.800
CPU max MHz:   2332.3999
CPU min MHz:   499.8000
BogoMIPS:  3199.86
Virtualization:VT-x
L1d cache: 24K
L1i cache: 32K
L2 cache:  1024K
NUMA node0 CPU(s): 0-3
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 76
model name  : Intel(R) Celeron(R) CPU  N3160  @ 1.60GHz
stepping: 4
microcode   : 0x40a
cpu MHz : 499.800
cache size  : 1024 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 11
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand
lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept
vpid tsc_adjust smep erms
bogomips: 3199.86
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 76
model name  : Intel(R) Celeron(R) CPU  N3160  @ 1.60GHz
stepping: 4
microcode   : 0x40a
cpu MHz : 499.800
cache size  : 1024 KB
physical id : 0
siblings: 4
core id : 1
cpu cores   : 4
apicid  : 2
initial apicid  : 2
fpu : yes
fpu_exception   : yes
cpuid level : 11
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand
lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept
vpid tsc_adjust smep erms
bogomips: 3199.86
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor   : 2
vendor

Re: Console fonts, was Re: Jessie for Udoo X86?

[Larry Dighera]

Hello David,

Thank you very much for taking the time to educate me about this display
issue.

My comments in-line below:


On Sun, 23 Apr 2017 22:19:47 -0500, David Wright <deb...@lionunicorn.co.uk>
wrote:

>On Sun 23 Apr 2017 at 18:55:03 (-0700), Larry Dighera wrote:
>
>> I'd like to have more lines/rows and columns on the console tty.  I've read
>> that 'vidcontrol' may do what I want, unfortunately 'apt-cache show
>> vidcontrol' reports that it is virtual (unavailable).  
>> 
>> I am grateful for any clues you may be able to provide.
>
>Best to start a new thread with a new subject, but anyway…
>
>The Debian Way to set a default font for dmesg output, login prompt,
>etc is (I think) to edit /etc/default/console-setup
>I like Terminus fonts (package console-setup-linux, I think),
>so I have:
>
>ACTIVE_CONSOLES="/dev/tty[1-6]"
>CHARMAP="UTF-8"
>CODESET="Lat15"
>#FONTFACE="Fixed"
>FONTFACE="Terminus"
>FONTSIZE="10x20"
>#FONTSIZE="12x24"
>#FONTSIZE="14x28"
>#FONTSIZE="16x32"
>VIDEOMODE=
>
>in there, with various sizes available.
>

The default console display size is 80 columns by 25 rows.  

Setting FONTFACE="Terminus" and FONTSIZE="12x6", in the hope reducing the
font size from 10x20 would result in getting more characters on the console
display, I found it didn't change anything.  I presume the 12 in 12x6 refers
to the height of the character matrix block, and the 6 the width, so if
that's correct it should permit about three times as many characters in a
row.  

I read the console-setup manual pages, and noticed SCREEN_WIDTH and
SCREEN_HEIGHT mentioned, so I put SCREEN_WIDTH="50" in the
/etc/default/console-setup file as a test to see if my edits were able to
effect some viable change in the console display.  Upon reboot, indeed the
screen was set to 50 columns, so I did a 'stty columns 80', and it was
restored to the default 80x25 size.

I suspect the failure to see any change when specifying FONTSIZE="12x6" was
probably a result of a limitation of the Udoo X86's Intel HD-graphics
display hardware limitations or the BIOS or something.

I found that 'setupcon' would cause the system to re-read the
/etc/default/console-setup file, so I could test edits without rebooting.   

The 'setfont' command does appear to be an alternate method of loading
console fonts.  But, it's difficult to know what valid arguments might be
for my system.

I tried the 'resizecons' command with -lines 132, and indeed there was some
change, however the screen was unreadable.  The resizecons man page is very
terse.  

So, after much experimentation and frustration, I'm afraid I've failed to
increase the amount of information that can be displayed on the console
screen.  Oh well...  

I am very grateful for your kind assistance, David.  And I'm willing to keep
trying if you are.  :-)



>
>However, I prefer using aliases like:
>
>alias my-font-tiny="setfont Lat15-Terminus12x6"
>alias my-font-small="setfont Lat15-Terminus14"
>alias my-font-medium="setfont Lat15-Terminus20x10"
>alias my-font-large="setfont Lat15-Terminus24x12"
>alias my-font-huge="setfont Lat15-Terminus28x14"
>alias my-font-vast="setfont Lat15-Terminus32x16"
>
>because you can then have different font sizes on each VC.
>I also have a bash function to choose an arbitrary font:
>
>function my-font-usr-share-consolefonts {
>[ -z "$1" ] && printf '%s\n' "Usage: $FUNCNAME 
> /usr/share/consolefonts/.psf.gz
>sets the specified font on the current VC.
>The command name serves as a reminder of the fonts' location.
>Use filename-completion to specify the appropriate filename.
>Redundant elements of the filename are stripped out before use.
>Typically, filenames start Lat15- or Uni." >&2 && return 1
>local FILENAME="$(basename "$1")"
>setfont "${FILENAME%%.*}"
>}
>
>Typing my-font reminds me of the name of the command,
>and the name of the command reminds me of the path to type in.
> then lists the font files to use filename completion on.
>
>Cheers,
>David.

Thanks for that, but I'm not there yet.  :-)

Apparently it's possible to do something similar by creating additional
/etc/default/console-setup files with filenames e.g. console-setup-small to
enable setfont to load alternate console line and column setups also.

Re: Jessie for Udoo X86?

[Larry Dighera]

Below are the lightdm and Xorg logs from my Debian Jessie install that
crashes when attempting to launch X11.

In particular, the "[  1983.306] (II) VESA(0): Bad V_BIOS checksum" message
in the Xorg log is troubling. 

Is this canonical evidence of hardware corruption?

== LIGHTDM LOG ==
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=3271
[+0.00s] DEBUG: Loading configuration dirs from
/usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from
/usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from
/etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.01s] DEBUG: Registered seat module xremote
[+0.01s] DEBUG: Registered seat module unity
[+0.01s] DEBUG: Registered seat module surfaceflinger
[+0.03s] DEBUG: Adding default seat
[+0.03s] DEBUG: Seat: Starting
[+0.03s] DEBUG: Seat: Creating greeter session
[+0.03s] DEBUG: Seat: Creating display server of type x
[+0.04s] DEBUG: Using VT 7
[+0.04s] DEBUG: Seat: Starting local X display on VT 7
[+0.04s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.05s] DEBUG: DisplayServer x-0: Writing X server authority to
/var/run/lightdm/root/:0
[+0.05s] DEBUG: DisplayServer x-0: Launching X Server
[+0.05s] DEBUG: Launching process 3275: /usr/bin/X :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.05s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.05s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.05s] DEBUG: Registering seat with bus path
/org/freedesktop/DisplayManager/Seat0
[+0.06s] WARNING: Error getting user list from org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
[+0.06s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.13s] DEBUG: User larry added

== X.ORG LOG ==
[  1983.182]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[  1983.182] X Protocol Version 11, Revision 0
[  1983.182] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[  1983.182] Current Operating System: Linux UdooX86Debian 3.16.0-4-amd64 #1
SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64
[  1983.182] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64
root=UUID=f0748180-a596-4f02-85d8-34b09b57cb42 ro quiet
[  1983.183] Build Date: 11 February 2015  12:32:02AM
[  1983.183] xorg-server 2:1.16.4-1 (http://www.debian.org/support)
[  1983.183] Current version of pixman: 0.32.6
[  1983.183]Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[  1983.183] Markers: (--) probed, (**) from config file, (==) default
setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1983.184] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 27 09:10:40
2017
[  1983.185] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1983.190] (==) No Layout section.  Using the first Screen section.
[  1983.190] (==) No screen section available. Using defaults.
[  1983.190] (**) |-->Screen "Default Screen Section" (0)
[  1983.190] (**) |   |-->Monitor ""
[  1983.193] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[  1983.193] (==) Automatically adding devices
[  1983.193] (==) Automatically enabling devices
[  1983.193] (==) Automatically adding GPU devices
[  1983.193] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not
exist.
[  1983.193]Entry deleted from font path.
[  1983.194] (==) FontPath set to:
   /usr/share/fonts/X11/misc,
   /usr/share/fonts/X11/100dpi/:unscaled,
   /usr/share/fonts/X11/75dpi/:unscaled,
   /usr/share/fonts/X11/Type1,
   /usr/share/fonts/X11/100dpi,
   /usr/share/fonts/X11/75dpi,
   built-ins
[  1983.194] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1983.194] (II) The server relies on udev to provide the list of input
devices.
   If no devices become available, reconfigure udev or disable
AutoAddDevices.
[  1983.194] (II) Loader magic: 0x7f66a0513d80
[  1983.194] (II) Module ABI versions:
[  1983.195]X.Org ANSI C Emulation: 0.4
[  1983.195]X.Org Video Driver: 18.0
[  1983.195]X.Org XInput driver : 21.0
[  1983.195]X.Org Server Extension : 8.0
[  1983.199] (--) PCI:*(0:0:2:0) 8086:22b1:8086:7270 rev 53, Mem @
0x9000/16777216, 0x8000/268435456, I/O @ 0x2000/64
[  1983.201] (II) LoadModule: "glx"
[  1983.204] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1983.234] (II) Module glx: 

Re: Jessie for Udoo X86?

[Larry Dighera]

David,

Thank you for you great response to my inquiry.  Very much appreciated.

My comments in-line below:


On Thu, 20 Apr 2017 14:14:40 -0500, David Wright <deb...@lionunicorn.co.uk>
wrote:

>On Thu 20 Apr 2017 at 07:11:53 (-0700), Larry Dighera wrote:
>
>> What I have discovered thus far, is that Debian wants to launch X11 by
>> default, instead of the command line UI.  That appears to result in a black
>> screen with a frozen system.  
>> 
>> At this point, I have no idea of the correct way to boot to the command line
>> interface, so I temporarily renamed lightdm, and now it boots to the command
>> line interface apparently after X11 fails to launch.  So, it appears that it
>> is X11 that has possible issues with the hardware or is misconfigured.
>> Perhaps there is something in X11's /var/log file that will provide a clue
>> about why it was failing to successfully launch.
>> 
>> So, it appears that grub is correctly configured after all.  
>> 
>> What is the correct way to configure the system to boot to the command line
>> UI instead of X11?  Do I need to edit things, or add files to, /etc/rc.d
>> someplace?  Or is there a higher-level way to tell systemd that I prefer to
>> manually launch X11?  
>
>For jessie/systemd,
>
># systemctl set-default multi-user.target
>
>and, to revert,
>
># systemctl set-default graphical.target
>

That worked perfectly.  Thank you very much.

>
>Removing the display manager was, I think, the old way.
>Not installing one, OTOH, is still the normal way if
>you don't want a DE (like me).
>
>> I'm aware that running the startx script is a reasonable way to launch X11
>> when I want it, but I'll have to diagnose its issue(s) first.  My past
>> familiarity with AT Unix from the early '80s through the '90s was pre-X11,
>> so I'm going to have to learn how to administrate X11 now I suppose.  
>> 
>> I sincerely appreciate your kind efforts in guiding me.  I gives me the
>> motivation to continue spending the time to get Jessie up on the new Udoo
>> X86 platform.
>
>There are several recent threads in this list about getting the
>right video drivers and X servers installed. Most of it goes
>over my head because my hardware is so old.
>
>Cheers,
>David.

I'll have to search the list archives.  Thank you for the pointer.


I'd like to have more lines/rows and columns on the console tty.  I've read
that 'vidcontrol' may do what I want, unfortunately 'apt-cache show
vidcontrol' reports that it is virtual (unavailable).  

I am grateful for any clues you may be able to provide.

Best regards,
Larry

Re: Jessie for Udoo X86?

[Larry Dighera]

On Tue, 18 Apr 2017 08:30:00 +, GiaThnYgeia
<giathnyg...@openmailbox.org> wrote:

>
>Larry Dighera:
>> I found the 'debian-8.7.1-amd64-DVD-1.iso' image here:
>> <http://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/>, burned it to
>> SD card in a USB reader with Rufus <https://rufus.akeo.ie/>, and booted it
>> from USB on the Udoo X86 Advanced hardware (Intel quad-core Celeron N3160
>> 2.24 GHz & Intel® Quark SE core 32 MHz plus 32-bit ARC core 32 MHz, Intel HD
>> Graphics 400 Up to 640 MHz 12 execution units, 4 GB DDR3L Dual Channel RAM
>> and 32GB eMMC Storage). 
>
>The link I sent you was for live versions where a complete Debian
>installation boots up (if it is possible based on the hardware) which is
>a very good indication that your installation will act just like it.
>You can select any desktop and then switch and install any desktop you
>like from the system once it is running.  I always use lxde as it is
>lean and mean.  This live version includes the debian installer which
>you can reboot and run from scratch or run it within the live debian
>system.  I prefer to reboot and run the installer alone after I have
>made sure live runs fine.  This gives the installer maximum resources
>and there are less things to confuse it.  You see from live when grub is
>installed it picks up the live drive as one of the installed systems.
>You have to keep an eye on what you select on the grub installation.
>But this would be a small problem, having an invalid boot option on your
>grub.
>
>> I selected the GUI Install from the menu, and all proceeded remarkably fast
>> and smooth without a hitch (except the WiFi, but gigabit Ethernet enabled
>> downloading all required additional files) until the last when it came to
>> grub.  
>
>Don't get me started down that path ;)
>
>> The installer advised that it had detected another OS being installed, and
>> presented me with a few choices to which I wasn't sure of the correct one,
>> so I took the default.  That must have been wrong, as now Debian won't boot
>> with grub from the eMMC "Hard Drive."  I'm not at all familiar with grub.
>
>Were you aware that there was an installed system on that disk and what
>it is?  Is it now an option on the grub boot-up screen? Remember that if
>you move the arrow up and down within the first 5" the default autostart
>that is timed to 5" is deactivated and you now have time to study it.
>Your first option on the base screen should be the debian you installed.
> The second should be for recovery which opens up a second screen where
>recovery is the 2nd option.  Is that what you used?
>Then on the base screen you should have 3 lines of memtest options, and
>at the bottom the "other" system that was previously installed.  It may
>be freedos or something factory???
>
>> I can boot into recovery mode though, and from the command line it appears
>> the install was successful.  So I'm close, but don't know exactly how to
>> proceed to make it bootable.
>
>In order to get to the grub part of the installation the system was
>completely installed and it is there.  There is an option to install
>grub to handle booting of all systems on the drive (possibly sda) and/or
>the partition itself where Debian was installed in which case it makes
>the partition bootable.  I assume the default is the first.
>
>> Any clues sincerely appreciated.
>
>When you pick the first option of Debian to boot, what do you see on the
>screen?  

It happens very quickly.  There is a brief flash of color, and perhaps a few
lines of text, then an interminable black screen with no response to
keyboard/mouse input.

>Lines of white text running some green and maybe red stuff?
>If it is all green you are in good shape, if it is red you have to
>concentrate on that first red tag and tell us what it says.
>

I'm familiar with the dmesg output at boot time.  I see that when I choose
to boot into recovery mode from the grub menus.  When the scrolling text
stops, I'm left with what I thought was a frozen screen, but it turns out to
be login, without a prompt, waiting for me to provide the root password.
Once I submit the root password, I have a command line interface to a
reasonably functional Debian system.

>
>Again, if there was a hardware issue the live system would have
>identified and displayed what the obstacle was.  Possibly you have to go
>into recovery, edit the sources (/etc/apt/sourced.list) and add "main
>contrib non-free" to where it says "main" if such firmware exist.  Then
>$apt update, $apt upgrade but then you have to know what you are missing
>to find the appropriate package to add if it exists.
>

What I 

Re: Jessie for Udoo X86?

[Larry Dighera]

On Tue, 18 Apr 2017 08:30:00 +, GiaThnYgeia
<giathnyg...@openmailbox.org> wrote:

>
>
>Larry Dighera:
>> I found the 'debian-8.7.1-amd64-DVD-1.iso' image here:
>> <http://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/>, burned it to
>> SD card in a USB reader with Rufus <https://rufus.akeo.ie/>, and booted it
>> from USB on the Udoo X86 Advanced hardware (Intel quad-core Celeron N3160
>> 2.24 GHz & Intel® Quark SE core 32 MHz plus 32-bit ARC core 32 MHz, Intel HD
>> Graphics 400 Up to 640 MHz 12 execution units, 4 GB DDR3L Dual Channel RAM
>> and 32GB eMMC Storage). 
>
>The link I sent you was for live versions where a complete Debian
>installation boots up (if it is possible based on the hardware) which is
>a very good indication that your installation will act just like it.
>You can select any desktop and then switch and install any desktop you
>like from the system once it is running.  I always use lxde as it is
>lean and mean.  This live version includes the debian installer which
>you can reboot and run from scratch or run it within the live debian
>system.  I prefer to reboot and run the installer alone after I have
>made sure live runs fine.  This gives the installer maximum resources
>and there are less things to confuse it.  You see from live when grub is
>installed it picks up the live drive as one of the installed systems.
>You have to keep an eye on what you select on the grub installation.
>But this would be a small problem, having an invalid boot option on your
>grub.
>
>> I selected the GUI Install from the menu, and all proceeded remarkably fast
>> and smooth without a hitch (except the WiFi, but gigabit Ethernet enabled
>> downloading all required additional files) until the last when it came to
>> grub.  
>
>Don't get me started down that path ;)
>
>> The installer advised that it had detected another OS being installed, and
>> presented me with a few choices to which I wasn't sure of the correct one,
>> so I took the default.  That must have been wrong, as now Debian won't boot
>> with grub from the eMMC "Hard Drive."  I'm not at all familiar with grub.
>
>Were you aware that there was an installed system on that disk and what
>it is?  Is it now an option on the grub boot-up screen? Remember that if
>you move the arrow up and down within the first 5" the default autostart
>that is timed to 5" is deactivated and you now have time to study it.
>Your first option on the base screen should be the debian you installed.
> The second should be for recovery which opens up a second screen where
>recovery is the 2nd option.  Is that what you used?
>Then on the base screen you should have 3 lines of memtest options, and
>at the bottom the "other" system that was previously installed.  It may
>be freedos or something factory???
>
>> I can boot into recovery mode though, and from the command line it appears
>> the install was successful.  So I'm close, but don't know exactly how to
>> proceed to make it bootable.
>
>In order to get to the grub part of the installation the system was
>completely installed and it is there.  There is an option to install
>grub to handle booting of all systems on the drive (possibly sda) and/or
>the partition itself where Debian was installed in which case it makes
>the partition bootable.  I assume the default is the first.
>
>> Any clues sincerely appreciated.
>
>When you pick the first option of Debian to boot, what do you see on the
>screen?  

It happens very quickly.  There is a brief flash of color, and perhaps a few
lines of text, then an interminable black screen with no response to
keyboard/mouse input.

>Lines of white text running some green and maybe red stuff?
>If it is all green you are in good shape, if it is red you have to
>concentrate on that first red tag and tell us what it says.
>

I'm familiar with the dmesg output at boot time.  I see that when I choose
to boot into recovery mode from the grub menus.  When the scrolling text
stops, I'm left with what I thought was a frozen screen, but it turns out to
be login, without a prompt, waiting for me to provide the root password.
Once I submit the root password, I have a command line interface to a
reasonably functional Debian system.

>
>Again, if there was a hardware issue the live system would have
>identified and displayed what the obstacle was.  Possibly you have to go
>into recovery, edit the sources (/etc/apt/sourced.list) and add "main
>contrib non-free" to where it says "main" if such firmware exist.  Then
>$apt update, $apt upgrade but then you have to know what you are missing
>to find the appropriate package to add if it exists.
>

What

Re: Jessie for Udoo X86?

[Larry Dighera]

On Mon, 17 Apr 2017 15:51:00 +, GiaThnYgeia
<giathnyg...@openmailbox.org> wrote:

>Eduard Bloch:
>> Hallo,
>> * Larry Dighera [Sun, Apr 16 2017, 09:27:46PM]:
>>>
>>> The new Udoo X86 boards have just begun to ship: <http://www.udoo.org/>. 
>>>
>>> Is anyone able to provide a link to the 64-bit Debian Jessie USB/SD
>>> installation ISO/img?
>> 
>> Did you try the regular installer from USB stick already?
>
>https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/
>
>If live runs well chances are that you can install it
>
>there is Puppy Linux among others that run entirely on RAM, once loaded
>no disk is required, ideally they will run as long as there is a
>continuous power supply.  Given enough ram you can modify most linux to
>run this way, but some are designed and modified specifically saving you
>the trouble.
>
>> Data sheet indicates that it supports "All Linux Flavors for x86". Which
>> means that it's probably usual Intel hardware inside. It might lack a
>> few drivers for recent hardware revisions but you could install a
>> kernel from jessie-backports in that case.
>
>Interesting and seems more potent than the raspberry system.  But if
>size did not matter so damn much for less money you can get a decent
>USFF box and throw the box away and pretend you are building from
>scratch.  I suspect the quality of some older USFF is higher.  Yes the
>processor and cooling aparatus is a bit bulky ... but it depends on the
>use and available space/weight requirement.

Thank you for your response.

I found the 'debian-8.7.1-amd64-DVD-1.iso' image here:
<http://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/>, burned it to
SD card in a USB reader with Rufus <https://rufus.akeo.ie/>, and booted it
from USB on the Udoo X86 Advanced hardware (Intel quad-core Celeron N3160
2.24 GHz & Intel® Quark SE core 32 MHz plus 32-bit ARC core 32 MHz, Intel HD
Graphics 400 Up to 640 MHz 12 execution units, 4 GB DDR3L Dual Channel RAM
and 32GB eMMC Storage).  

I selected the GUI Install from the menu, and all proceeded remarkably fast
and smooth without a hitch (except the WiFi, but gigabit Ethernet enabled
downloading all required additional files) until the last when it came to
grub.  

The installer advised that it had detected another OS being installed, and
presented me with a few choices to which I wasn't sure of the correct one,
so I took the default.  That must have been wrong, as now Debian won't boot
with grub from the eMMC "Hard Drive."  I'm not at all familiar with grub.

I can boot into recovery mode though, and from the command line it appears
the install was successful.  So I'm close, but don't know exactly how to
proceed to make it bootable.

Any clues sincerely appreciated.

Re: Jessie for Udoo X86?

[Larry Dighera]

On Mon, 17 Apr 2017 10:55:23 +0200, Eduard Bloch <e...@gmx.de> wrote:

>Hallo,
>* Larry Dighera [Sun, Apr 16 2017, 09:27:46PM]:
>> 
>> The new Udoo X86 boards have just begun to ship: <http://www.udoo.org/>. 
>> 
>> Is anyone able to provide a link to the 64-bit Debian Jessie USB/SD
>> installation ISO/img?
>
>Did you try the regular installer from USB stick already?
>
>Data sheet indicates that it supports "All Linux Flavors for x86". Which
>means that it's probably usual Intel hardware inside. It might lack a
>few drivers for recent hardware revisions but you could install a
>kernel from jessie-backports in that case.
>
>Best regards,
>Eduard.


Hello Eduard,

Thank you for your response to my inquiry.

No; I have not yet tried the "regular installer from USB stick."  Are you
able to provide a link to the correct one?  

That sounds like what I'm looking for to install Debian Jessie 64-bit on the
Udoo X86 Advanced board with Intel Celeron N3160 CPU clocked at 2.24 GHz:
<http://shop.udoo.org/usa/preorder-x86.html>.

Best regards,
Larry

Jessie for Udoo X86?

[Larry Dighera]

The new Udoo X86 boards have just begun to ship: . 

Is anyone able to provide a link to the 64-bit Debian Jessie USB/SD
installation ISO/img?

ADVthanksANCE

Re: Security Updates

[Larry Dighera]

Hello Paul,

Thank you for your kind response to my inquiry.

My comments in-line below:


On Wed, 31 Aug 2016 14:48:36 +0100, Darac Marjal <mailingl...@darac.org.uk>
wrote:

>On Tue, Aug 30, 2016 at 12:58:47PM -0700, Larry Dighera wrote:
>>
>>This page <https://www.debian.org/releases/stable/errata> states:
>>
>>"If you use APT, add the following line to /etc/apt/sources.list to be 
>> able
>>to access the latest security updates:
>>
>>deb http://security.debian.org/ jessie/updates main contrib non-free
>>
>>After that, run apt-get update followed by apt-get upgrade."
>>
>>Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running Debian
>>Jessie results in an error message indicating that the public key is not 
>>found.
>>It also finds two libraries that require updating that are not found when the
>>above mentioned /etc/apt/sources.list entry is removed.
>
>As other people are discussing how to avoid the problems, let me have a 
>go at answering your questions directly.
>
>>
>>  1.  What do I need to do to prevent the error message?
>
>Check that "debian-archive-keyring" is installed. 
>

# apt-get -s install debian-archive-keyring
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'raspbian-archive-keyring' instead of
'debian-archive-keyring'
raspbian-archive-keyring is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Hmmm...  I didn't expect that.  Now I am confused.  I don't recall where I got
the notion that I was running Debian Jessie as opposed to Raspbian Jessie.  I
suppose it was from this link:
<https://www.raspberrypi.org/blog/raspbian-jessie-is-here/> where it is stated:

"Raspbian has now been updated to the new stable version of Debian, which
is called Jessie."

I guess I failed to make the distinction between Raspbian Jessie and Debian
Jessie.  Me culpa.

>
>If that is showing as untrusted as well, then read 
>https://ftp-master.debian.org/keys.html.  
>Note the warning at the top, though: "Please note that the details here 
>are for information only, you should not rely on them and use other ways 
>to verify them."
>

I don't know if it's "showing as un-trusted," but I'm beginning to suspect my
confusion between Raspbian Jessie and Debian Jessie is the source of the issue
I experienced.  

Here is the output from os-release and uname:

 # cat ../usr/lib/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/;
SUPPORT_URL="http://www.raspbian.org/RaspbianForums;
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs;


 # uname -a
Linux raspberrypi3 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l
GNU/Linux

I guess that puts a stake in the heart of this apparent non-issue. 

>
>>
>>  2.  As there are other security related URLs (doubtless, as
>>  distributed/released) that are checked during apt-get update, is the
>>  recommended additional entry advisable/useful for this platform?
>
>If you're running Debian, then that line should provide all the security 
>updates you require. If you've added other repositories, though (PPAs, 
>for example, or if you're using a debian-derived distribution such as 
>Ubuntu, Mint, Devuan etc), then you should consult THOSE projects 
>individually to see if they provide security updates (they may simply 
>provide a rolling "bleeding edge" update model instead).
>

Apparently Raspbian Jessie is "a debian-derived distribution," and not Debian
Jessie as I erroneously believed until your assistance enlightened me.

I'll have to presume the default Raspbian Jessie apt sources repositories
provide the intended security robustness, despite the possible security issues
in libldap-2.4-2 and linux-libc-dev packages that came to light when I ran
apt-get update with the "deb http://security.debian.org/ jessie/updates main
contrib non-free" entry in my /etc/apt/sources.list.

As you suggested, I'll take this discussion to raspbian.org, and see if they
can shed some light on the possible security issues in the libldap-2.4-2 and
linux-libc-dev packages.

I am grateful your thoughtful and sagacious support, and the education I
received as a result.  It's always good to grok truth.  :-)

Best regards,
Larry

Re: Security Updates

[Larry Dighera]

On Wed, 31 Aug 2016 14:19:15 +0100, Lisi Reisz <lisi.re...@gmail.com> wrote:

>On Wednesday 31 August 2016 10:39:53 Lisi Reisz wrote:
>> Since you are not replying to anyhting, you may not be subscribed,
>
>I had a reply off list that said that Larry is not replying to our questions 
>because he considers them irrelevant to his original question.
>
>Lisi


Of course, that is not what I said at all.  

Here is a copy of the message I sent to Lisi:

-
To: Lisi Reisz <lisi.re...@gmail.com>
Subject: Re: Security Updates
From: Larry Dighera <ldigh...@att.net>
Date: Wed, 31 Aug 2016 06:09:27 -0700

On Wed, 31 Aug 2016 10:39:53 +0100, Lisi Reisz <lisi.re...@gmail.com> wrote:

>Since you are not replying to anyhting, you may not be subscribed, so here is 
>what I said again:
>
>On Tuesday 30 August 2016 20:58:47 Larry Dighera wrote:
>> This page <https://www.debian.org/releases/stable/errata> states:
>>
>> "If you use APT, add the following line to /etc/apt/sources.list to be
>> able to access the latest security updates:
>>
>> deb http://security.debian.org/ jessie/updates main contrib non-free
>>
>> After that, run apt-get update followed by apt-get upgrade."
>>
>> Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running
>> Debian Jessie results in an error message indicating that the public key is
>> not found. It also finds two libraries that require updating that are not
>> found when the above mentioned /etc/apt/sources.list entry is removed.
>>
>>   1.  What do I need to do to prevent the error message?
>>
>>   2.  As there are other security related URLs (doubtless, as
>>   distributed/released) that are checked during apt-get update, is the
>>   recommended additional entry advisable/useful for this platform?
>
>What is the whole of your sources.list?
>
>Lisi
>
>Like other respondents I suspect that you are using Raspbian not Debian.  Your 
>sources list will tell me/us, or guide us ot teh problem if it is not that.


I'm sorry.  I didn't find your question relevant to my question about the
Debian.org web site providing instructions that produce error messages, and
politely ignored it.  
---


For those who may be following this message thread, here is the output from
'apt-get update' with the offending 'deb-src
http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi
' entry edited into the /etc/apt/sources.list as instructed on this page:
<https://www.debian.org/releases/stable/errata>:

-
Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB]
Hit http://mirrordirector.raspbian.org jessie InRelease
Hit http://archive.raspberrypi.org jessie InRelease
Ign http://security.debian.org jessie/updates InRelease
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages
Ign http://linux.teamviewer.com stable InRelease
Get:2 http://security.debian.org jessie/updates/main armhf Packages [292 kB]
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Ign http://linux.teamviewer.com preview InRelease
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages
Hit http://archive.raspberrypi.org jessie/ui armhf Packages
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages
Get:3 http://security.debian.org jessie/updates/contrib armhf Packages [1,138
B]
Hit http://linux.teamviewer.com stable Release.gpg
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages
Get:4 http://security.debian.org jessie/updates/non-free armhf Packages [14 B]
Get:5 http://security.debian.org jessie/updates/contrib Translation-en [1,211
B]
Hit http://linux.teamviewer.com stable Release
Hit http://linux.teamviewer.com preview Release.gpg
Get:6 http://security.debian.org jessie/updates/main Translation-en [161 kB]
Hit http://linux.teamviewer.com stable/main armhf Packages
Get:7 http://security.debian.org jessie/updates/non-free Translation-en [14 B]
Hit http://linux.teamviewer.com preview Release
Hit http://linux.teamviewer.com preview/main armhf Packages
Ign http://security.debian.org jessie/updates/contrib Translation-en_GB
Ign http://security.debian.org jessie/updates/main Translation-en_GB
Ign http://security.debian.org jessie/updates/non-free Translation-en_GB
Ign http://archive.raspberrypi.org jessie/main Translation-en_GB
Ign http://archive.raspberrypi.org jessie/main Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en_GB
Ign http://archive.raspberrypi.org jessie/ui Translation-en
Ign http://linux.teamviewer.com stable/main Translation-en_GB
Ign http://linux.teamviewer.com stable/m

Re: Security Updates

[Larry Dighera]

On Wed, 31 Aug 2016 13:28:21 +, "Andrew M.A. Cater"
<amaca...@galactic.demon.co.uk> wrote:

>On Wed, Aug 31, 2016 at 06:04:34AM -0700, Larry Dighera wrote:
>> On Tue, 30 Aug 2016 20:44:27 +, "Andrew M.A. Cater"
>> <amaca...@galactic.demon.co.uk> wrote:
>> 
>> >On Tue, Aug 30, 2016 at 12:58:47PM -0700, Larry Dighera wrote:
>> >> 
>> >> This page <https://www.debian.org/releases/stable/errata> states:
>> >> 
>> >> "If you use APT, add the following line to /etc/apt/sources.list to 
>> >> be able
>> >> to access the latest security updates:
>> >> 
>> >> deb http://security.debian.org/ jessie/updates main contrib non-free
>> >> 
>> >> After that, run apt-get update followed by apt-get upgrade."
>> >> 
>> >> Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running 
>> >> Debian
>> >> Jessie results in an error message indicating that the public key is not 
>> >> found.
>> >> It also finds two libraries that require updating that are not found when 
>> >> the
>> >> above mentioned /etc/apt/sources.list entry is removed.
>> >> 
>> >>   1.  What do I need to do to prevent the error message?
>> >> 
>> >>   2.  As there are other security related URLs (doubtless, as
>> >>   distributed/released) that are checked during apt-get update, is the
>> >>   recommended additional entry advisable/useful for this platform?
>> >
>> >Debian or Raspbian?
>> >
>> >If Raspbian - that's based very closely on Debian but isn't strictly Debian.
>> >
>> >Mixing the two might not be a good idea since there will probably be 
>> >incompatibilities at some level.
>> >
>> >There is a port of pure Debian to the Pi 2 - look on the Debian wiki - but 
>> >no one has yet done this for the Pi 3 as far as I know.
>> >
>> >[The original Pi required different compilation options to cope with 
>> >floating point "stuff" which rendered Debian incompatible:
>> >Raspbian is a re-compilation to suit the Raspberry Pi. Pi 2 is ARM v7 with 
>> >hardware floating point. Pi 3 is 64 bit core (so arm64 would work if
>> >the Pi folk hadn't put in 32 bit glue logic or thereabouts). There are also 
>> >issues with the way of loading the operating system, initialising video
>> >and non-free firmware which can cause problems.]
>> >
>> >All the best,
>> >
>> >AndyC
>> 
>> 
>> 
>> Hello Andy,
>> 
>> I thought I made it clear that the OS was Debian Jessie.  It was installed 
>> from
>> the NOOBS release: <https://www.raspberrypi.org/downloads/noobs/>.  As you 
>> can
>> see from this article
>> <https://www.raspberrypi.org/blog/raspbian-jessie-is-here/>, Debian Jessie 
>> was
>> released for the Raspberry Pi platform almost a year ago, September 2015.  
>> 
>> Have you any insight into how to overcome the ;public key not found; error
>> message adding that security repository to the apt list, as stated on the
>> Debian.org web site, may be resolved?
>> 
>> Thank you for your response.
>> 
>> Best regards,
>> Larry
>>
>
>Hi Larry, 
>
>That's Raspbian - NOOBS installs Raspbian.
>
>As Lisi Reisz has stated to you in another email: Raspbian handle their own 
>security updates.
>
>If you want to add the keys to the Debian security updates repository you can 
>use an apt-key add command and the key available from 
>http://ftp-master.debian.org/keys.html
>[The main archive signing key is also used to sign the security updates].
>
>Be aware that you might create problems for yourself.
>
>You may well want to look at the Debian Administrators handbook - you can try 
>apt-get install debian-handbook if the package is also available for Raspbian.
>
>Hope this helps,
>
>Al the very best,
>
>AndyC 
>
>[Copying to the list as this may be of more use more widely]


Hello Andy,

Have you even looked at the information here:
<https://www.raspberrypi.org/blog/raspbian-jessie-is-here/>?  After reading
that announcement, how can you continue to insist that I am not running Debian
Jessie?  

I appreciate your pointer to adding keys to the Debian security updates
repository with apt-key add.  I will look into that, however if it were
necessary for me to do that manually, I would have expected the
<https://www.debian.org/releases/stable/errata> page to have mentioned it
explicitly.  Perhaps I expect too much...

I find the stability of the Debian APT system to be one of the most valuable
aspects of Debian Linux, compared to other less stable distributions I have
encountered over the years.  So I am wary of doing anything to break it, even
if it proffered on a Debian web page, as you cautioned.  

Thank you for sharing your knowledge.

Best regards,
Larry

Security Updates

[Larry Dighera]

This page  states:

"If you use APT, add the following line to /etc/apt/sources.list to be able
to access the latest security updates:

deb http://security.debian.org/ jessie/updates main contrib non-free

After that, run apt-get update followed by apt-get upgrade."

Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running Debian
Jessie results in an error message indicating that the public key is not found.
It also finds two libraries that require updating that are not found when the
above mentioned /etc/apt/sources.list entry is removed.

  1.  What do I need to do to prevent the error message?

  2.  As there are other security related URLs (doubtless, as
  distributed/released) that are checked during apt-get update, is the
  recommended additional entry advisable/useful for this platform?