Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #201782
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: i386 version for chrome |
| Date | 2018-10-28 12:10 +0100 |
| Message-ID | <wNR7c-58w-5@gated-at.bofh.it> (permalink) |
| References | <wNs8O-6Vx-3@gated-at.bofh.it> <wNQb8-4Ah-9@gated-at.bofh.it> <wNQEa-4Jp-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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 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 install does NOT > > > > > > accept it until the network has been brought up. > > > > > > > > > > In another news, you cannot have a default gateway unless it's > > > > > reachable according to existing routing table. > > > > That is the problem, a route -n is without a gateway assignment and > > has been missing since my first attempt to install stretch. > > Ok. > > > > > Its reachable, and listed in every hosts file here by both name > > > > and address. > > > > > > Not before you bring up any non-local network interface. > > > > Then why, after giving the installer all that info, and it uses that > > during the install, does it not have a gateway set after the initial > > reboot or any subsequent reboot? > > Works for me every time I tried it, so I cannot answer that. > > > And nothing you can do will give it a gateway, so you wind up > > playing 10,000 monkeys writing Shakespear, and a reboot for every > > session of nano trying to find the magic twanger that makes it work? > > I have made jessie work on an armhf but its been done after the > > initial reboot. An armbian install that claims its debian 9, is the > > only install out of 5 or 6 from various sources including the > > debian-arm iso twice. > > > > For the jessie install on an r-pi-3b, this /e/n/i works: > > > > auto lo > > > > # The loopback network interface > > iface lo inet loopback > > address 127.0.0.1 > > netmask 255.255.255.0 > > > > auto eth0 > > > > # regular network for coyote.den > > iface eth0 inet static > > address 192.168.NN.12 > > netmask 255.255.255.0 > > gateway 192.168.NN.1 > > > > but it doesn't work if the interface address is given in address/24 > > format so the netmask isn't needed. > > 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. > > To me, thats all the evidence needed > > to point the guilty finger at something in the ifup code. > > Accusing software of something may ease one's mind, but it won't make > it work. Usually, that is. > > > > > > The reason is simple - a default gateway is not 'global', the > > > > > kernel must decide with interface to attach to a default > > > > > gateway route. So you bring a network interface up, add an > > > > > address to it and only then configure a default gateway. > > > > > > > > Then how does one guarantee its done in that order? > > > > > > By using ifupdown, for instance. > > > > > > > And what was changed > > > > to prevent its working in the newer way of doing things? > > They have this wonderful principle at movie industry - show but do not > tell. > Please provide 'ifup -v' output that shows ifupdown misbehaviour, or > it did not happen. Now that I know theres a new syntax in town, I'll try it. When the next install fails. > > > ifupdown works for me that way since etch was testing. > > > If it does not - there's always troubleshooting in form of 'ifup > > > -v'. > > > > As in "ifup -vvv eth0"? > > -vvv is not documented, and I'm too lazy to dig into the source to see > if it does something at all. > > ifdown eth0 > ifup -v eth0 > > > What log file, on stretch, would I find that trace data in? > > Stdout/stderr, as documented by ifup(8). Too volatile, scrolled off screen by the remainder of the boot. I want a log file I can insert into an email. Then we'll all see whats happening. > > Theres not anything in /v/l/syslog w/o the -v. > > And there should not be anything about ifupdown, unless someone > redirects stdout/stderr of /etc/init.d/networking to syslog. Howto? > > Reco -- 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>
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