Re: i386 version for chrome

2018-11-02 Thread Gene Heskett
On Friday 02 November 2018 23:08:52 David Wright wrote: > On Sat 27 Oct 2018 at 11:29:35 (-0400), Gene Heskett wrote: > > On Saturday 27 October 2018 11:03:56 Matthew Crews wrote: > > > Original Message > > > On Oct 27, 2018, 06:58, Curt wrote: > > > > > > On 2018-10-27, Gene

Re: i386 version for chrome

2018-11-02 Thread David Wright
On Sat 27 Oct 2018 at 11:29:35 (-0400), Gene Heskett wrote: > On Saturday 27 October 2018 11:03:56 Matthew Crews wrote: > > > Original Message > > On Oct 27, 2018, 06:58, Curt wrote: > > > > On 2018-10-27, Gene Heskett wrote: > > >> Might be nice, but several of the dependecies

Re: i386 version for chrome

2018-10-29 Thread Brian
On Mon 29 Oct 2018 at 20:37:18 +, Brian wrote: > about, the rewrite could be considered. Baited breath and all that. "Bated", if preferred. -- Brian.

Re: i386 version for chrome

2018-10-29 Thread Brian
On Mon 29 Oct 2018 at 16:11:01 -0400, Gene Heskett wrote: > On Monday 29 October 2018 11:05:32 Michael Stone wrote: > > > On Mon, Oct 29, 2018 at 10:45:50AM -0400, Gene Heskett wrote: > > >Is it a separate bug to fuss about the near total lack of meaning to > > > the man pages for ip and its

Re: i386 version for chrome

2018-10-29 Thread John Hasler
Just file a bug report describing what you did, what you expected to happen, what did happen, and why you believe that the difference constitutes a bug. No need to include a patch. -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: i386 version for chrome

2018-10-29 Thread Michael Stone
On Mon, Oct 29, 2018 at 04:11:01PM -0400, Gene Heskett wrote: Hmmf. If I could make an educated suggestion, but I've not got a clue as to how it is supposed to work, those pages aren't a how-to, so I'd be pinning the tail on the donkey just as if I was blindfolded. But this isn't a party. If

Re: i386 version for chrome

2018-10-29 Thread Gene Heskett
On Monday 29 October 2018 11:05:32 Michael Stone wrote: > On Mon, Oct 29, 2018 at 10:45:50AM -0400, Gene Heskett wrote: > >Is it a separate bug to fuss about the near total lack of meaning to > > the man pages for ip and its children. > > Assuming you have no substantive suggestions, it's not a

Re: i386 version for chrome

2018-10-29 Thread Michael Stone
On Mon, Oct 29, 2018 at 10:45:50AM -0400, Gene Heskett wrote: Is it a separate bug to fuss about the near total lack of meaning to the man pages for ip and its children. Assuming you have no substantive suggestions, it's not a bug report at all, it's just complaining.

Re: i386 version for chrome

2018-10-29 Thread Gene Heskett
On Monday 29 October 2018 10:45:50 Gene Heskett wrote: > On Monday 29 October 2018 08:53:35 Michael Stone wrote: > > On Sun, Oct 28, 2018 at 08:18:44PM +0300, Reco wrote: > > >On Sun, Oct 28, 2018 at 12:56:13PM -0400, The Wanderer wrote: > > >> The definition for netmask I find in that section is

Re: i386 version for chrome

2018-10-29 Thread Gene Heskett
On Monday 29 October 2018 08:53:35 Michael Stone wrote: > On Sun, Oct 28, 2018 at 08:18:44PM +0300, Reco wrote: > >On Sun, Oct 28, 2018 at 12:56:13PM -0400, The Wanderer wrote: > >> The definition for netmask I find in that section is > >> netmask mask > >> Netmask (dotted quad or

Re: i386 version for chrome

2018-10-29 Thread Michael Stone
On Sun, Oct 28, 2018 at 08:18:44PM +0300, Reco wrote: On Sun, Oct 28, 2018 at 12:56:13PM -0400, The Wanderer wrote: The definition for netmask I find in that section is netmask mask Netmask (dotted quad or CIDR) which at a glance would lead me to expect a full CIDR-format address

Re: i386 version for chrome

2018-10-29 Thread Michael Stone
On Mon, Oct 29, 2018 at 08:19:54AM -0400, Gene Heskett wrote: And amazingly to me, I read that RFC, and did not encounter the "netmask 24" syntax anyplace in it. In any event I think all my machines use the dotted quad representations. It should be unsurprising that an internet RFC fails to

Re: i386 version for chrome

2018-10-29 Thread Gene Heskett
On Monday 29 October 2018 07:18:44 Michael Stone wrote: > On Sun, Oct 28, 2018 at 08:18:44PM +0300, Reco wrote: > >On Sun, Oct 28, 2018 at 12:56:13PM -0400, The Wanderer wrote: > >> The definition for netmask I find in that section is > >> netmask mask > >> Netmask (dotted quad or

Re: i386 version for chrome

2018-10-29 Thread Michael Stone
On Sun, Oct 28, 2018 at 08:18:44PM +0300, Reco wrote: On Sun, Oct 28, 2018 at 12:56:13PM -0400, The Wanderer wrote: The definition for netmask I find in that section is netmask mask Netmask (dotted quad or CIDR) which at a glance would lead me to expect a full CIDR-format address

Re: i386 version for chrome

2018-10-29 Thread Michael Stone
On Sun, Oct 28, 2018 at 12:04:54PM -0400, Gene Heskett wrote: On Sunday 28 October 2018 08:43:33 Reco wrote: Hi. On Sun, Oct 28, 2018 at 07:04:02AM -0400, Gene Heskett wrote: > > Ever consider you're doing it the wrong way? > > This will work: > > > > iface eth0 inet static > >

Re: i386 version for chrome

2018-10-29 Thread Curt
On 2018-10-28, Gene Heskett wrote: >> >> I'm reading: >> >> dns-search determines which domain is appended for dns lookups. >> Normally you will specify here the same domain as returned by >> hostname -f.* > > Which is itself and patently wrong for this since the local dns query > path is

Re: i386 version for chrome

2018-10-29 Thread Michael Stone
On Sun, Oct 28, 2018 at 12:18:42PM -0400, Gene Heskett wrote: On Sunday 28 October 2018 10:51:50 Michael Stone wrote: On Sat, Oct 27, 2018 at 10:58:49PM +, Steve McIntyre wrote: >It *looks* like a misunderstood reference to nsswitch.conf maybe: > >hosts: files dns We've been

Re: i386 version for chrome

2018-10-28 Thread Gene Heskett
On Sunday 28 October 2018 15:22:32 Brian wrote: > On Sun 28 Oct 2018 at 12:04:54 -0400, Gene Heskett wrote: > > Maybe its time we let this thread die, it is working now, as I have > > other hardware problems to deal with ATM. With shipping delays > > delays from the Chinglish writers, till around

Re: i386 version for chrome

2018-10-28 Thread David
On Sun, 28 Oct 2018 at 09:59, Gene Heskett wrote: > On Saturday 27 October 2018 18:49:13 Gene Heskett wrote: > > On Saturday 27 October 2018 18:20:16 David wrote: > > > > > > There seems to be an ongoing theme here with lines that look like > > > *search hosts dns > > > popping up in other

Re: i386 version for chrome

2018-10-28 Thread Brian
On Sun 28 Oct 2018 at 12:04:54 -0400, Gene Heskett wrote: > Maybe its time we let this thread die, it is working now, as I have other > hardware problems to deal with ATM. With shipping delays delays from the > Chinglish writers, till around thanksgiving here in the yuuh ess aye. > Needless to

Re: i386 version for chrome

2018-10-28 Thread Gene Heskett
On Sunday 28 October 2018 12:23:35 Reco wrote: > Hi. > > On Sun, Oct 28, 2018 at 12:04:54PM -0400, Gene Heskett wrote: > > > On Sun, Oct 28, 2018 at 07:04:02AM -0400, Gene Heskett wrote: > > > > > Ever consider you're doing it the wrong way? > > > > > This will work: > > > > > > > > > >

Re: i386 version for chrome

2018-10-28 Thread Brian
On Sun 28 Oct 2018 at 12:56:13 -0400, The Wanderer wrote: > On 2018-10-28 at 12:23, Reco wrote: > > > > Gene, if I needed a *normal* result of this sequence I'd asked for > > one. What I've asked was a *broken* one, which does not get a default > > route as a result. > > If I'm understanding

Re: i386 version for chrome

2018-10-28 Thread Reco
Hi. On Sun, Oct 28, 2018 at 12:56:13PM -0400, The Wanderer wrote: > On 2018-10-28 at 12:23, Reco wrote: > > > Hi. > > > > On Sun, Oct 28, 2018 at 12:04:54PM -0400, Gene Heskett wrote: > > [that in a previous message, Reco wrote:] > > >>> interfaces(5), the usual place. > >> > >>

Re: i386 version for chrome

2018-10-28 Thread john doe
On 10/28/2018 5:56 PM, The Wanderer wrote: > On 2018-10-28 at 12:23, Reco wrote: > >> Hi. >> >> On Sun, Oct 28, 2018 at 12:04:54PM -0400, Gene Heskett wrote: > > [that in a previous message, Reco wrote:] > interfaces(5), the usual place. >>> >>> I just checked that man page on wheezy,

Re: i386 version for chrome

2018-10-28 Thread The Wanderer
On 2018-10-28 at 12:23, Reco wrote: > Hi. > > On Sun, Oct 28, 2018 at 12:04:54PM -0400, Gene Heskett wrote: [that in a previous message, Reco wrote:] >>> interfaces(5), the usual place. >> >> I just checked that man page on wheezy, jessie and stretch, and no >> examples are found using

Re: i386 version for chrome

2018-10-28 Thread Reco
Hi. On Sun, Oct 28, 2018 at 12:04:54PM -0400, Gene Heskett wrote: > > On Sun, Oct 28, 2018 at 07:04:02AM -0400, Gene Heskett wrote: > > > > Ever consider you're doing it the wrong way? > > > > This will work: > > > > > > > > iface eth0 inet static > > > > address 192.168.NN.12 > >

Re: i386 version for chrome

2018-10-28 Thread Gene Heskett
On Sunday 28 October 2018 10:51:50 Michael Stone wrote: > On Sat, Oct 27, 2018 at 10:58:49PM +, Steve McIntyre wrote: > >It *looks* like a misunderstood reference to nsswitch.conf maybe: > > > >hosts: files dns > > We've been through this before, explained it thoroughly, he never >

Re: i386 version for chrome

2018-10-28 Thread Gene Heskett
On Sunday 28 October 2018 08:43:33 Reco wrote: > Hi. > > On Sun, Oct 28, 2018 at 07:04:02AM -0400, Gene Heskett wrote: > > > Ever consider you're doing it the wrong way? > > > This will work: > > > > > > iface eth0 inet static > > > address 192.168.NN.12 > > > netmask 24 > > > gateway

Re: resolv.conf (was i386 version for chrome)

2018-10-28 Thread Pierre Frenkiel
On Sun, 28 Oct 2018, Reco wrote: So, answering your original question, you have working name resolution because you have a caching nameserver on your laptop. My money's on dnsmasq. you are right: I had bind installed on my laptop, but on my desktop the bind9 package was missing. After

Re: i386 version for chrome

2018-10-28 Thread Michael Stone
On Sat, Oct 27, 2018 at 10:58:49PM +, Steve McIntyre wrote: It *looks* like a misunderstood reference to nsswitch.conf maybe: hosts: files dns We've been through this before, explained it thoroughly, he never listens, then he brings it back again and the cycle repeats. It's

Re: i386 version for chrome

2018-10-28 Thread Michael Stone
On Sat, Oct 27, 2018 at 01:13:07PM -0400, Gene Heskett wrote: Sorry Steve, but your claim that its simply not true, pulls my trigger, best to duck. You doing it wrong and refusing to listen when people try to correct you is no reason for anyohne else to "duck" as if they're at fault.

Re: resolv.conf (was i386 version for chrome)

2018-10-28 Thread Reco
Hi. On Sun, Oct 28, 2018 at 04:17:17PM +0300, Reco wrote: > Hi. > > On Sun, Oct 28, 2018 at 02:13:30PM +0100, Pierre Frenkiel wrote: > > On Sun, 28 Oct 2018, Reco wrote: > > > > > strace getent hosts bad.solutions > > > > thanks for your answer, but the output is rather obscure

Re: resolv.conf (was i386 version for chrome)

2018-10-28 Thread Reco
Hi. On Sun, Oct 28, 2018 at 02:13:30PM +0100, Pierre Frenkiel wrote: > On Sun, 28 Oct 2018, Reco wrote: > > > strace getent hosts bad.solutions > > thanks for your answer, but the output is rather obscure for a non-guru > user, > except a lot of "no such file or directory" > In

Re: resolv.conf (was i386 version for chrome)

2018-10-28 Thread Pierre Frenkiel
On Sun, 28 Oct 2018, Reco wrote: strace getent hosts bad.solutions thanks for your answer, but the output is rather obscure for a non-guru user, except a lot of "no such file or directory" In particular, I don't see how to explain the difference of behaviour on my 2 computers. best

Re: resolv.conf (was i386 version for chrome)

2018-10-28 Thread Reco
Hi. On Sun, Oct 28, 2018 at 12:53:11PM +0100, Pierre Frenkiel wrote: > On Sun, 28 Oct 2018, Curt wrote: > > > So it seems your config would create the following entries in > > /etc/resolv.conf > > > > nameserver 192.168.NN.1 > > search hosts dns > > > > hi, > I thought it was

Re: i386 version for chrome

2018-10-28 Thread Reco
Hi. On Sun, Oct 28, 2018 at 07:04:02AM -0400, Gene Heskett wrote: > > Ever consider you're doing it the wrong way? > > This will work: > > > > iface eth0 inet static > > address 192.168.NN.12 > > netmask 24 > > gateway 192.168.NN.1 > > > in 20 years, I have never seen that

resolv.conf (was i386 version for chrome)

2018-10-28 Thread Pierre Frenkiel
On Sun, 28 Oct 2018, Curt wrote: So it seems your config would create the following entries in /etc/resolv.conf nameserver 192.168.NN.1 search hosts dns hi, I thought it was better to rename this thread, as the discussion shifted a little. I have a question about resolv.conf: I

Re: i386 version for chrome

2018-10-28 Thread Gene Heskett
On Sunday 28 October 2018 06:30:32 Reco wrote: > Hi. > > On Sun, Oct 28, 2018 at 05:59:52AM -0400, Gene Heskett wrote: > > On Sunday 28 October 2018 02:55:09 Reco wrote: > > > Hi. > > > > > > On Sat, Oct 27, 2018 at 05:35:49PM -0400, Gene Heskett wrote: > > > > On Saturday 27 October 2018

Re: i386 version for chrome

2018-10-28 Thread Gene Heskett
On Sunday 28 October 2018 04:53:10 Curt wrote: > On 2018-10-27, Gene Heskett wrote: > >> Gene, the line > >> > >> > >dns-search hosts dns > >> > >> that you show above does not match anything documented by > >> the manpages on wheezy. I checked > >> interfaces(5) > >> resolv.conf(5) > >>

Re: i386 version for chrome

2018-10-28 Thread Reco
Hi. On Sun, Oct 28, 2018 at 05:59:52AM -0400, Gene Heskett wrote: > On Sunday 28 October 2018 02:55:09 Reco wrote: > > > Hi. > > > > On Sat, Oct 27, 2018 at 05:35:49PM -0400, Gene Heskett wrote: > > > On Saturday 27 October 2018 14:37:38 Reco wrote: > > > > Hi. > > > > > > >

Re: i386 version for chrome

2018-10-28 Thread Gene Heskett
On Sunday 28 October 2018 02:55:09 Reco wrote: > Hi. > > On Sat, Oct 27, 2018 at 05:35:49PM -0400, Gene Heskett wrote: > > On Saturday 27 October 2018 14:37:38 Reco wrote: > > > Hi. > > > > > > On Sat, Oct 27, 2018 at 01:13:07PM -0400, Gene Heskett wrote: > > > > Then give me an install

Re: i386 version for chrome

2018-10-28 Thread Curt
On 2018-10-27, Gene Heskett wrote: >> >> Gene, the line >> >> > >dns-search hosts dns >> >> that you show above does not match anything documented by >> the manpages on wheezy. I checked >> interfaces(5) >> resolv.conf(5) >> resolvconf(8) >> nsswitch.conf(5) >> >> Gene, what are you

Re: i386 version for chrome

2018-10-28 Thread Reco
Hi. On Sat, Oct 27, 2018 at 05:35:49PM -0400, Gene Heskett wrote: > On Saturday 27 October 2018 14:37:38 Reco wrote: > > > Hi. > > > > On Sat, Oct 27, 2018 at 01:13:07PM -0400, Gene Heskett wrote: > > > Then give me an install that can be made to work in a hosts file > > > defined

Re: i386 version for chrome

2018-10-27 Thread Thomas D Dial
On Sat, 2018-10-27 at 13:13 -0400, Gene Heskett wrote: > On Saturday 27 October 2018 11:09:48 Steve McIntyre wrote: > > > Gene Heskett wrote: > > >On Saturday 27 October 2018 09:58:45 Curt wrote: > > > > > >root@coyote:/home/gene/Downloads# dpkg -i > > >vivaldi-stable_2.1.1337.36-1_i386.deb > >

Re: i386 version for chrome

2018-10-27 Thread Gene Heskett
On Saturday 27 October 2018 18:49:13 Gene Heskett wrote: > On Saturday 27 October 2018 18:20:16 David wrote: > > On Sun, 28 Oct 2018 at 05:21, Steve McIntyre wrote: > > > Gene Heskett wrote: > > > >auto eth0 > > > >iface eth0 inet static > > > >address 192.168.NN.2/24 > > > >gateway

Re: i386 version for chrome

2018-10-27 Thread Steve McIntyre
David wrote: >On Sun, 28 Oct 2018 at 05:21, Steve McIntyre wrote: > >There seems to be an ongoing theme here with lines that look like > *search hosts dns >popping up in other places in Gene's system. > >See: >https://lists.debian.org/debian-user/2017/10/msg00857.html

Re: i386 version for chrome

2018-10-27 Thread Gene Heskett
On Saturday 27 October 2018 18:20:16 David wrote: > On Sun, 28 Oct 2018 at 05:21, Steve McIntyre wrote: > > Gene Heskett wrote: > > >auto eth0 > > >iface eth0 inet static > > >address 192.168.NN.2/24 > > >gateway 192.168.NN.1 > > >dns-nameserver 192.168.NN.1 > > >dns-search hosts dns > > > > I'm

Re: i386 version for chrome

2018-10-27 Thread Brian
On Sat 27 Oct 2018 at 17:21:43 -0400, Gene Heskett wrote: > On Saturday 27 October 2018 14:21:23 Steve McIntyre wrote: > > > Gene Heskett wrote: > > >On Saturday 27 October 2018 11:09:48 Steve McIntyre wrote: > > >> You keep on asserting this, but it's patently not true. That's a > > >> standard

Re: i386 version for chrome

2018-10-27 Thread David
On Sun, 28 Oct 2018 at 05:21, Steve McIntyre wrote: > Gene Heskett wrote: > > >auto eth0 > >iface eth0 inet static > >address 192.168.NN.2/24 > >gateway 192.168.NN.1 > >dns-nameserver 192.168.NN.1 > >dns-search hosts dns > > I'm assuming that "NN" is a placeholder you've added, and not copied >

Re: i386 version for chrome

2018-10-27 Thread Gene Heskett
On Saturday 27 October 2018 15:52:53 Matthew Crews wrote: > ‐‐‐ Original Message ‐‐‐ > > On Saturday, October 27, 2018 8:29 AM, Gene Heskett wrote: > > On Saturday 27 October 2018 11:03:56 Matthew Crews wrote: > > > Correct me if I'm wrong, but Wheezy is no longer supported, and > > >

Re: i386 version for chrome

2018-10-27 Thread Gene Heskett
On Saturday 27 October 2018 14:37:38 Reco wrote: > Hi. > > On Sat, Oct 27, 2018 at 01:13:07PM -0400, Gene Heskett wrote: > > Then give me an install that can be made to work in a hosts file > > defined local network that can accept a gateway statement in its > > e/n/i file. The default

Re: i386 version for chrome

2018-10-27 Thread Gene Heskett
On Saturday 27 October 2018 14:21:23 Steve McIntyre wrote: > Gene Heskett wrote: > >On Saturday 27 October 2018 11:09:48 Steve McIntyre wrote: > >> You keep on asserting this, but it's patently not true. That's a > >> standard feature of Debian on all architectures. I understand > >> you've seen

Re: i386 version for chrome

2018-10-27 Thread Matthew Crews
‐‐‐ Original Message ‐‐‐ On Saturday, October 27, 2018 8:29 AM, Gene Heskett wrote: > On Saturday 27 October 2018 11:03:56 Matthew Crews wrote: > > > Correct me if I'm wrong, but Wheezy is no longer supported, and Jessie > > is barely supported. Except as a curiosity, why would you want

Re: i386 version for chrome

2018-10-27 Thread Reco
Hi. On Sat, Oct 27, 2018 at 01:13:07PM -0400, Gene Heskett wrote: > Then give me an install that can be made to work in a hosts file defined > local network that can accept a gateway statement in its e/n/i file. The > default install does NOT accept it until the network has been brought

Re: i386 version for chrome

2018-10-27 Thread Steve McIntyre
Gene Heskett wrote: >On Saturday 27 October 2018 11:09:48 Steve McIntyre wrote: >> >> You keep on asserting this, but it's patently not true. That's a >> standard feature of Debian on all architectures. I understand you've >> seen problems, but it just needs debugging to see how things were >>

Re: i386 version for chrome

2018-10-27 Thread Gene Heskett
On Saturday 27 October 2018 11:09:48 Steve McIntyre wrote: > Gene Heskett wrote: > >On Saturday 27 October 2018 09:58:45 Curt wrote: > > > >root@coyote:/home/gene/Downloads# dpkg -i > >vivaldi-stable_2.1.1337.36-1_i386.deb > >Selecting previously unselected package vivaldi-stable. > >(Reading

Re: i386 version for chrome

2018-10-27 Thread Curt
On 2018-10-27, Pierre Frenkiel wrote: > On Sat, 27 Oct 2018, Curt wrote: > >> At any rate a curl command line that proves inoperable on Wheezy arouses >> the interest of even the most jaded observer. > >I found it on Stretch, but was unable to use it for a ftp transfer, >while ncftp works

Re: i386 version for chrome

2018-10-27 Thread Gene Heskett
On Saturday 27 October 2018 11:03:56 Matthew Crews wrote: > Original Message > On Oct 27, 2018, 06:58, Curt wrote: > > On 2018-10-27, Gene Heskett wrote: > >> Might be nice, but several of the dependecies can only be satisfied > >> if on stretch, and the curl command lines

Re: i386 version for chrome

2018-10-27 Thread Steve McIntyre
Gene Heskett wrote: >On Saturday 27 October 2018 09:58:45 Curt wrote: > >root@coyote:/home/gene/Downloads# dpkg -i >vivaldi-stable_2.1.1337.36-1_i386.deb >Selecting previously unselected package vivaldi-stable. >(Reading database ... 517038 files and directories currently installed.) >Unpacking

Re: i386 version for chrome

2018-10-27 Thread Matthew Crews
Original Message On Oct 27, 2018, 06:58, Curt wrote: On 2018-10-27, Gene Heskett wrote: > >> Might be nice, but several of the dependecies can only be satisfied if on >> stretch, and the curl command lines don't work on wheezy. At all. >> >At any rate a curl command line that

Re: i386 version for chrome

2018-10-27 Thread Pierre Frenkiel
On Sat, 27 Oct 2018, Curt wrote: At any rate a curl command line that proves inoperable on Wheezy arouses the interest of even the most jaded observer. I found it on Stretch, but was unable to use it for a ftp transfer, while ncftp works like a charm. best regards, -- Pierre Frenkiel

Re: i386 version for chrome

2018-10-27 Thread Gene Heskett
On Saturday 27 October 2018 09:58:45 Curt wrote: > On 2018-10-27, Gene Heskett wrote: > >> These folks appear to have found some kind of workaround for the > >> https prefixation syndrome: > >> > >> https://forum.vivaldi.net/topic/28038/how-to-set-a-local-file-as-ho > >>me- page > >> > >> > best

Re: i386 version for chrome

2018-10-27 Thread Curt
On 2018-10-27, Gene Heskett wrote: >> >> These folks appear to have found some kind of workaround for the https >> prefixation syndrome: >> >> https://forum.vivaldi.net/topic/28038/how-to-set-a-local-file-as-home- >>page >> >> > best regards, > > Might be nice, but several of the dependecies can

Re: i386 version for chrome

2018-10-27 Thread tony
On 27/10/2018 13:24, Pierre Frenkiel wrote: > On Sat, 27 Oct 2018, Roberto C. S?nchez wrote: > >> Did you try an absolute path? >> >> file:///home/user/bookmarks.html >   I tried it, and also file://~user... > I set my home page to http://localhost/index.shtml Cheers, Tony

Re: i386 version for chrome

2018-10-27 Thread Gene Heskett
On Saturday 27 October 2018 08:05:13 Curt wrote: > On 2018-10-27, Pierre Frenkiel wrote: > > On Sat, 27 Oct 2018, Roberto C. S?nchez wrote: > >> Did you try an absolute path? > >> > >> file:///home/user/bookmarks.html > > > >I tried it, and also file://~user... > > > >but the problem is

Re: i386 version for chrome

2018-10-27 Thread Pierre Frenkiel
On Sat, 27 Oct 2018, Matthew Crews wrote: Use Chromium instead of Chrome. Chrome is actually based on Chromium. i386 versions of Chromium are in the Debian repos. It's what I do since several years, but I saw that: The biggest difference between the two browsers is that, while Chrome

Re: i386 version for chrome

2018-10-27 Thread Curt
On 2018-10-27, Pierre Frenkiel wrote: > On Sat, 27 Oct 2018, Roberto C. S?nchez wrote: > >> Did you try an absolute path? >> >> file:///home/user/bookmarks.html >I tried it, and also file://~user... > >but the problem is not there, but in the fact that, as I said, >it puts a https://

Re: i386 version for chrome

2018-10-27 Thread Matthew Crews
On 10/27/18 1:19 AM, Pierre Frenkiel wrote: > hi, > I wanted to install chrome on my intel desktop, but the only version I found > is amd64. > Is it possible to get the i386 version? > > best regards, > -- > Pierre Frenkiel > Use Chromium instead of Chrome. Chrome is actually based on Chromium.

Re: i386 version for chrome

2018-10-27 Thread Pierre Frenkiel
On Sat, 27 Oct 2018, Roberto C. S?nchez wrote: Did you try an absolute path? file:///home/user/bookmarks.html I tried it, and also file://~user... but the problem is not there, but in the fact that, as I said, it puts a https:// before.. which of course can't work Anyway, what

Re: i386 version for chrome

2018-10-27 Thread Roberto C . Sánchez
On Sat, Oct 27, 2018 at 12:37:04PM +0200, Pierre Frenkiel wrote: > On Sat, 27 Oct 2018, Andrew Wood wrote: > > > Google no longer produce a 32 bit version but you could try vivaldi > > which is based on Chrome and has a 32 bit version > > https://vivaldi.com/download/ > > > thank you. > I

Re: i386 version for chrome

2018-10-27 Thread Pierre Frenkiel
On Sat, 27 Oct 2018, Andrew Wood wrote: Google no longer produce a 32 bit version but you could try vivaldi which is based on Chrome and has a 32 bit version https://vivaldi.com/download/ thank you. I installed it, but I'm not convince by its features 1/ I want to define my

Re: i386 version for chrome

2018-10-27 Thread Andrew Wood
On 27/10/2018 09:19, Pierre Frenkiel wrote: hi, I wanted to install chrome on my intel desktop, but the only version I found is amd64. Is it possible to get the i386 version? best regards, Google no longer produce a 32 bit version but you could try vivaldi which is based on Chrome and has

i386 version for chrome

2018-10-27 Thread Pierre Frenkiel
hi, I wanted to install chrome on my intel desktop, but the only version I found is amd64. Is it possible to get the i386 version? best regards, -- Pierre Frenkiel