Re: converting my local site to be https only access

[davidson]

On Sun, 30 Apr 2017, Gene Heskett wrote:


On Sunday 30 April 2017 20:19:21 david...@freevolt.org wrote:


On Sun, 30 Apr 2017, Gene Heskett wrote:

[trimmed]

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.


Well, as Greg W. pointed out, you aren't really restricted to whatever
links happen to be present in the startfile/"Main screen".

When running in "Novice" mode, the shortcut key for loading an
arbitrary url (G) is helpfully listed at the bottom of every screen:

  Arrow keys: Up and Down to move.  Right to follow a link; Left to go back.
  H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list

But if you would like the default "Main screen" to be something more
web-access-centric, the choice is yours. Maybe

 STARTFILE:https://duckduckgo.com/lite/

or

 STARTFILE:https://www.google.com/

would fit the bill. Or something else entirely. Obviously you will
know better than I do what your users will find helpful.

Somebody upstream of us apparently thought that a site about lynx
would be a good initial default. Not a bad choice, if you ask me. Too
bad the site had to move.


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.


Thought so: http://scout.wisc.edu/

Which was presumably the value of DEFAULT_INDEX_FILE .

Whatever scout.wisc.edu may have had there in the past, the content
currently shown on that page is pretty much worthless as a general web
index.

So you'll probably change it to something better.


...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.


Sounds reasonable to me.

On the other hand, it is the site administrator, rather than Thomas
Dickey or the debian maintainer for lynx-cur, who is in the better
position to determine helpful values for both STARTFILE and
DEFAULT_INDEX_FILE in a given lynx install. I imagine (or hope) they
are frequently customised.

Anyways, maintenance of Wheezy is now in the hands of the Debian LTS
team:

 https://wiki.debian.org/LTS/FAQ#Where_can_bugs_be_reported.3F

  Where can bugs be reported?

   Please report bugs that you found in the packages to the
   debian-lts[1] mailing list. The bar for severity will be raised
   (minor issues will no longer be fixed).

   1. https://wiki.debian.org/LTS/Contact#debian-lts


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.


It'll be interesting to follow along.

Re: converting my local site to be https only access

[davidson]

On Mon, 1 May 2017, 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)  "


I linked to that page because it contained discussion of the website's
move away from isc.org to invisible-island.net .

Lynx current development:

 http://lynx.invisible-island.net/current/index.html

More generally:

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

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[David Wright]

On Mon 01 May 2017 at 14:48:13 (-0400), Greg Wooledge wrote:
> On Mon, May 01, 2017 at 01:18:58PM -0500, David Wright wrote:
> > They do. Both expect a command. You can "show" something but you can't
> > "dev" it or, at least, I don't know how to.
> 
> The surprise comes from the fact that typically you can add "dev eth0"
> to the end of one working ip command, to get another working ip command
> which is restricted to that one interface -- but not always.
> 
> ip addr show (working)
> ip addr show dev eth0 (working)
> 
> But
> 
> ip addr (working)
> ip addr dev eth0 (NOT working)
> 
> And
> 
> ip -s link show (working)
> ip -s link show dev eth0 (working)
> 
> But
> 
> ip -s link (working)
> ip -s link dev eth0 (NOT working)
> 
> Apparently, in order to understand why half of the commands work and
> half do not, you have to somehow figure out that you're currently using
> a command with an assumed verb, and that this makes a difference, in
> some way, if you try to add words that follow the assumed verb.  Like,
> "the verb is only added if the parser runs out of words" or something.

I'd assumed that the presumption of "show [everything]" was there
because non-root users can do little else, and I don't think you can
omit/assume any other verb. cf mount.

> The inconsistency is quite confusing, especially if you haven't
> scientifically attempted EVERY combination of words yet, to see which
> combinations work and which do not, in order to analyze it for patterns
> and infer the actual grammar rules.

Sure, but who would prefer "ip link" to give you a load of its BNF
rather than assuming you meant show. "ip" does give you BNF, it's
true, but with such a flexible command, where to start. "ip nt"
already fills the screen; only 16 more object types to go.

Cheers,
David.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[David Wright]

On Wed 26 Apr 2017 at 15:26:36 (-0500), Richard Owlett wrote:
> On 04/26/2017 10:02 AM, Lisi Reisz wrote:
> >But did /sbin/ifconfig work?
> >
> 
>  Had no reason to try.
> Whenever I come across a command that *SHOULD* work, but does not,
> the first diagnostic step is attempt to run the *IDENTICAL* command
> as root.
> In the *MAJORITY* of cases that it runs demonstrates that someone at
> sometime decided to restrict some computer owners from using their
> own computer in a reasonable manner.

Which merely begs the question. The meaning of "*should* work
as non-root" is defined by your workaround.

> Remember Linux borrows heavily from an OS designed in another era
> for a another audience. I have yet to run across a case where any
> distinction should be made between "user richard" and "user root". I
> do not take that as necessary and sufficient conditions to abolish
> questionable conventions. They might be occasionally valuable.

That's a nice explanation of why I wrote last year a sentence that
you didn't understand:

  The usefulness of many suggestions is limited, of course, by the OPs
  insistence that a horse and cart is driven through the unix security
  model merely because the OP never connects anything to the internet
  (which is insane).

https://lists.debian.org/debian-user/2016/11/msg00903.html

I guess you were happier with DOS.

> In the age of laptops, tablets, and so-called "smart phones" I think
> the more relevant basic distinction would be between "physically
> local user" and "physically external user".

So how is anyone able to configure a computer for their naive family,
say, to use.

> Haven't yet figured out what to propose that wouldn't "throw baby
> out with the bath water".

The same answer, then, as I gave you for your proposed vague changes
to the man pages.

Cheers,
David.

Re: converting my local site to be https only access

[rhkramer]

On Monday, May 01, 2017 02:54:05 PM rhkra...@gmail.com wrote:
> On Monday, May 01, 2017 12:57:58 PM Gene Heskett wrote:
> > On Monday 01 May 2017 11:18:21 rhkra...@gmail.com wrote:
> > > I hadn't heard anything about this, so I tried Googling.  The only
> > > thing I've found so far is reference to an optional add-on / plugin
> > > ("HTTPS Everywhere", iiuc) that would allow the browser to look only
> > > at ssl (https) pages.  Am I missing something?
> > 
> > That refers to ones browser, zip to do with a web server.
> 
> Well, Firefox is a browser, I thought that was what was being talked about?

Oh, maybe to be clearer, that plugin is for Firefox.

Re: converting my local site to be https only access

[rhkramer]

On Monday, May 01, 2017 12:57:58 PM Gene Heskett wrote:
> On Monday 01 May 2017 11:18:21 rhkra...@gmail.com wrote:
> > I hadn't heard anything about this, so I tried Googling.  The only
> > thing I've found so far is reference to an optional add-on / plugin
> > ("HTTPS Everywhere", iiuc) that would allow the browser to look only
> > at ssl (https) pages.  Am I missing something?
> 
> That refers to ones browser, zip to do with a web server.

Well, Firefox is a browser, I thought that was what was being talked about?

> Its converting my legacy web site that I am attempting to do.

Understood

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Greg Wooledge]

On Mon, May 01, 2017 at 01:18:58PM -0500, David Wright wrote:
> They do. Both expect a command. You can "show" something but you can't
> "dev" it or, at least, I don't know how to.

The surprise comes from the fact that typically you can add "dev eth0"
to the end of one working ip command, to get another working ip command
which is restricted to that one interface -- but not always.

ip addr show (working)
ip addr show dev eth0 (working)

But

ip addr (working)
ip addr dev eth0 (NOT working)

And

ip -s link show (working)
ip -s link show dev eth0 (working)

But

ip -s link (working)
ip -s link dev eth0 (NOT working)

Apparently, in order to understand why half of the commands work and
half do not, you have to somehow figure out that you're currently using
a command with an assumed verb, and that this makes a difference, in
some way, if you try to add words that follow the assumed verb.  Like,
"the verb is only added if the parser runs out of words" or something.

The inconsistency is quite confusing, especially if you haven't
scientifically attempted EVERY combination of words yet, to see which
combinations work and which do not, in order to analyze it for patterns
and infer the actual grammar rules.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[David Wright]

On Wed 26 Apr 2017 at 09:36:36 (-0500), Richard Owlett wrote:
> On 04/26/2017 07:50 AM, Darac Marjal wrote:
> >On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
> >>On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
> >>>For interface statistics from ip, try "ip -s link [interface]".
> >>
> >>On stretch:
> >>
> >>wooledg:~$ ip -s link eth0
> >>Command "eth0" is unknown, try "ip link help".
> >>
> >>wooledg:~$ ip -s link dev eth0
> >>Command "dev" is unknown, try "ip link help".
> >>
> >>wooledg:~$ ip link help
> >>[... enormous BNF dump, entirely missing -s, or any reference whatsoever
> >>to the fact that you can stick options between "ip" and "link" ...]
> >>
> >>wooledg:~$ ip -s link show eth0
> >>2: eth0:  mtu 1500 qdisc pfifo_fast
> >>state UP mode DEFAULT group default qlen 1000
> >>   link/ether a0:8c:fd:c3:89:e0 brd ff:ff:ff:ff:ff:ff
> >>   RX: bytes  packets  errors  dropped overrun mcast
> >>   380719013  1442490  0   0   0   4731
> >>   TX: bytes  packets  errors  dropped carrier collsns
> >>   57971257   614586   0   0   0   0
> >>
> >>Aha!
> >
> >My bad. I actually only got as far as discovering "ip -s link" on my own
> >system. As I was typing up the email I remembered that Richard was after
> >statistics for a specific interface. I should have been more diligent in
> >working out the correct format.
> >
> >>
> >>(Sadly, this is my *typical* experience with the ip command -- trying
> >>random things until one of them works, because the documentation
> >>is impenetrable, and the syntax barely guessable, and certainly not
> >>predictable.)
> >
> >ip *could* do a lot better, it's true. As a monolithic tool, there's not
> >really much excuse for the different sub-tools to parse the commands
> >differently. As you say, "ip address" expects the device to be expressed
> >as "dev eth0", so why doesn't "ip link" handle it the same way? I don't
> >know.
> 
> 
> I would go further saying iproute2 is non-functional due to being
> functionally un-documented.
> 
> https://manpages.debian.org/jessie/iproute2/ip.8.en.html is useless.

It is if you want to know exactly what you can do with one of
the seventeen different objects it can handle. If you want to
know what those objects are, or what options are available, it's
not useless.

> Functional commands, for this thread's topic would be
>   ip -s link
> or
>   ip -s link ls usb0
> 
> No hint of either in so-called man page.
> 
> I accidentally discovered it by following up links when doing
> DuckDuckGo search for "documentation iproute2" (w/o quotes).
> 
> I then did another netinst of testing. There is some subset of the
> "ip" command available after the network has been configured. The
> help is too abbreviated to be useful.

Not at all. The abbreviated help shows you what's available
during the installation process which, as you have noticed,
is often a subset.

Having ascertained that subset, you now know which parts of the
main documentation, available in various locations, still apply.

You seem to want the cut-down man pages to be included in the
installation, which is a surprise coming from someone who seems
concerned about bandwidth almost to the point of obsession.

Cheers,
David.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[David Wright]

On Wed 26 Apr 2017 at 13:50:15 (+0100), Darac Marjal wrote:
> On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
> >On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
> >>For interface statistics from ip, try "ip -s link [interface]".
> >
> >On stretch:
> >
> >wooledg:~$ ip -s link eth0
> >Command "eth0" is unknown, try "ip link help".
> >
> >wooledg:~$ ip -s link dev eth0
> >Command "dev" is unknown, try "ip link help".
> >
> >wooledg:~$ ip link help
> >[... enormous BNF dump, entirely missing -s, or any reference whatsoever
> >to the fact that you can stick options between "ip" and "link" ...]

Presumably you realisd that the options to ip are documented in
man ip   and summarised in   ip help. Otherwise, this has to be
duplicated and maintained seventeen times.

> >wooledg:~$ ip -s link show eth0
> >2: eth0:  mtu 1500 qdisc pfifo_fast state 
> >UP mode DEFAULT group default qlen 1000
> >   link/ether a0:8c:fd:c3:89:e0 brd ff:ff:ff:ff:ff:ff
> >   RX: bytes  packets  errors  dropped overrun mcast
> >   380719013  1442490  0   0   0   4731
> >   TX: bytes  packets  errors  dropped carrier collsns
> >   57971257   614586   0   0   0   0
> >
> >Aha!
> 
> My bad. I actually only got as far as discovering "ip -s link" on my own
> system. As I was typing up the email I remembered that Richard was after
> statistics for a specific interface. I should have been more diligent in
> working out the correct format.
> 
> >
> >(Sadly, this is my *typical* experience with the ip command -- trying
> >random things until one of them works, because the documentation
> >is impenetrable, and the syntax barely guessable, and certainly not
> >predictable.)
> 
> ip *could* do a lot better, it's true. As a monolithic tool, there's not
> really much excuse for the different sub-tools to parse the commands
> differently. As you say, "ip address" expects the device to be expressed
> as "dev eth0", so why doesn't "ip link" handle it the same way? I don't
> know.

They do. Both expect a command. You can "show" something but you can't
"dev" it or, at least, I don't know how to.

Cheers,
David.

Re: index.html

[Gene Heskett]

On Monday 01 May 2017 11:55:49 Tony Baldwin wrote:

> On 04/30/2017 08:26 PM, Gene Heskett wrote:
> > 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
>
> nope. You've got to write or create your own index, unless you install
> something that generates one, such as dokuwiki, or wordpress, or any
> of a myriad of other CMS, (micro)blogging, social networking, or wiki
> platforms, forums or gallerys...the possibilities are nearly endless.
>
> If you just want to list the directories contents, try putting in an
> index.php with something like this in it:
>
> 
> 
> 
>  // loop through files and list them
>
> $path = "/var/www/html/gene/";
>
> $dir_handle = @opendir($path) or die("Unable to open $path");
>
> while ($file = readdir($dir_handle)) {
>
>   if($file == "." || $file == ".." || $file == "index.php" ||
> $file == "private" || $file == ".htaccess" || $file == "robots.txt" ||
> $file == ".index.php.swp" )
>
>   continue;
>
>   echo "$file";
>
>   }
>
>   closedir($dir_handle);
> ?>
> 
> 
> 
>
>
> You'll have to have php5 or better installed.

My web site is very simple, text and pix. So this 82 yo old fart can 
usually maintain it himself. No php, no databasie stuff at all.

The closest to high level stuff is that the pix galleries were created 
using jigl, so when you visit one of those pages, you get a screenfull 
of thumbnails, clicking on one of them brings up a pretty compressed but 
full screen image.  Clicking on many of those a second time will get you 
the original, straight out of the camera version of that image.  Those 
directories with mixed text & images are presented as a directory 
listing, but you can click on an image and get it, or .pdf's and such 
are offered for downloading when clicking on the directory entry.

Its a pretty "stable" site. If I add something, the link gets posted on 
the mailing list that applies so folks interested in one of my cnc 
machines will know about it, but I don't take out adds in the paper 
about it.

> This is essentially how I built http://tonybaldwin.me/pages/
> and various other pages on my site, including
> http://tonybaldwin.me/images/
>   only that has
>   $path = "/path/to/www/images/";
>
> 
>  style=\"max-width:200px;\">$file
> because that dir is full of images, so I have the index show a
> thumbnail, linking to the larger image.
>
>
> tony


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

[Gene Heskett]

On Monday 01 May 2017 11:18:21 rhkra...@gmail.com wrote:

> On Sunday, April 30, 2017 09:32:33 PM Gene Heskett wrote:
> > All this got started because
> > the next firefox says it will not look at a plain http site, and I
> > was
>
> I hadn't heard anything about this, so I tried Googling.  The only
> thing I've found so far is reference to an optional add-on / plugin
> ("HTTPS Everywhere", iiuc) that would allow the browser to look only
> at ssl (https) pages.  Am I missing something?
>
That refers to ones browser, zip to do with a web server.

> (Well, I didn't read what I found carefully or completely, I did see
> some snippet of text that said that, in some respects, it would work
> (or use some methodologies) of NoScript, which *might* mean that there
> might be a way to override the plugin manually to view non-SSL pages.)
>
> (Not to say that SSL everywhere wouldn't be a good idea, but, until
> "legacy" websites are converted, we may be missing a lot of the web.)

Its converting my legacy web site that I am attempting to do.

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: index.html

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, May 01, 2017 at 11:55:49AM -0400, Tony Baldwin wrote:
> 
> On 04/30/2017 08:26 PM, Gene Heskett wrote:
> >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
> >
> 
> nope. You've got to write or create your own index, unless you
> install something that generates one, such as dokuwiki, or
> wordpress, or any of a myriad of other CMS, (micro)blogging, social
> networking, or wiki platforms, forums or gallerys...the
> possibilities are nearly endless.
> 
> If you just want to list the directories contents, try putting in an
> index.php with something like this in it [...]

Or there is the

  Options +Indexes

for the Apache config [1]. You can fine-tune how the index itself
is rendered via the IndexOptions directive [2].

This would be a more lightweight, yet less flexible approach.

Note that you'll have to make sure that your clients don't see
things you don't want them to see (but this applies even more
strongly to a scripting solution, like the PHP example offered)

regards
[1] https://httpd.apache.org/docs/2.2/mod/core.html#options
[2] https://httpd.apache.org/docs/2.2/mod/mod_autoindex.html#indexoptions

- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkHYRsACgkQBcgs9XrR2kb4nQCdHtUVN0AbRUmh7CkbLyHKeVxf
QbEAnAroaZ3MhCFoEv82gzsDUhFSGL4v
=37ag
-END PGP SIGNATURE-

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

[David Wright]

On Sun 30 Apr 2017 at 16:40:49 (-0700), Larry Dighera wrote:
> 
> 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 think the cause may be explained in the earlier reply to this post.
I've not really played with the framebuffer specifications.

> 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.

As it says, these variables can only reduce the width used by default,
not increase it. I've never used them. I just set the fontsize and
then record the resulting size with COLUMNS/LINES for future reference.

> 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.

That may be the case.

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

If you're editing that file to make changes, then yes. But I
don't like using setupcon because I usually have an X server running,
which can interfere with things. (I might be maligning it; it could
be keyboard changes which interfere, I don't remember.)

> 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.

That's why I posted my-font-usr-share-consolefonts which gives
the location of the possible files you can use. Just look through
/usr/share/consolefonts/

> 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 

Re: index.html

[Greg Wooledge]

On Mon, May 01, 2017 at 11:55:49AM -0400, Tony Baldwin wrote:
> If you just want to list the directories contents, try putting in an 
> index.php with something like this in it:

Or remove all of index.php, index.html and index.htm, and make sure
you've turned on the "Indexes" option for this directory in the Apache
config.  Then Apache will simply generate a directory index page for
you, and you don't need to write a PHP program.

Re: index.html

[Tony Baldwin]

On 04/30/2017 08:26 PM, Gene Heskett wrote:

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



nope. You've got to write or create your own index, unless you install 
something that generates one, such as dokuwiki, or wordpress, or any of 
a myriad of other CMS, (micro)blogging, social networking, or wiki 
platforms, forums or gallerys...the possibilities are nearly endless.


If you just want to list the directories contents, try putting in an 
index.php with something like this in it:





 if($file == "." || $file == ".." || $file == "index.php" || 
$file == "private" || $file == ".htaccess" || $file == "robots.txt" || 
$file == ".index.php.swp" )


 continue;

 echo "$file";

 }

 closedir($dir_handle);
?>





You'll have to have php5 or better installed.
This is essentially how I built http://tonybaldwin.me/pages/
and various other pages on my site, including
http://tonybaldwin.me/images/
 only that has
 $path = "/path/to/www/images/";


style=\"max-width:200px;\">$file
because that dir is full of images, so I have the index show a 
thumbnail, linking to the larger image.



tony

--
http://tonybaldwin.me
all tony, all the time

Re: converting my local site to be https only access

[rhkramer]

On Sunday, April 30, 2017 09:32:33 PM Gene Heskett wrote:
> All this got started because
> the next firefox says it will not look at a plain http site, and I was

I hadn't heard anything about this, so I tried Googling.  The only thing I've 
found so far is reference to an optional add-on / plugin ("HTTPS Everywhere", 
iiuc) that would allow the browser to look only at ssl (https) pages.  Am I 
missing something?

(Well, I didn't read what I found carefully or completely, I did see some 
snippet of text that said that, in some respects, it would work (or use some 
methodologies) of NoScript, which *might* mean that there might be a way to 
override the plugin manually to view non-SSL pages.)

(Not to say that SSL everywhere wouldn't be a good idea, but, until "legacy" 
websites are converted, we may be missing a lot of the web.)

Re: mutt & maillist digests

[Mike McClain]

On Tue, Apr 25, 2017 at 11:29:18AM -0500, David Wright wrote:
> On Tue 25 Apr 2017 at 17:22:28 (+0200), Vincent Lefevre wrote:
> > On 2017-04-24 15:57:17 -0700, Mike McClain wrote:
> > > I'm running Debian Wheeze on a P3 1/2M memory. Mostly CL.
> > > Mutt 1.5.21 is the culprit ( or am I? )
> > > I subscribe to mailing lists in digest form.
> > > Mutt recognizes the fact when I'm viewing a Debian User digest but not
> > > when I'm reading a 'help-bash' digest from gnu.org. The difference
> > > that's got me is that when I open a DebUser digest I can enter 'v' and
> > > mutt separates the messages so I can respond on list to a particular
> > > message. The help-bash digest doesn't get split like that by mutt so
> > > if I want to reply to a particular message mutt will put the whole
> > > digest into the reply for me to delete all that doesn't apply to the
> > > message I want to send.
> >
> > Perhaps the 'help-bash' digest does not use MIME.
>
> Or perhaps you didn't subscribe to the MIME version if it exists. On
> https://lists.gnu.org/mailman/listinfo/help-bash
> IIRC the digest "radio button" selects only the non-MIME version.
> To get the MIME one you have to go down to the section ridiculously
> labelled:
>
> Help-bash Subscribers
> (The subscribers list is only available to the list administrator.)
>
> and press:
>
> Unsubscribe or edit options
>
> Some non-MIME list digests scrub the attachments and give links to
> see them, which don't work. BTW I've never received a reply to any
> email sent to webmast...@gnu.org about any of their lists/problems.
>
> Cheers,
> David.

Thanks David.
Your directions were clear, concise and accurate.
'help-bash' traffic goes in spurts and though I made the changes in my
subscription the day you posted I only today got confirmation.
Blessings,
Mike
--
"A pessimist sees the difficulty in every opportunity;
an optimist sees the opportunity in every difficulty."
- Sir Winston Churchill (1874-1965)

Re: converting my local site to be https only access

[Gene Heskett]

On Monday 01 May 2017 09:28:10 Greg Wooledge wrote:

> On Sun, Apr 30, 2017 at 09:32:33PM -0400, Gene Heskett wrote:
> > >   STARTFILE:file://localhost/~/
> > >
> > > makes a sensible default.
> >
> > except I am then trapped in my home dir.
>
> *boggle*
>
> You can press 'g' and then paste (or type) whatever URL you want into
> the terminal.  You are not "trapped" anywhere.

I was referring to the usual visitor who likely doesn't know that.

> Of course, the fact that you are in lynx means half the Web will not
> WORK, especially your new-fangled "Let's Encrypt" https site using a
> virtual domain, which is presumably what you are actually trying to
> use lynx to test.
>
> elinks has the same problem.  It can't talk to sites like
> https://paste.debian.net/
>
> I have been told that w3m might not have this problem, but I haven't
> had a chance to try it yet.

Neither have I. I think I have it, but  don't recall that it worked the 
last time.  But does ok now.

Thanks, its back among the living. but not for https.

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

[Greg Wooledge]

On Sun, Apr 30, 2017 at 09:32:33PM -0400, Gene Heskett wrote:
> >   STARTFILE:file://localhost/~/
> >
> > makes a sensible default.
> 
> except I am then trapped in my home dir.

*boggle*

You can press 'g' and then paste (or type) whatever URL you want into
the terminal.  You are not "trapped" anywhere.

Of course, the fact that you are in lynx means half the Web will not
WORK, especially your new-fangled "Let's Encrypt" https site using a
virtual domain, which is presumably what you are actually trying to use
lynx to test.

elinks has the same problem.  It can't talk to sites like
https://paste.debian.net/

I have been told that w3m might not have this problem, but I haven't
had a chance to try it yet.

web site problems on localhost

[Gene Heskett]

Greetings;

I found the problem, something had replaced the index.html, which was a 
link to the front-page.html of my web site with the default apache 
index.html.

Restored that by rm'ing the renamed copy of it, then cp'd the ~ version 
back to the real one, voila! Web page functions normally.

I haven't a clue what did that, I did not run anything that would have 
changed that while attempting to make it do an automatic conversion of 
an http access into an https access. So whatever did do it, I want to 
protect it from everything including me until such time as I remove the 
protections so I can edit it.

But I cannot make those links immutable, chattr won't let me. And 
apparently I can't remove the owners write perms.  So how can I freeze 
these solid until I restore write perms?

Is there a way to do this?

Thank you.

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 

Password is required to mount SD card

[Yvan Masson]

Hi list,

My Dell E6400, running Debian testing with Gnome, has a builtin SD card
reader. Unfortunately, when I insert an SD card it is not automatically
mounted, like it would be with a USB key or a CD/DVD.

If I open "Gnome Disks" to manually mount the card, I am prompted for my
password. This is not too bad, but this is not yet what I would expect
from a user friendly desktop, so I would like to correct this.

GVFS seems to be doing its work when I plug the card in:

$ gvfs-mount --monitor -i
Volume added:   'Volume de 8,0 GB'
  Volume(0): Volume de 8,0 GB
Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
ids:
 class: 'device'
 unix-device: '/dev/mmcblk0p1'
 uuid: '6AD7-8181'
themed icons:  [drive-removable-media]  [drive-removable]  [drive]
symbolic themed icons:  [drive-removable-media-symbolic]
[drive-removable-symbolic]  [drive-symbolic]  [drive-removable-media]
[drive-removable]  [drive]
can_mount=1
can_eject=0
should_automount=0
sort_key=gvfs.time_detected_usec.1493629406193406


I notice that the above "should_automount" is set instead to "1" when I
plug a USB key. This makes me think the problem comes from previous
steps (udev, udisks or policykit) but I am stuck at this point. Any
advice would be welcome, even if it is "report bug against this package".

Regards,
Yvan



signature.asc
Description: OpenPGP digital signature

Re: underscore in xterm sometimes invisible

[Sven Joachim]

On 2017-05-01 08:58 +, David Griffith wrote:

> When I completely log out and log back in, the underscore character
> will be invisible in xterm.  If I do "xrdb .Xresources", subsequent
> xterms created will show underscores.
>
> Investigating further, I tried starting with no .Xresources file.
> This gave me a much-too-small xterm window.  When I do "xrdb -merge
> .Xresources-foobar", which is my normal .Xresources file, I get my
> favored xterm settings EXCEPT that underscores are invisible.  If I
> don't use the "-merge" flag, then that will cause subsequent xterms to
> show underscores. What's going on here?  How can I fix it?

This has been reported in bug #858142[1], but I have not been able to
reproduce it on my systems and I don't know what's going on.

Cheers,
   Sven


1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858142

underscore in xterm sometimes invisible

[David Griffith]

When I completely log out and log back in, the underscore character will 
be invisible in xterm.  If I do "xrdb .Xresources", subsequent xterms 
created will show underscores.


Investigating further, I tried starting with no .Xresources file.  This 
gave me a much-too-small xterm window.  When I do "xrdb -merge 
.Xresources-foobar", which is my normal .Xresources file, I get my favored 
xterm settings EXCEPT that underscores are invisible.  If I don't use the 
"-merge" flag, then that will cause subsequent xterms to show underscores. 
What's going on here?  How can I fix it?


Here's my .Xresources file:

xterm*faceName: DejaVu Sans Mono :antialias=true
xterm*faceSize: 12

XTerm*renderFont: true
XTerm*utf8: 1
xterm*vt100.initialFont: 3
xterm*loginShell: true
xterm*vt100*geometry: 80x24
xterm*saveLines: 2000
xterm*charClass: 33:48,35:48,37:48,43:48,45-47:48,64:48,95:48,126:48
xterm*foreground: rgb:ee/ee/ee
xterm*background: rgb:00/00/00


--
David Griffith
d...@661.org

A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Re: Encrypted flash drives

[Mark Fletcher]

On Mon, Apr 03, 2017 at 03:05:18PM +0200, to...@tuxteam.de wrote:
> 
> > I'm still trying to find a way to make that ghost disk disappear. I am 
> > fairly sure a reboot will sort it but solving the problem without 
> > understanding it is something I only do when there is a good reason, 
> > like some needed service is compromised or something. Not the case here.
> 
> But if I were you, I'd see whether udisks is managing your DE's
> perception of "disks". See [1]. Do you have a binary called udiskctl?
> 
> Another way to try to home in on the problem would be to just "reset"
> the DE's memory, e.g. by completely logging out and back in,
> without rebooting. Is the ghost gone? Then you'd know your DE is
> dreaming. Otherwise it's seeing "something out there".
> 

Just had the first occasion to reboot this machine since this issue 
occurred, and I can now report that a reboot solved it. Both thumb 
drives working as expected after a reboot.

Mark