Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #201772
| From | Thomas D Dial <tdial@acm.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: i386 version for chrome |
| Date | 2018-10-28 04:10 +0100 |
| Message-ID | <wNJCF-xK-1@gated-at.bofh.it> (permalink) |
| References | <wNApI-3ui-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web