|
Marc Clifton wrote: It'll eventually stop raining
In Wales?
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
But at least it wasn't YOUR code. Elephanting customer can't follow a spec.
|
|
|
|
|
"I'm so annoyed carrying all these loyalty cards around. Why can't I have one card that works in all stores?"
|
|
|
|
|
Good one 
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
That sounds an awful lot like a credit card.
|
|
|
|
|
I thought you said it was semi hard (8)
|
|
|
|
|
I thought you said it
MISHEARD
was semi hard (Anag)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
No - she's a nice girl, but Herself would complain.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
A little part of my home automation is based on a raspberry Pi running a web app. Since I am on the DIY track, I installed a Debian distro out of the box (= downloaded an image from the internet) and ... linux is a real PITA. I have to write a sudo command in front of all other commands just for rights elevation (Really ?) or continuously switch between root session and own session. This packages thing is completely cryptical. You have 10,000 different solutions to a same problem, depending on the 10,000 different tastes of your operating system version. Elementary things are requiring 5 configuration files to be modified, either with root or normal sessions (but not both). Some files with dot-seprated-filenames-parts are actually directories and no files.
Mind you, I had to do everything over the command line because of ssh remote connection, so it is probably easier going over the desktop.
But I still think this remains a geek activity. There is nothing out there that makes you want to deep dive into it, unless you have countless hours to lose doing and redoing the same all over again.
|
|
|
|
|
Rage wrote: this remains a geek activity.
This is where Ubuntu makes an improvement, it is packaged in a more user friendly way. Gone are the endless command lines to update components, instead there is a package adder app.
|
|
|
|
|
I see you've never had it break on you.
When that happens, you'll be back to the command line to try and fix it.
|
|
|
|
|
I never used it actually, always used the command line! 
In fact I dont know why Rage is finding this difficult, as an engineer this should be easy, and it certainly is easier than when getting .net to work properly when windows decides to screw you around!
|
|
|
|
|
It is not difficult, it is only a PITA. 
|
|
|
|
|
As far as updating anything on Linux goes, I prefer the command line as well.
sudo apt-get update
sudo apt-get upgrade
Or just
yum update
Done. Most GUI-based package managers require an awful lot of clicks by the time you're done. Not to mention that they often hide in different menus on different distributions and I can never remember where to find them.
|
|
|
|
|
dandy72 wrote: Not to mention that they often hide in different menus on different distributions and I can never remember where to find them.
Yeah, that is true.
|
|
|
|
|
Debian is a bit harsh. Ubuntu is more friendly.
Just try to do anything from the Windows command prompt and you are going to bless Linux.
|
|
|
|
|
Rage wrote: There is nothing out there that makes you want to deep dive into it, unless you have countless hours to lose doing and redoing the same all over again.
What do you do for a living? We do something only twice, for the first and the last time.
(Captain Kirk voice) Lazyness is our business!
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
Rage wrote: I have to write a sudo command in front of all other commands just for rights elevation (Really ?)
Yes 
Rage wrote: Mind you, I had to do everything over the command line because of ssh remote connection, so it is probably easier going over the desktop.
Clicking through a thousand menu's in an ever-changing UI is easier than executing a script on a command line?
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Rage wrote: so it is probably easier going over the desktop.
No it isn't. The desktop environments I've worked with don't support anything but basic BS, and even then, doing something like moving a file from one folder to another can be a WTF experience. For example, I couldn't even change the date/time on my BeagleBone from the LXE desktop.
Rage wrote: But I still think this remains a geek activity.
Absolutely. And in particular, the nasty kind of narcissistic, masochistic, self-flagellating with delusions of godhood kind of geek. Klingons run in terror from these geeks.
|
|
|
|
|
It's changed, the UNIX world that is (Linux acolytes gasping). Back when I did Unix for a living, I had to deal with Sun OS, Solaris (Sparc, x86), HPUX, AIX, and I am almost certain I'm missing one, ha! Ultrix and Digital Unix. It all depended on what machine the customer wanted host our hardware.
Although all of these flavors had their differences, there was a general method to the madness.
This: The Red Book[^] saved my life. Then came Linux. I guess this is the follow on:
The not so red book[^]
I remember fond days of vi, *easily* configuring the network, NEVER having to worry about drivers other than my own, etc.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
For one of my classes in college...I don't remember if it was C or Unix...probably Unix.
I chose Coherent[^]. I have no idea why, but I did.
So when Linux came around, I wasn't all that wowed by someone who wrote their own version of Unix. 
|
|
|
|
|
Rage wrote: I have to write a sudo command in front of all other commands just for rights elevation (Really ?) or continuously switch between root session and own session.
By that, do you mean you actually login with the root account, run your commands, then switch back to the original account?
Are you not familiar with 'su' as an alternative to sudo?
|
|
|
|
|
su is bad practice, or so the internet told me. sudo -i instead.
|
|
|
|
|
If it saves you from entering 'sudo' in front of 10 different commands in a row, then frankly I see nothing in running su, running the 10 commands, then exit.
Besides - logging in as root is just as bad IMO, if not worse, because once you've logged in, who wants to constantly switch back and forth between sessions...?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
