On Wednesday 06 July 2016 14:33:25 deloptes wrote: > Gene Heskett wrote: > > On Monday 04 July 2016 03:46:38 deloptes wrote: > >> Gene Heskett wrote: > >> > But, anything that looks or acts like network manager has been > >> > removed from my system. So any comments I might make about NM > >> > should be taken as the best swag* I can make based on 18 years of > >> > running linux. > >> > >> NM is useful on notebooks that change locations, interfaces etc. If > >> one uses a home network with many computers I would advise setting > >> up proper dhcp and perhaps name server. You don't have to take care > >> of each machines own files. But this is usually an individual > >> preference. > >> > >> regards > > > > The last time, several years ago, that I tried using dhcp on my > > lappy, which is itself an antique, I had 3 problems. > > > > 1. NM insisted on using the bcm-4318 radio in the lappy even if it > > was powered down by the switch. It totally ignored a radio in a usb > > dongle that actually worked where the bcm-4318 never worked for more > > than 1 minute, even when useing the drivers from xp that came > > installed to run it. Rebooting to xp disclosed that this pos radio > > was junk from the gitgo. > > You have the strangest problems. Amazingly you solve them the "gene" > way. > > > 2. Getting it setup via dhcp with a usb radio dongle, so I could sit > > down while out in the shop, and write gcode for one of the 2 > > machines out there worked flawlessly over an ssh -Y machinename > > connection, until I wanted to ssh -Y lappy, which is its own name > > from the house machine. So the dns lookup which NM should have set > > up, wasn't there, forcing me to string a 25' hunk of cat5 plugged > > into its ethernet port. Adding its ip address and name to all the > > hosts files, and fixing all the network related files to be > > immutable after edited correctly, and then its just one of the > > family. > > I never had a problem using dhcp. At home we have a server (many > disks) that has dhcpd and dns server running. This serves the local > network. It stays behind a firewall. The router has wireless access > point and is infront of the firewall. The router has also a dhcpd and > nameserver, but when connecting via wireless I use the vpn (running on > the firewall). > > > Strangely, when NM found it couldn't rewrite those files, it made no > > complaint in any log. And it didn't spin its wheels, burning up the > > cpu either. > > > > 3. I've left it that way in all subsequent installs. Now I remove > > NM and other than making /etc/resolv.conf a real file, its a 10 > > minute job after a fresh install to have a working network > > regardless of which socket I plug its cat5 cable into. With 2, 8 > > port switches available, soon to be 3 as I'll need another in the > > garage as I bring a bigger Sheldon 11x36 lathe to life with > > LinuxCNC. So the end of the cat5 I strung thru the nether regions > > of the house to get to the garage, will eventually have an 8 port > > switch on the end of it. That cable was 4 days getting run, a right > > PITA. > > I had the issue with the resolv.conf being not a symlink when > experimenting, but I prefer the standard solution, which seems to be > working fine. > > I takes 1minute to set a new machine up. Just add mac/hostname to dhcp > and hostname/ip to bind and restart both - done. Many physical and > virtual machines reside there. I even use the conf files to remember > what is setup where :) In what files, plz? I found the man pages quite opaque in that regard. > > I also prefer cat5 because of nfs, but my wife uses heavily the > wireless from here (smart) phone. I think she finds typing with one > finger on the touch screen sexy :) I replaced all use of nfs with its finickety file system setups about 6 months back with a key file acl in sshfs, so no login. It Just Works(TM). Dr Klepp on this list can probably advise you how. Putting all three of the current cnc machines to full read/write accessability, once the keys have been traded, is as simple as: ========================= #!/bin/bash sshfs gene@shop:/ /sshnet/shop sshfs gene@lathe:/ /sshnet/lathe sshfs gene@GO704:/ /sshnet/GO704 ========================= And they are magically available to me as user 1000. > The great thing of FOSS software is you can fix and customize it the > way you like it. Thumbs up, Gene! Absolutely, and too few, particularly those coming in from a windows environment, can understand that. My mind was never poisoned by that, thank $DIETY. My trail thru multiuser/multitasking operating systems starts in about 1985 when I discovered os9 for the trs-80 Color computers, very much like unix but could run on a 16 bit cpu. From there to amigados because we used half a dozen of them for graphics generators at the tv station, Jim Hines and I wrote some PD and some commercial SW in that language, the PD was a EzCron that didn't burn cpu in a wait loop, and the commercial program was EzHome to run a housefull of X10 stuff. I still do that but with heyu. And finally in '98 to a RedHat 5 system I built at work and took home to replace the aging A2k I had been using for a decade. And we still, to this day, do not have a programming language with the power of William (Bill) Hawes "ARexx" which was a huge, went right to the hardware superset of Regina for Linux. You could write assembly language powerfull SW in plain English. Bill should have collected at least half of what Commie sold it for, on a per copy basis. But he never got a damned dime. Commie stiffed a lot of people when the two top guys went to Bermuda, along with any money that was in the bank account at the time. 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>