Unable to compile newest emacs with gnutls

2017-04-30 Thread Harry Putnam 
Attempting to build latest emacs I run into a problem gnutls not being
available.

  ./configure --prefix=/usr/local/src/vcs/git/test --with-x=yes
   --with-x-toolkit=athena  --with-imagemagick
   --with-gpm --with-sound=no
  [...]
  
  configure: error: The following required libraries were not found:
  gnutls
  Maybe some development libraries/packages are missing?
  If you don't want to link with them give
 --with-gnutls=no
  as options to configure

I have these gnutls related pkgs installed:

  i A libcurl3-gnutls   - easy-to-use client-side URL transfer libra
  i   libgnutls-deb0-28 - GNU TLS library - main runtime library
  i   libgnutls-openssl27   - GNU TLS library - OpenSSL wrapper 
  i A libneon27-gnutls  - HTTP and WebDAV client library (GnuTLS ena

I suspect it might be the dev pkgs that is needed:

  libgnutls-dev

But when I try to install it, I run into a complicated dependency
problem I don't know how to solve:

  aptitude install libgnutls-dev

  The following NEW packages will be installed:
libgcrypt11{a} libgcrypt11-dev{ab} libgcrypt20-dev{a} libgnutls-dev{b} 
libgnutls26{a} libgnutlsxx27{a} libgpg-error-dev{a} libp11-kit-dev{a} 
libtasn1-3{a} libtasn1-3-dev{a} 
  0 packages upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
  Need to get 2,990 kB of archives. After unpacking 7,831 kB will be used.
  The following packages have unmet dependencies:
   libgnutls-dev : Depends: libgnutls-openssl27 (= 2.12.20-8+deb7u5) but 
3.3.8-6+deb8u4 is installed.
   libgcrypt11-dev : Breaks: libgnutls-dev (< 2.12.23-18) but 2.12.20-8+deb7u5 
is to be installed.
  The following actions will resolve these dependencies:

   Keep the following packages at their current version:
  1) libgnutls-dev [Not Installed]  

  Accept this solution? [Y/n/q/?]

The offered solution ends with libngutls-dev not installed.

I walked thru several other solutions by pressing `. '

But none of the first 6 offer a way to end up with libgnutls-dev
installed.

I'm not even sure that is the missing pkg to allow emacs to compile
with gnutls...

Hopefully someone here will have experience compiling emacs from
source and will know or have a good idea what needs to be done here.

Re: Unable to compile newest emacs with gnutls

2017-04-30 Thread Reco 
Hi.

On Sun, 30 Apr 2017 10:08:25 -0400
Harry Putnam  wrote:

> Attempting to build latest emacs I run into a problem gnutls not being
> available.
> 
>   ./configure --prefix=/usr/local/src/vcs/git/test --with-x=yes
>--with-x-toolkit=athena  --with-imagemagick
>--with-gpm --with-sound=no
>   [...]
>   
>   configure: error: The following required libraries were not found:
>   gnutls
>   Maybe some development libraries/packages are missing?
>   If you don't want to link with them give
>  --with-gnutls=no
>   as options to configure
...
> I suspect it might be the dev pkgs that is needed:
> 
>   libgnutls-dev

Indeed, but not this one. Not unless you're using wheezy.


> But when I try to install it, I run into a complicated dependency
> problem I don't know how to solve:
> 
>   aptitude install libgnutls-dev

aptitude install libgnutls28-dev

Reco

Re: Unable to compile newest emacs with gnutls

2017-04-30 Thread Sven Joachim 
On 2017-04-30 10:08 -0400, Harry Putnam wrote:

> Attempting to build latest emacs I run into a problem gnutls not being
> available.
>
>   ./configure --prefix=/usr/local/src/vcs/git/test --with-x=yes
>--with-x-toolkit=athena  --with-imagemagick
>--with-gpm --with-sound=no
>   [...]
>   
>   configure: error: The following required libraries were not found:
>   gnutls
>   Maybe some development libraries/packages are missing?
>   If you don't want to link with them give
>  --with-gnutls=no
>   as options to configure
>
> I have these gnutls related pkgs installed:
>
>   i A libcurl3-gnutls   - easy-to-use client-side URL transfer libra
>   i   libgnutls-deb0-28 - GNU TLS library - main runtime library
>   i   libgnutls-openssl27   - GNU TLS library - OpenSSL wrapper 
>   i A libneon27-gnutls  - HTTP and WebDAV client library (GnuTLS ena
>
> I suspect it might be the dev pkgs that is needed:
>
>   libgnutls-dev

That guess seems likely, but is wrong: libgnutls-dev exists only in
oldstable, you should install libgnutls28-dev instead.

Cheers,
   Sven

ls: cannot access '/sys/class/ieee80211/': No such file or directory

2017-04-30 Thread 郭文茂 
Hello,
I am a linux new.I am testing ar9271 wireless card on kali 2.0. when I  type in 
terminal airmon-ng I get a error message.
The CPU architecture is ARMv7(s5p6818)and kernel version is 3.4.9.
can you tell me what should I do? Thanks.

Log message following:

root@kali:~# lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@kali:~# airmon-ng
ls: cannot access '/sys/class/ieee80211/': No such file or directory
PHY Interface   Driver  Chipset

root@kali:~# airmon-ng check kill
ls: cannot access '/sys/class/ieee80211/': No such file or directory

Killing these processes:

  PID Name
  416 dhclient

root@kali:~# dmesg | tail
[5.16] systemd[1]: Mounted POSIX Message Queue File System.
[5.168000] systemd[1]: Started Journal Service.
[5.62] systemd-journald[196]: Received request to flush runtime journal 
from PID 1
[5.86] Registered led device: ledp1
[5.896000] rtc-ds1307: probe of 0-0068 failed with error -5
[5.984000] bt_bcm: rfkill set_block Off GPIOB.8
[5.996000] adxl34x 0-001d: Failed to probe ADXL34x accelerometer
[6.564000] eth0: device MAC address 76:92:d4:85:f3:0f
[9.312000] PHY: stmmac-0:07 - Link is Up - 100/Full
[   16.896000] eth0: no IPv6 routers present

Best & Thanks,
wenmao

Re: converting my local site to be https only access

2017-04-30 Thread Gene Heskett 
On Saturday 29 April 2017 14:49:04 Gene Heskett wrote:

> On Saturday 29 April 2017 14:21:27 Jochen Spieker wrote:
> > Gene Heskett:
> > > On Saturday 29 April 2017 04:05:01 Felix Dietrich wrote:
> > >> Gene Heskett  writes:
> > >>> Where can I find a tut that is a complete instruction set to
> > >>> have it do an auto-redirect to itself, but using the "s" stuff
> > >>> regardless of the accessing client as long as the client can
> > >>> handle the https stuff this conversion will return to the
> > >>> client?
> >
> > What you want to do requires that you understand the basics of
> > Apache's configuration mechanism. You should really start with that.
> >
> > http://httpd.apache.org/docs/2.4/en/getting-started.html
> > http://httpd.apache.org/docs/2.4/en/bind.html
> > http://httpd.apache.org/docs/2.4/en/configuring.html
> > http://httpd.apache.org/docs/2.4/en/urlmapping.html
> > http://httpd.apache.org/docs/2.4/en/vhosts/
> >
I don't have 2.4, 2.2 here on wheezy.

Looking in the docs/2.2/envvars reference and trying some of the commands 
I find I apparently must specify the port # somehow. apache2ctl cannot 
connect on port 80.  It apparently uses /etc/alternatives/www-browser, 
which is a softlink to /usrt/bin/lynx, and guess what?

lynx support at lynx.isc.org has been deleted. And it won't work without 
talking to isc.org first.  Even after being re-installed.

So A: file a bug against lynx, best to remove it as its apparently been 
EOL'd by isc.org

And B: what can I change that softlink in /etc/alternatives to so 
apache2ctl will work against localhost:6309 ?

And C: If I have to learn a new httpd server, is nginx any better than 
apache2?
> > That's really just the basics so you know where to put random things
> > you find on the internet. For your use case, these should also be
> > helpful:
> >
> > http://httpd.apache.org/docs/2.4/en/ssl/
> > http://httpd.apache.org/docs/2.4/en/rewrite/
> >
> > What the upstream Apache documentation does not mention (or care
> > about) is that Debian has its own way of splitting up Apache
> > configuration files. If a random (not Debian- or Ubuntu-specific)
> > tutorial tells you to change your httpd.conf then this is most
> > certainly not the way to do it in Debian.
> >
> > >>> I tried putting those 3 lines quoted numerous times at the
> > >>> bottom of the httpd/conf/httpd.conf, but that killed local
> > >>> access so I assume it also killed external access too.  And its
> > >>> failure did not generate an error.log entry.
> >
> > The bottom of your httpd.conf might be the wrong place to put it. It
> > really depends on your local configuration which we do not know. Do
> > you have a plain Debian installation that you did yourself or do you
> > use an image from a hoster or any other company? What changes have
> > you done to your configuration?
> >
> > What Debian expects most admins to do is drop their own virtual host
> > definitions into /etc/apache2/sites-available/ and use a2ensite to
> > enable them. Global configuration directives can be placed in
> > conf-available/ (use a2enconf).
> >
> > >>> Something was said about the AllowRedirect settings in
> > >>> httpd.conf, but it did not specify what to change it to.
> >
> > Don't touch httpd.conf, it will probably not do what you want to
> > achieve. Instead, edit the virtual host you are using.
> >
> > > Chuckle, point taken, used your search string and got smarter hits
> > > for apache2.  Since my domain registrar is namecheap, I'm reading
> > > this link:
> > >  > >/3 8/redirect-to-https-on-apache>
> >
> > Your domain registrar is irrelevant here. Look for
> > Debian/Ubuntu-specific tutorials after reading up on the basics.
> >
> > > Syntax error on line 71 of /etc/apache2/mods-enabled/ssl.conf:
> > > Invalid command 'Header', perhaps misspelled or defined by a
> > > module not included in the server configuration
> > > Action 'start' failed.
> >
> > Apparently the header module is not enabled in your configuration.
> > You can do so by running "a2enmod headers".
>
> Not being fam with this a2enmod thing, I just used mc to make a
> softlink. That moved the error and changed it a wee bit, to line 72,
> which had the keyword always spelled alway. Fixed, start right up. I
> can only see it at localhost, so I've no clue if the link in my sig
> works or not.
>
> If it redirects to https and the front page pix loads, I'm good to go
> I think.
>
> > > If you install the ssl-cert package, a self-signed certificate
> > > will be automatically created using the hostname currently
> > > configured on your computer.
>
> Which is not the same as the dns servers returns.
>
> > If your machine is publicly available, there is really no reason
> > anymore to use self-signed certificates -- except for testing,
> > probably. If your configuration works with your self-signed
> > certificate, you should consider using Let's Encrypt.
> >
> > > So in internal na

Re: converting my local site to be https only access

2017-04-30 Thread Dejan Jocic 
On 30-04-17, Gene Heskett wrote:
> On Saturday 29 April 2017 14:49:04 Gene Heskett wrote:
> 
> > On Saturday 29 April 2017 14:21:27 Jochen Spieker wrote:
> > > Gene Heskett:
> > > > On Saturday 29 April 2017 04:05:01 Felix Dietrich wrote:
> > > >> Gene Heskett  writes:
> > > >>> Where can I find a tut that is a complete instruction set to
> > > >>> have it do an auto-redirect to itself, but using the "s" stuff
> > > >>> regardless of the accessing client as long as the client can
> > > >>> handle the https stuff this conversion will return to the
> > > >>> client?
> > >
> > > What you want to do requires that you understand the basics of
> > > Apache's configuration mechanism. You should really start with that.
> > >
> > > http://httpd.apache.org/docs/2.4/en/getting-started.html
> > > http://httpd.apache.org/docs/2.4/en/bind.html
> > > http://httpd.apache.org/docs/2.4/en/configuring.html
> > > http://httpd.apache.org/docs/2.4/en/urlmapping.html
> > > http://httpd.apache.org/docs/2.4/en/vhosts/
> > >
> I don't have 2.4, 2.2 here on wheezy.
> 
> Looking in the docs/2.2/envvars reference and trying some of the commands 
> I find I apparently must specify the port # somehow. apache2ctl cannot 
> connect on port 80.  It apparently uses /etc/alternatives/www-browser, 
> which is a softlink to /usrt/bin/lynx, and guess what?
> 
> lynx support at lynx.isc.org has been deleted. And it won't work without 
> talking to isc.org first.  Even after being re-installed.
> 
> So A: file a bug against lynx, best to remove it as its apparently been 
> EOL'd by isc.org
> 
> And B: what can I change that softlink in /etc/alternatives to so 
> apache2ctl will work against localhost:6309 ?

For changing those softlinks in /etc/alternatives best would be to use
update-alternatives. As root, or with sudo, whatever you prefer. As to
what would be best in your case, I do not know. Other terminal browsers
you could use are Links and w3m.

Re: converting my local site to be https only access

2017-04-30 Thread Eike Lantzsch 
On Sunday, 30 April 2017 17:07:47 -04 Gene Heskett wrote:
[snip]
> 
> I don't have 2.4, 2.2 here on wheezy.
> 
> Looking in the docs/2.2/envvars reference and trying some of the commands
> I find I apparently must specify the port # somehow. apache2ctl cannot
> connect on port 80.  It apparently uses /etc/alternatives/www-browser,
> which is a softlink to /usrt/bin/lynx, and guess what?
> 
> lynx support at lynx.isc.org has been deleted. And it won't work without
> talking to isc.org first.  Even after being re-installed.
> 
> So A: file a bug against lynx, best to remove it as its apparently been
> EOL'd by isc.org

[snip]

Gene,
You might like to replace lynx with links.
There is also links2 and elinks, but according to openbsd.org elinks is full 
of security holes and those guys I do believe.

Sorry, can't comment on your main problem.

Cheers
Eike

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

2017-04-30 Thread 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 
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: converting my local site to be https only access

2017-04-30 Thread davidson 

On Sun, 30 Apr 2017, Gene Heskett wrote:


On Saturday 29 April 2017 14:49:04 Gene Heskett wrote:


On Saturday 29 April 2017 14:21:27 Jochen Spieker wrote:

Gene Heskett:

On Saturday 29 April 2017 04:05:01 Felix Dietrich wrote:

Gene Heskett  writes:

Where can I find a tut that is a complete instruction set to
have it do an auto-redirect to itself, but using the "s" stuff
regardless of the accessing client as long as the client can
handle the https stuff this conversion will return to the
client?


What you want to do requires that you understand the basics of
Apache's configuration mechanism. You should really start with that.

http://httpd.apache.org/docs/2.4/en/getting-started.html
http://httpd.apache.org/docs/2.4/en/bind.html
http://httpd.apache.org/docs/2.4/en/configuring.html
http://httpd.apache.org/docs/2.4/en/urlmapping.html
http://httpd.apache.org/docs/2.4/en/vhosts/


I don't have 2.4, 2.2 here on wheezy.

Looking in the docs/2.2/envvars reference and trying some of the commands
I find I apparently must specify the port # somehow. apache2ctl cannot
connect on port 80.  It apparently uses /etc/alternatives/www-browser,
which is a softlink to /usrt/bin/lynx, and guess what?

lynx support at lynx.isc.org has been deleted. And it won't work without
talking to isc.org first.  Even after being re-installed.


Lynx works just fine. I expect your configuration file simply has some
references to obsolete remote locations.

Does this work?

 $ WWW_HOME="https://en.wikipedia.org/wiki/PEBKAC"; lynx

or this?

 $ 
WWW_HOME="file://localhost/REPLACE-ME-WITH-A-PATH-TO-SOME-LOCAL-HTML-DOC.html" 
lynx

And does this...

 $ grep '^STARTFILE:' /etc/lynx-cur/lynx.cfg

...confirm that you have something obsolete like

 STARTFILE:http://lynx.isc.org/

in your lynx.cfg ?

Then fix that broken reference. Edit /etc/lynx-cur/lynx.cfg, replacing
that STARTFILE url with whatever you like.

FWIW, I think

 STARTFILE:file://localhost/~/

makes a sensible default.

Or, if for some incomprehensible reason you think a remote website is
an appropriate default startfile, you could use

  STARTFILE:http://lynx.invisible-island.net/

instead.

While you're at it, you might want to cast your eye over any other
lines returned by this...

 $ grep '^[A-Z_]*:[[:blank:]]*https\?://' /etc/lynx-cur/lynx.cfg

...and see if you wouldn't rather change them to something more
up-to-date, more reliable, or more appropriate for your installation.


So A: file a bug against lynx, best to remove it as its apparently been
EOL'd by isc.org


Huh? You would remove a program simply because isc.org removes a
couple web pages?

Development of lynx continues unabated:

 http://invisible-island.net/lynx/lynx-develop.html

Good luck with your project.

index.html

2017-04-30 Thread Gene Heskett 
Greetings;

Imagine my surprise when I looked at /var/www/html/index.html,
and found that somehow, it was native to a PCLos install I was running 
half a decade or more ago!

Now, do we have a script that will rebuild a new index.html for the 
defined root of the server, and which WILL access the /var/www/html/gene 
directory? This should restore the whole site to http compatibility.

Right now, with out without that file, the subdir "gene" isn't 
accessible.  Cannot be found is the message.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Unable to compile newest emacs with gnutls

2017-04-30 Thread Harry Putnam 
Harry Putnam  writes:

[...]


Reco  writes:

[...]

> ...
>> I suspect it might be the dev pkgs that is needed:
>> 
>>   libgnutls-dev
>
> Indeed, but not this one. Not unless you're using wheezy.
>
>
>> But when I try to install it, I run into a complicated dependency
>> problem I don't know how to solve:
>> 
>>   aptitude install libgnutls-dev
>
> aptitude install libgnutls28-dev

Sven Joachim  writes:

[...]

>> I suspect it might be the dev pkgs that is needed:
>>
>>   libgnutls-dev
>
> That guess seems likely, but is wrong: libgnutls-dev exists only in
> oldstable, you should install libgnutls28-dev instead.

Thanks to you both, yes it works now after that install.

Re: converting my local site to be https only access

2017-04-30 Thread Lisi Reisz 
On Monday 01 May 2017 01:19:21 david...@freevolt.org wrote:
> Development of lynx continues unabated:
>
>   http://invisible-island.net/lynx/lynx-develop.html

The most recent reference seems to be to 2015:
"Finally (as of 2015)  "

Lisi

Re: converting my local site to be https only access

2017-04-30 Thread Gene Heskett 
On Sunday 30 April 2017 20:19:21 david...@freevolt.org wrote:

> On Sun, 30 Apr 2017, Gene Heskett wrote:
> > On Saturday 29 April 2017 14:49:04 Gene Heskett wrote:
> >> On Saturday 29 April 2017 14:21:27 Jochen Spieker wrote:
> >>> Gene Heskett:
>  On Saturday 29 April 2017 04:05:01 Felix Dietrich wrote:
> > Gene Heskett  writes:
> >> Where can I find a tut that is a complete instruction set to
> >> have it do an auto-redirect to itself, but using the "s" stuff
> >> regardless of the accessing client as long as the client can
> >> handle the https stuff this conversion will return to the
> >> client?
> >>>
> >>> What you want to do requires that you understand the basics of
> >>> Apache's configuration mechanism. You should really start with
> >>> that.
> >>>
> >>> http://httpd.apache.org/docs/2.4/en/getting-started.html
> >>> http://httpd.apache.org/docs/2.4/en/bind.html
> >>> http://httpd.apache.org/docs/2.4/en/configuring.html
> >>> http://httpd.apache.org/docs/2.4/en/urlmapping.html
> >>> http://httpd.apache.org/docs/2.4/en/vhosts/
> >
> > I don't have 2.4, 2.2 here on wheezy.
> >
> > Looking in the docs/2.2/envvars reference and trying some of the
> > commands I find I apparently must specify the port # somehow.
> > apache2ctl cannot connect on port 80.  It apparently uses
> > /etc/alternatives/www-browser, which is a softlink to
> > /usrt/bin/lynx, and guess what?
> >
> > lynx support at lynx.isc.org has been deleted. And it won't work
> > without talking to isc.org first.  Even after being re-installed.
>
> Lynx works just fine. I expect your configuration file simply has some
> references to obsolete remote locations.
>
> Does this work?
>
>   $ WWW_HOME="https://en.wikipedia.org/wiki/PEBKAC"; lynx
>
> or this?
>
>   $
> WWW_HOME="file://localhost/REPLACE-ME-WITH-A-PATH-TO-SOME-LOCAL-HTML-D
>OC.html" lynx
>
> And does this...
>
>   $ grep '^STARTFILE:' /etc/lynx-cur/lynx.cfg
>
> ...confirm that you have something obsolete like
>
>   STARTFILE:http://lynx.isc.org/
>
> in your lynx.cfg ?
>
it was.

> Then fix that broken reference. Edit /etc/lynx-cur/lynx.cfg, replacing
> that STARTFILE url with whatever you like.
>
> FWIW, I think
>
>   STARTFILE:file://localhost/~/
>
> makes a sensible default.

except I am then trapped in my home dir.
>
> Or, if for some incomprehensible reason you think a remote website is
> an appropriate default startfile, you could use
>
>STARTFILE:http://lynx.invisible-island.net/
>
> instead.
>
> While you're at it, you might want to cast your eye over any other
> lines returned by this...
>
>   $ grep '^[A-Z_]*:[[:blank:]]*https\?://' /etc/lynx-cur/lynx.cfg

Which was a wisc.edu url.
>
> ...and see if you wouldn't rather change them to something more
> up-to-date, more reliable, or more appropriate for your installation.
>
> > So A: file a bug against lynx, best to remove it as its apparently
> > been EOL'd by isc.org
>
> Huh? You would remove a program simply because isc.org removes a
> couple web pages?
>
> Development of lynx continues unabated:
>
>   http://invisible-island.net/lynx/lynx-develop.html

Sorta seems to me that ought to be kept uptodate in re that by the debian 
folks.
> Good luck with your project. 

I have atm, the darnest collection of Murphy's work I've ever seen. So I 
am inclined to fire up amrecover, back it up a week, and recover 
the /etc/apache2, /etc/httpd, and /var/www/html trees.  That sould put 
me back to a working, non ssl, web server.  All this got started because 
the next firefox says it will not look at a plain http site, and I was 
trying to make robots.txt kick googlebot in the gonads and out of my 
site, its eating more #$%& bandwidth than my site traffic is.  So once 
I've restored normal http operations, I'll come back and see if I can 
find some help converting it to https.

Thank you david...@freevolt.org.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: converting my local site to be https only access

2017-04-30 Thread Gene Heskett 
On Sunday 30 April 2017 20:51:54 Lisi Reisz wrote:

> On Monday 01 May 2017 01:19:21 david...@freevolt.org wrote:
> > Development of lynx continues unabated:
> >
> >   http://invisible-island.net/lynx/lynx-develop.html
>
> The most recent reference seems to be to 2015:
> "Finally (as of 2015)  "
>
> Lisi

Thanks Lisi, I hadn't had time to look yet.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Console fonts

2017-04-30 Thread Felix Miata 
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.

GiaThnYgeia later wrote:
$ inxi -c10 -v3
Will list basic system info and hardware
***
I found nothing in the archive or on original reading of the thread 
responding
to this, but then later I did see OP wrote:

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
***
This supports my suspicion. Later, OP provided logs, which contained:

Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64
root=UUID=f0748180-a596-4f02-85d8-34b09b57cb42 ro quiet
(EE) open /dev/dri/card0: No such file or directory
(EE) open /dev/dri/card0: No such file or directory
(EE) open /dev/fb0: No such file or directory
(EE) open /dev/fb0: No such file or directory
(EE) Screen 0 deleted because of no matching config section.
(EE) Screen 0 deleted because of no matching config section.
***
These support my suspicion, and explain why his ttys are stuck in 80x25 
mode,
unresponsive to later instruction from David Wright. Lack of /dev/fb0 is a not
unusual pre-KMS result from a kernel cmdline (from the selected Grub stanza, as
modified, if modified) that lacks anything telling the kernel not to enable
framebuffer, resulting in use of 80x25 text mode on the ttys. Since Jessie's
3.16 kernel does support KMS, his 1920x1080 Samsung SyncMaster display's native
mode should be picked up by KMS, but that depends on the kernel supporting his
Intel HD Graphics 400 device. Possibly Grub could be reconfigured to make a
lesser mode like 1440x900 or less explicit. Lack of /dev/dri/card0 explains why
X doesn't work, the kernel found no supported gfx device.

When I boot an Intel video Jessie PC with no video parameters on cmdline,
root=LABEL=deb8jessie plymouth.enable=0 noresume
I see kernel messages begin in 80x25 mode, after which the kernel figures out
the display's native mode and switches to it, resulting in ttys producing 210
columns by 65 rows.
# inxi -c0 -G
Graphics:  Card: Intel 82945G/GZ Integrated Graphics Controller
   Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
   tty size: 210x65 Advanced Data: N/A for root out of X

When I reboot same PC with framebuffer disabled to emulate OP's boot condition 
thus,
root=LABEL=deb8jessie plymouth.enable=0 noresume nomodeset
# ls -l /dev/fb*
ls: cannot access /dev/fb*: No such file or directory
the ttys stay in 80x25 mode:
# inxi -c0 -G
Graphics:  Card: Intel 82945G/GZ Integrated Graphics Controller
   Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
   tty size: 80x25 Advanced Data: N/A for root out of X

I've seen nothing in thread explicitly explaining why he has no /dev/fb0, but
unless and until /dev/fb0 exists, ttys are stuck in 80x25. Maybe that is
something installing a working Plymouth can fix. I don't know, as I never use
Plymouth, and suspect it would also be victim of unsupported hardware.

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.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/