Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #201736 > unrolled thread
| Started by | Pierre Frenkiel <pierre.frenkiel@gmail.com> |
|---|---|
| First post | 2018-10-27 10:30 +0200 |
| Last post | 2018-10-27 14:50 +0200 |
| Articles | 13 on this page of 73 — 17 participants |
Back to article view | Back to linux.debian.user
i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 10:30 +0200
Re: i386 version for chrome Andrew Wood <andrewjameswood@ymail.com> - 2018-10-27 10:40 +0200
Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 12:40 +0200
Re: i386 version for chrome Roberto C. Sánchez <roberto@debian.org> - 2018-10-27 13:10 +0200
Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 13:30 +0200
Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-27 14:10 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 15:10 +0200
Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-27 16:10 +0200
Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 17:00 +0200
Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-27 18:00 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 17:00 +0200
Re: i386 version for chrome Steve McIntyre <steve@einval.com> - 2018-10-27 17:20 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 19:20 +0200
Re: i386 version for chrome Steve McIntyre <steve@einval.com> - 2018-10-27 20:30 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 23:30 +0200
Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-28 00:50 +0200
Re: i386 version for chrome David <bouncingcats@gmail.com> - 2018-10-28 00:30 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 01:00 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 01:00 +0200
Re: i386 version for chrome David <bouncingcats@gmail.com> - 2018-10-28 23:00 +0100
Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-28 10:10 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 12:00 +0100
Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-29 12:00 +0100
resolv.conf (was i386 version for chrome) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-28 13:00 +0100
Re: resolv.conf (was i386 version for chrome) Reco <recoverym4n@enotuniq.net> - 2018-10-28 13:50 +0100
Re: resolv.conf (was i386 version for chrome) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-28 14:20 +0100
Re: resolv.conf (was i386 version for chrome) Reco <recoverym4n@enotuniq.net> - 2018-10-28 14:20 +0100
Re: resolv.conf (was i386 version for chrome) Reco <recoverym4n@enotuniq.net> - 2018-10-28 14:50 +0100
Re: resolv.conf (was i386 version for chrome) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-28 16:40 +0100
Re: i386 version for chrome Steve McIntyre <steve@einval.com> - 2018-10-28 01:00 +0200
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-28 16:00 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 17:20 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 11:30 +0100
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-27 20:40 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 23:40 +0200
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 08:00 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 11:10 +0100
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 11:40 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 12:10 +0100
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 13:50 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 17:10 +0100
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 17:30 +0100
Re: i386 version for chrome The Wanderer <wanderer@fastmail.fm> - 2018-10-28 18:00 +0100
Re: i386 version for chrome john doe <johndoe65534@mail.com> - 2018-10-28 18:10 +0100
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 18:20 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 12:20 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 13:30 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 13:40 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 14:00 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 15:50 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 15:50 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 16:10 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 21:20 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 21:20 +0100
Re: i386 version for chrome John Hasler <jhasler@newsguy.com> - 2018-10-29 21:30 +0100
Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-29 21:40 +0100
Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-29 21:50 +0100
Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-28 20:00 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 20:10 +0100
Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-28 20:30 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 00:40 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 12:20 +0100
Re: i386 version for chrome Thomas D Dial <tdial@acm.org> - 2018-10-28 04:10 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-28 15:50 +0100
Re: i386 version for chrome Matthew Crews <mailinglists@mattcrews.com> - 2018-10-27 17:10 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 17:40 +0200
Re: i386 version for chrome Matthew Crews <mailinglists@mattcrews.com> - 2018-10-27 22:00 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 00:10 +0200
Re: i386 version for chrome David Wright <deblis@lionunicorn.co.uk> - 2018-11-03 04:10 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-11-03 04:40 +0100
Re: i386 version for chrome tony <lists@vanderhoff.org> - 2018-10-27 15:10 +0200
Re: i386 version for chrome Matthew Crews <mailinglists@mattcrews.com> - 2018-10-27 13:50 +0200
Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 14:50 +0200
Page 4 of 4 — ← Prev page 1 2 3 [4]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-10-29 00:40 +0100 |
| Message-ID | <wO2OZ-3xK-3@gated-at.bofh.it> |
| In reply to | #201817 |
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 thanksgiving here in > > the yuuh ess aye. Needless to say I've ordered spares. > > I am having difficulty in understanding the first part of the second > sentence (up to the comma). Is there a derogatory aspect to it? A light dose of snide, combined with poor proof reading, refering to the time it takes China Post to get a 1 oz package to me from wherever the maker is in China. Seems like 20-25 days is too long. Although 10 of this item is probably around 3 or 4 oz. The repair will not be completed until that package arrives, nominally 2 weeks after the rest of the stuff to re-build it in a brand new box is on hand. So the machine will be laid up for nearly a month for a failed $2.30 part, which as it failed blew a $20 breakout board. Classic chain reaction. Similar to that old saw about your tv blowing $50 worth of parts (and labor to replace them) while protecting a 50 cent fuse. But in this case, I'm the one that built it, so I have to look in the mirror to point a finger at the guilty party. ;-) -- 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 <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2018-10-29 12:20 +0100 |
| Message-ID | <wOdKp-1EB-3@gated-at.bofh.it> |
| In reply to | #201802 |
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 >> > > address 192.168.NN.12 >> > > netmask 24 >> > > gateway 192.168.NN.1 >> > >> > in 20 years, I have never seen that syntax used. What man page do I >> > find that format in. >> >> interfaces(5), the usual place. > >I just checked that man page on wheezy, jessie and stretch, and no >examples are found using "netmask 24" All of those indicate in the man page that netmask can either be a dotted quad or a CIDR mask length. >address 192.168.##.##/24 is supposed to be understood as netmask >255.255.255.0, and has worked here forever. And remains in the man 5 >interfaces page. > >And has Just Worked, until now with stretch. Ironically, a CIDR netmask in the address was not recognized until wheezy, which is hardly forever. Prior to that the netmask was mandatory (and only recognized the dotted quad format). >Also, I haven't ever seen an official definition of "CIDR", so its >possible I need tutoring on that. IMO any man page that uses an acronym, >needs to include its definition. Classless Inter-Domain Routing. Since that probably didn't clear anything up, you likely need to do some googling. "CIDR" is probably a better keyword than "Classless Inter-Domain Routing" so this is a good example of a case where the acronym is best understood (and used) without expansion.
[toc] | [prev] | [next] | [standalone]
| From | Thomas D Dial <tdial@acm.org> |
|---|---|
| Date | 2018-10-28 04:10 +0100 |
| Message-ID | <wNJCF-xK-1@gated-at.bofh.it> |
| In reply to | #201756 |
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 > > >Selecting previously unselected package vivaldi-stable. > > >(Reading database ... 517038 files and directories currently > > > installed.) Unpacking vivaldi-stable (from > > > vivaldi-stable_2.1.1337.36-1_i386.deb) ... > > > > > >dpkg: dependency problems prevent configuration of vivaldi-stable: > > > vivaldi-stable depends on libappindicator3-1; however: > > > Package libappindicator3-1 is not installed. > > > > > > vivaldi-stable depends on libc6 (>= 2.16); however: > > > Version of libc6:i386 on system is 2.13-38+deb7u12. > > > > > > vivaldi-stable depends on libgtk-3-0 (>= 3.9.10); however: > > > Version of libgtk-3-0:i386 on system is 3.4.2-7+deb7u1. > > > > > > vivaldi-stable depends on libpango-1.0-0 (>= 1.14.0); however: > > > Package libpango-1.0-0 is not installed. > > > > > > vivaldi-stable depends on libpangocairo-1.0-0 (>= 1.14.0); > however: > > > Package libpangocairo-1.0-0 is not installed. > > > > > >dpkg: error processing vivaldi-stable (--install): > > > dependency problems - leaving unconfigured > > >Processing triggers for menu ... > > >Processing triggers for desktop-file-utils ... > > >Errors were encountered while processing: > > > vivaldi-stable > > > > > >So its not going to work on a 32 bit wheezy, ever. > > > > That's hardly a surprise. Wheezy was released over 5 years ago, and > > isn't even in LTS any more. > > > > >I'll update this machine to a 64 bit stretch if and when the > network > > >works again. Armbian is now working on a rock64, but thats the only > > >variety of nix for arm64 that will accept and use a gateway > statement > > >in its net config > > > > 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 > > broken in your case. :-( > > 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 > up. And the syntax for the deprecated route command is too complex > to > remember, then everybody wants me to use ip-(mumble) for that without > anything that resembles a man page to tell me how to use it for > that. > Thats the singular most obtuse man pages group I've tried to make > sense > of in 35+ years of making networks work starting even before Hayes > modems were the default. > > The arm64 stretch install has, as e/n/i.d/eth0: > > 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 > > And that works, I just got it from that machine with an ssh login. > > So all the stuff that used to be in e/resolv.conf is now in that > file, > but no one in 2 damned years of my asking questions has ever > mentioned > that its been moved or why. To add to the confusion, /etc/resolv.conf > is > now a link that returns a list of nameservers only. But is there any > documentation for all the shuffling? Not thats been converted to a > utf8 > file I can peruse and learn from. #=== # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug enp0s18 iface enp0s18 inet static address 192.168.1.60/24 gateway 192.168.1.1 dns-nameserver 192.168.1.60 dns-nameserver 192.168.1.4 dns-search xxxxxx.org #=== This /etc/network/interfaces file has been in use for 2+ years through several upgrades without issues, so it might not be a really bad pattern to look at. The nameservers at .60 and .4 are authoritative for xxxxxx.org and refer other requests to opendns. > > Sorry Steve, but your claim that its simply not true, pulls my > trigger, > best to duck. And maybe fix a few man pages. Please. ;-) > > -- > 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 <http://geneslinuxbox.net:6309/gene> Best wishes Tom Dial
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2018-10-28 15:50 +0100 |
| Message-ID | <wNUy5-71w-17@gated-at.bofh.it> |
| In reply to | #201756 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Matthew Crews <mailinglists@mattcrews.com> |
|---|---|
| Date | 2018-10-27 17:10 +0200 |
| Message-ID | <wNynT-2jl-3@gated-at.bofh.it> |
| In reply to | #201748 |
[Multipart message — attachments visible in raw view] — view raw
-------- 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 proves >inoperable on Wheezy arouses >the interest of even the most jaded observer. 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 to use a web browser on Wheezy these days? Especially when the expectation of security updates and compatible software for modern web browsing is nearly, if not completely, zero.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-10-27 17:40 +0200 |
| Message-ID | <wNyQW-2t8-9@gated-at.bofh.it> |
| In reply to | #201751 |
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 don't work on wheezy. At > >> all. > > > >At any rate a curl command line that proves > >inoperable on Wheezy arouses > >the interest of even the most jaded observer. > > 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 to use > a web browser on Wheezy these days? Because its main application (LinuxCNC) is married to a 32 bit install, wheezy ATM. I understand a stretch version is being worked on, but the increased latency involved in a 64 bit context switch is very very hard to tolerate on real machinery. Real time kernels that actually work are virtually non-existant on 64 bit machinery. I have one that almost works on armhf, but it loves to throw away mouse and keyboard events, but that goes away, or gets worse if you reboot. And a good reboot is good till the next power bump on that machine, running Jessie.. > Especially when the expectation of > security updates and compatible software for modern web browsing is > nearly, if not completely, zero. Its certainly getting that way. -- 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 <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Matthew Crews <mailinglists@mattcrews.com> |
|---|---|
| Date | 2018-10-27 22:00 +0200 |
| Message-ID | <wNCUy-4Pf-9@gated-at.bofh.it> |
| In reply to | #201753 |
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, October 27, 2018 8:29 AM, Gene Heskett <gheskett@shentel.net> 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 to use > > a web browser on Wheezy these days? > > Because its main application (LinuxCNC) is married to a 32 bit install, > wheezy ATM. > Gotcha, I suspected it was something like that. I personally wouldn't connect such a device to the internet unless I had to, or if I had firewalls configured correctly. But I'm going to assume you know what you're doing in that regard :) I would prepare for the inevitable time when a Chromium-based web browser simply becomes unsupported on i386. Also I was incorrect about Wheezy support. It still has commercial Extended LTS support for another seven months. https://wiki.debian.org/LTS/Extended Looks like the LinuxCNC folks will need to plan on migrating to a later version of Debian soon.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-10-28 00:10 +0200 |
| Message-ID | <wNEWl-6gd-5@gated-at.bofh.it> |
| In reply to | #201763 |
On Saturday 27 October 2018 15:52:53 Matthew Crews wrote: > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On Saturday, October 27, 2018 8:29 AM, Gene Heskett <gheskett@shentel.net> 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 to use a web browser on Wheezy these days? > > > > Because its main application (LinuxCNC) is married to a 32 bit > > install, wheezy ATM. > > Gotcha, I suspected it was something like that. > > I personally wouldn't connect such a device to the internet unless I > had to, or if I had firewalls configured correctly. But I'm going to > assume you know what you're doing in that regard :) > > I would prepare for the inevitable time when a Chromium-based web > browser simply becomes unsupported on i386. > > Also I was incorrect about Wheezy support. It still has commercial > Extended LTS support for another seven months. > https://wiki.debian.org/LTS/Extended Looks like the LinuxCNC folks > will need to plan on migrating to a later version of Debian soon. They are working on it. For stretch. The problem is that its also expected to run on 25+ yo hardware too. Telling some shop owner who isn't computer literate, that he has to pop for a new computer, and a consultant to come in and make it work, upping the cost for that new hardware and the consultant to marry it all together, brings the cost of free software to often north of 5 grand per machine since the consultant likes to eat and have a warm place to sleep while he is doing it. He, not figuring on that, will junk the machine and buy a new one with a fanuc control, for 30-60 grand just to get that spot on the floor back to making money, but with 20% of linuxcnc's capability (but his machinists can understand the loss as that loss of capability translates into lost piecework bonuses for them). Fanuc and several others treat the specialty stuff that LCNC can do OOTB as extra fee addons that because the shop owner is not savvy, costs him a bunch. So the LCNC developers have to jump thru burning hoops to try and recover the lost latency that jumping to a 64 bit kernel costs them. I'm not doing the broadcast consulant scene anymore, not at 84 and taking care of a wife dying from copd. I think the characterization is "between a rock and a hard place". Thanks Matthew. -- 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 <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2018-11-03 04:10 +0100 |
| Message-ID | <wPUtX-5hf-11@gated-at.bofh.it> |
| In reply to | #201753 |
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 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 proves > > >inoperable on Wheezy arouses > > >the interest of even the most jaded observer. > > > > 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 to use > > a web browser on Wheezy these days? > > Because its main application (LinuxCNC) is married to a 32 bit install, > wheezy ATM. > > I understand a stretch version is being worked on, but the increased > latency involved in a 64 bit context switch is very very hard to > tolerate on real machinery. Real time kernels that actually work are > virtually non-existant on 64 bit machinery. I have one that almost works > on armhf, but it loves to throw away mouse and keyboard events, but that > goes away, or gets worse if you reboot. And a good reboot is good till > the next power bump on that machine, running Jessie.. That explains why you run wheezy at all. But it doesn't explain why you run a web browser on wheezy or on a computer that's required to have good realtime performance. I thought you ran a LAN of computers there. > > Especially when the expectation of > > security updates and compatible software for modern web browsing is > > nearly, if not completely, zero. > > Its certainly getting that way. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-11-03 04:40 +0100 |
| Message-ID | <wPUX0-5x1-7@gated-at.bofh.it> |
| In reply to | #202007 |
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 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 proves > > > >inoperable on Wheezy arouses > > > >the interest of even the most jaded observer. > > > > > > 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 to use a web browser on Wheezy these days? > > > > Because its main application (LinuxCNC) is married to a 32 bit > > install, wheezy ATM. > > > > I understand a stretch version is being worked on, but the increased > > latency involved in a 64 bit context switch is very very hard to > > tolerate on real machinery. Real time kernels that actually work are > > virtually non-existant on 64 bit machinery. I have one that almost > > works on armhf, but it loves to throw away mouse and keyboard > > events, but that goes away, or gets worse if you reboot. And a good > > reboot is good till the next power bump on that machine, running > > Jessie.. > > That explains why you run wheezy at all. But it doesn't explain why > you run a web browser on wheezy or on a computer that's required to > have good realtime performance. I thought you ran a LAN of computers > there. > I do, but except for an r-pi-3b running stretch, all the rest are running wheezy for the same reason. There is one stretch, a bare bones armbian running on a rock64. And this is the only machine with a comfy office chair in front of its keyboard. Thats in deference to the aches & pains of an 84 yo body. :( > > > Especially when the expectation of > > > security updates and compatible software for modern web browsing > > > is nearly, if not completely, zero. > > > > Its certainly getting that way. > > Cheers, > David. Thanks David. -- 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 <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | tony <lists@vanderhoff.org> |
|---|---|
| Date | 2018-10-27 15:10 +0200 |
| Message-ID | <wNwvL-1be-11@gated-at.bofh.it> |
| In reply to | #201741 |
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
[toc] | [prev] | [next] | [standalone]
| From | Matthew Crews <mailinglists@mattcrews.com> |
|---|---|
| Date | 2018-10-27 13:50 +0200 |
| Message-ID | <wNvgl-fS-3@gated-at.bofh.it> |
| In reply to | #201736 |
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. i386 versions of Chromium are in the Debian repos. # apt install chromium
[toc] | [prev] | [next] | [standalone]
| From | Pierre Frenkiel <pierre.frenkiel@gmail.com> |
|---|---|
| Date | 2018-10-27 14:50 +0200 |
| Message-ID | <wNwcp-OI-5@gated-at.bofh.it> |
| In reply to | #201742 |
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 is
based on Chromium, Google also adds a number of proprietary features to
Chrome like automatic updates and support for additional video formats.
Unfortunately, they only provide a 64 bit version.
best regards,
--
Pierre Frenkiel
[toc] | [prev] | [standalone]
Page 4 of 4 — ← Prev page 1 2 3 [4]
Back to top | Article view | linux.debian.user
csiph-web