On 26.11.11 12:40, Jeremy Visser wrote:
Thus spake Erik Christiansen:
On 25.11.11 20:38, Russell Coker wrote:
It's Debian. I just put the ip and route commands on "up" lines in /etc/network/interfaces.
That sounds easier¹ than MSWindows.
Having a point-and-drool GUI interface to do the job doesn’t count as being easy? Sheesh.
This old dog finds them hard to learn, mostly because they are difficult to navigate (I suppose anything is, the first time.) There doesn't seem to be anything to hold onto to remember the fix for next time, as compared to a command line invocation, which does stick. Or can succinctly be recorded in extracranial memory, for when the wetware starts showing bad blocks, with age. Ease is relative. Nearly forty years now¹, poking keys at the command line, does make that direct-access-to-everything interface easier for most things, than scurrying up and down menus in a graphical maze. Where content is graphical, as in schematic capture, PCB layout, and even a web browser, I'll spend the weeks to master the interface specific to that application. But not for sysadmin, programming tools, editors, etc. A quarter of a century spent as a coder makes text easier to grok. Erik ¹ Counting those uni days, hammering at an ASR33. The Hollerith card punch wasn't on-line command line, but similar mind-think. -- Habit is habit, and not to be flung out of the window by any man, but coaxed down-stairs a step at a time. - Mark Twain, "Pudd'nhead Wilson's Calendar