]Ethernet over twisted pair was designed to leverage standard structured ]wiring - the RJ45 ports spread throughout offices and so on are not ]"ethernet" ports but "structured wiring" ports intended from the off to ]carry a broad range of different traffic (phone, CCTV, audio etc) without ]the need to rip up the floorboards for each new connection.
Yea - what ever. So why do you boys allow youself to get carried away in trying to justify the need for a national-railway-system to connect ONE rPi to ONE PC?
What happened about the bloke who wrote that he wanted to take rPi with him when he went down to Mexico, and he could just plug into the hotel TV?
If rPi had/has code to drive a 3Gdongle, he could have inet access too. I don't need a keyboard to operate the rPi, since I solved the problem. `eject` switches the dongle, OK; but wheres `pppd`? Or what does Debian use, in place of `pppd`?
Can you spell m i n i m a l ?
Isn't that the idea of rPi? To escape the bloated WinTel monopolists?
All this national-railway-station clap trap seems to be missing the point that its TCP/IP that brings you that, and nothing whatsoever to do with ethernet!
If you want to install packages, then you will need a network connection (that does not need to be ethernet - however that is the easiest one to use for 99%+ of users). Now if you want to run TCP/IP over your 3G device, then you may need to do some setup work first getting the packages onto the device by other means. If you have a PC with ethernet and a working 3G connection, then the obvious answer would be to plug the pi into the PC via ethernet, bring up the 3G connection on the PC, and then bridge the ethernet and 3G virtual adaptors such that the PC acts as a gateway.
Yes that was the one route which I was persuing, except I didn't find how to "bridge the ethernet and 3G virtual adaptors".
The alternative of getting pppd installed [manually], has now allowed the RPi to `apt-get install ` and give the illusion of power and you-know-what-you're-doing. link2, dvtm, gpm each took average 6 secs on-line time to install!
Is that without the national-railway-system/ethernet?
I agree with you, and in the UK context, where an ethernet connection is apparently as common as piped water, that was the obvious choice. Especially for model A with only one USB. I'm guessing that few people get use of the RCA? I've got a 70's TRS80/Z80 microproc RCA b/w monitor which is great with RPi.
Also I don't know what TV systems are used around the world, and it's changing.
I had to google "mc"... looks like it's "Midnight Commander". Do you call that an "essential utility"? And "gpm" appears to be "General Purpose Mouse server"...
Kids these days...
Posted on a Mac, which has essential utilities like "grep", "sed", "awk", "tr", "dc", etc... but not "mc", and "not "gpm".
gpm is really useful it lets you copy and paste between virtual consoles which can be handy for moving ssh keysm copying URLs around and other tedious sysadmin tasks.
And both are an "apt-get install" away. The source of that apt-get can be a local USB drive you can carry around.
Likewise; I see emacs, lynx, bash and a dozen other utilities sufficently valuable to have access to them mandatory in my support contracts with third parties. They are not in the standard rpi install either; but I am completely fine with having them available on a small apt-get script, to be performed late in any install of a debian-based linux.
I am sure my tools have a lot more merit than random utilities like the ones you mention if you count hack-hours of the proponents. But I let this gripe lie. The install is fine as it is. I can even manage with vi if I have to; but I am a LOT less productive.
What makes me a little bit stern in my comments is that _all_ of these gripes are standard linux newbie gripes that have been fleshed out in other newsgroups thousands of times, and have the answers well googlable from at least a dozen different sources each.
I seem to be the only experiences Linux sysadmin in this group; because there has been no other answers forthcoming. I therefore stand by my comment about the lack of linux skills here. This is fine, PROVIDED you are willing to learn.
I know that this is different from windows; in that you _can_ open the bonnet of this one and look around inside. There are even multiple layers there. udev is just one of them. They usually work fine in their default setting, but sometimes this "open bonnet" philosophy comes back to bite you. This has been discussed to death in the kernel* lists, and there is a consensus of letting it be; as long as the simple stuff works right out of the box; then the advanced stuff can require some config file writing.
This part reflects directly upon the quality of the OS experience as well.
When it comes to device discovery the architects of windows have repeatedly stated that this is the single biggest technical obstacle to both responsiveness and stability for the windows platform; but due to the market conditions in which windows operates they are more or less powerless in fixing it. They have literally hundreds of thousands of third party binary drivers to get working, and just having them work at all is a tall order in itself.
Linux has fixed it, with good help from the OpenBSD people. It involved fixes to > 10k drivers and rewrites of several thousand of these. The discovery process is totally asynchronous as of 2.6, and this means that like interfaces can be differently named between boots. If this is a problem you can do explicit name assignments. Normally, it isn't, therefore the default install is usually fine. It speeds up the boot process enourmously, and makes the system a lot more responsive when the kernel has more control over which interrupts goes where etc.
Compare the actions of plugging in my 2001 vintage microsoft mouse (which remains my favourite pointing tool) into a linux computer vs a microsoft windows machine. The windows machine doesn't recognise it because of the age; and asks for a driver. (for a HUD device!) the Linux box just makes a brief popup "new mouse discovered: \nDo you want to make this your primary ponting device Y N". (asked the first time only).
Yes, with one-cough each, the ExpertSystem installed them. `gpm` is the most essential because it's the most basic/primitive way of moving text between locations. And text is the most basic/primitive repository of our knowledge [w.r.t.computing].
`mc`is essential, because your value is NOT in some monster browser, but rather in your file-tree. Like the office-of-past-days, with various devices [filing cabinets ...clouds]. `mc` can walk-around the file tree and do all the various house keeping jobs VISUALLY. Instead of having a centralised monster, you eg. visit the individual projects, via `mc`, and do-the-job at the relevant node of the dir-tree.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.