On Mon, 05 Jan 2015 13:43:47 -0600, Linda Kateley <lkateley at kateley.com> wrote: > I always like a good joke, please share? > > I actually am in the process of picking a linux(for zol). I have always > dug suse as a company, but ubuntu seems more practical.. redhat seems to > have gone too commercial > > So what linux do you use and why? I use debian because: 1. apt - advanced package tool - easy to use, so easy to install packages. 2. NOT on the bleeding edge! I hate it when stuff you use breaks on you. Although, sometimes, I do wish they were a little farther along because if you get new hardware, sometimes debian stuff is too far behind. So, I could switch distros solely for hardware isues if absolutely necessary. 3. Stuff seems tested heavily. While I use GTK+ (which seems like a piece of GNOME), I've had to drop GNOME as my DesktopEnvironment because I don't like the changes made when they went to GNOME 3. Instead, I use LXDE. But I don't like LX-Terminal, so I use ROX-Terminal (roxterm). roxterm seems to operate with a lot of features of gnome-terminal, and some additional stuff of its own. The WindowManager I use is openbox. Now, before, I was running openbox and had no DesktopEnvironment at all, so I'm already familiar with openbox, and what's cool about openbox is that it is easy to add stuff to the menus, whereas, with GNOME menus, I don't have a clue about how to add stuff. I'ven't figure out how to do pipe-menu-s yet with openbox, but it SOUNDS cool. The one cool thing about LXDE is that it gets the following right: : This computer is a host. : This computer has two network interfaces (Windows people call these NIC cards or NIC interfaces). : Oh, look, there's an Ethernet network interface. : Oh, look, there's a WiFi interface. And there's WiFi stations in this area. : Oh, look, the Ethernet cable is connected. : Oh, look, both the Ethernet and the WiFi want to use the same IP address. : Now, for the part where NO OTHER NETWORKING SOFTWARE SEEMS TO DO RIGHT... DRUM ROLL, PLEASE... : I think that since this host went through the trouble of having a cable plugged in that I will connect to Ethernet and disconnect from WiFi. =========== Summarizing: When you find a HOST (i.e., a computer that is NOT a ROUTER) with an IP address the same for both interfaces, Ethernet **TRUMPS** WiFi! =========== Whenever I have to stoop to using Win7, I have to go thru the "disable one interface" and "enable the other interface" way more times than you'd think because it was last set "the other way". But wataaya expect from Micro$oft? I use *bash* as my shell, although I think that *zsh* is probably more capable--it's just that I don't think I can cram in any more shell syntax into my thick head, anymore. Lastly, I like that there is an ARM version of Debian Wheezy Linux that others have adapated to use with Android phones. Although you don't have to pay, it is asked that you pay what you can, anyhow, therefore, it's not open source, but, tell me, can you figure out how to have a program that you wrote (nonGUI of course) that you can run on your phone without rooting the phone? My favorite is plugging your android into your laptop via the usual USB data cable and running X (however, they tell me the communication is not via the usual X stuff but uses the same as the protcol VNC uses--to be more specific--tightVNC//Up pops an xterm via twm). Another thing with the app that launches Debian Wheezy: It uses ptrace() to make it so that you can both be debian-user-root (to use apt-get, for example), and yet not to require having the phone rooted. Cuz if you have the phone rooted, you could do a real chroot. I'ven't figure out how this works yet. OK, sorry, this was TMI (Acronym expansion: (T)oo (M)uch (I)nformation). > > linda > -- Name: Steve Trapp Homepage: http://steventrapp.home.comcast.net Email: stevetrapp **AT** comcast **DOT** net Locale: en_US.UTF-8 | Location: Upper Midwest