Language Selection

English French German Italian Portuguese Spanish

Commandline Interface

All Cli, all the time
37% (348 votes)
Everyday
36% (340 votes)
Once in a while
15% (144 votes)
Rarely, if I have to
9% (84 votes)
Nope, never, no way
3% (24 votes)
Total votes: 940

Perhaps a better question...

If you're using this as a measure of relative user sophistication, then perhaps a better question is how many have written their own scripts (in shell language, python, ruby, perl, or lua or whatever) to help with system administration or automating common repetitive tasks?

After all, even the rawest Ubuntu newbie user uses the cli to install (mostly the non-free) stuff.

For my own combination of desktop use and server administration, I'm somewhere between "every day" and "once in a while", but closer to "every day".

Not very sophisticated.

gfranken wrote:
If you're using this as a measure of relative user sophistication, then perhaps a better question is how many have written their own scripts (in shell language, python, ruby, perl, or lua or whatever) to help with system administration or automating common repetitive tasks?

After all, even the rawest Ubuntu newbie user uses the cli to install (mostly the non-free) stuff.

For my own combination of desktop use and server administration, I'm somewhere between "every day" and "once in a while", but closer to "every day".


I write scripts, but they're very elementary affairs. Nevertheless, they save me an incredible amount of time. It's pretty amazing what you can do with a simple knowlege of commands, a little ingenuity, and search and replace.

Scripting

My own scripts are typically in Ruby, Python and PHP (the latter for web based stuff).

Unfortunately, my bash shell programming skills are weak, and I've always planned to take a couple of days to do a crash course study marathon of bash shell programming. No excuse for not doing it, just lazy, I guess.

I don't like Perl, but I've customized a few Perl scripts to meet my needs, with reference book in hand.

In my opinion, basic system scripting creation/modification is one of the steps from basic Linux user to intermediate user. Of course the real gurus (which I'm not) can do it in their sleep.

Ahhhh, yes! Servers!

I was just trying to be funny, but servers would certainly explain it.

22 per cent of you never use the GUI at ALL?

I'd estimate that 17 per cent of the rest of us actually believe you.

Re: 22 per cent of you never use the GUI at ALL?

It really depends on the distribution.
I use ArchLinux. Our package manager is called pacman. It's only cli. There is no working gui frontend for it.
Cli doesn't mean unfriendly and vim is very user friendly.

I believe it.

I think it's conceivable that I could live without a GUI for a month at a time. If I had to right now, I could... it might be a little uncomfortable at first, but I'd get used to it real quick. I can already edit files, compile programs, surf the web, remotely control my school's development server, play games, print and scan, play music and watch videos... I can also make use of my six available virtual terminals, or I can fire up Screen and be able to run multiple programs simultaneously in one terminal.

I think I'll make that my goal for January: Go the whole month without using a GUI (except for when I absolutely have to use one of the school computers running Windows, in which case I'll immediately SSH into my machine with Putty 99% of the time.

__________________________________________________________________
Ubuntu is lame as a duck- not the metaphorical lame duck, but more like a real duck that hurt its leg, maybe by stepping on a land mine.

I'm sure you could do it.

Spinlock wrote:
I think it's conceivable that I could live without a GUI for a month at a time. If I had to right now, I could... it might be a little uncomfortable at first, but I'd get used to it real quick. I can already edit files, compile programs, surf the web, remotely control my school's development server, play games, print and scan, play music and watch videos... I can also make use of my six available virtual terminals, or I can fire up Screen and be able to run multiple programs simultaneously in one terminal.

I think I'll make that my goal for January: Go the whole month without using a GUI (except for when I absolutely have to use one of the school computers running Windows, in which case I'll immediately SSH into my machine with Putty 99% of the time.

Oh, I'm sure you could do it, if you could resist the temptation. I did it once. My computer broke down, the mobo was on warranty and had to go back to the factory, and the only thing I had was an old Pentium with 32 MB RAM. I ran it from the console with Slackware 11. There were limitations of course, but it ran great, it was a lot of fun, and I think I actually got more work done. I keep telling myself I should run from the console more, but I can never resist the lure of the gui.

re: believe it

I use commandline only on my server, and that's what I figured most of those "only cli" answers were about. On my desktop I use the cli for all my file and system management and nano for quick edits, but I love my kontact and konqueror. I'd hate to get by without those.

cli makes me lazy

Hehe, It's like I already have gnome-terminal open anyway so I just use vim instead of moving the mouse pointer all the way to other side of the screen and opening gedit. Big Grin Smile

More in Tux Machines

Kernel Space: Linux, Graphics

  • Linux kernel bug delivers corrupt TCP/IP data to Mesos, Kubernetes, Docker containers
    The Linux Kernel has a bug that causes containers that use veth devices for network routing (such as Docker on IPv6, Kubernetes, Google Container Engine, and Mesos) to not check TCP checksums. This results in applications incorrectly receiving corrupt data in a number of situations, such as with bad networking hardware. The bug dates back at least three years and is present in kernels as far back as we’ve tested. Our patch has been reviewed and accepted into the kernel, and is currently being backported to -stable releases back to 3.14 in different distributions (such as Suse, and Canonical). If you use containers in your setup, I recommend you apply this patch or deploy a kernel with this patch when it becomes available. Note: Docker’s default NAT networking is not affected and, in practice, Google Container Engine is likely protected from hardware errors by its virtualized network.
  • Performance problems
    Just over a year ago I implemented an optimization to the SPI core code in Linux that avoids some needless context switches to a worker thread in the main data path that most clients use. This was really nice, it was simple to do but saved a bunch of work for most drivers using SPI and made things noticeably faster. The code got merged in v4.0 and that was that, I kept on kicking a few more ideas for optimizations in this area around but that was that until the past month.
  • Compute Shader Code Begins Landing For Gallium3D
    Samuel Pitoiset began pushing his Gallium3D Mesa state tracker changes this morning for supporting compute shaders via the GL_ARB_compute_shader extension. Before getting too excited, the hardware drivers haven't yet implemented the support. It was back in December that core Mesa received its treatment for compute shader support and came with Intel's i965 driver implementing CS.
  • Libav Finally Lands VDPAU Support For Accelerated HEVC Decoding
    While FFmpeg has offered hardware-accelerated HEVC decoding using NVIDIA's VDPAU API since last summer, this support for the FFmpeg-forked libav landed just today. In June was when FFmpeg added support to its libavcodec for handling HEVC/H.265 video decoding via NVIDIA's Video Decode and Presentation API for Unix interface. Around that same time, developer Philip Langdale who had done the FFmpeg patch, also submitted the patch for Libav for decoding HEVC content through VDPAU where supported.

Unixstickers, Linux goes to Washington, Why Linux?

  • Unixstickers sent me a package!
    There's an old, popular saying, beware geeks bearing gifts. But in this case, I was pleased to see an email in my inbox, from unixstickers.com, asking me if I was interested in reviewing their products. I said ye, and a quick few days later, there was a surprise courier-delivered envelope waiting for me in the post. Coincidentally - or not - the whole thing happened close enough to the 2015 end-of-the-year holidays to classify as poetic justice. On a slightly more serious note, Unixstickers is a company shipping T-shirts, hoodies, mugs, posters, pins, and stickers to UNIX and Linux aficionados worldwide. Having been identified one and acquired on the company's PR radar, I am now doing a first-of-a-kind Dedoimedo non-technical technical review of merchandise related to our favorite software. So not sure how it's gonna work out, but let's see.
  • Linux goes to Washington: How the White House/Linux Foundation collaboration will work
    No doubt by now you've heard about the Obama Administration's newly announced Cybersecurity National Action Plan (CNAP). You can read more about it on CIO.com here and here. But what you may not know is that the White House is actively working with the Linux and open source community for CNAP. In a blog post Jim Zemlin, the executive director of the Linux Foundation said, “In the proposal, the White House announced collaboration with The Linux Foundation’s Core Infrastructure Initiative (CII) to better secure Internet 'utilities' such as open-source software, protocols and standards.”
  • Why Linux?
    Linux may inspire you to think of coders hunched over their desks (that are littered with Mountain Dew cans) while looking at lines of codes, faintly lit by the yellow glow of old CRT monitors. Maybe Linux sounds like some kind of a wild cat and you have never heard the term before. Maybe you have use it every day. It is an operating system loved by a few and misrepresented to many.

RebeccaBlackOS 2016-02-08 Review. Why? Because it’s Friday.

These are the types of problems found in an independent distro build from scratch. I cannot understand how a system built on Debian could be this buggy and apparently have zero VM support which Debian comes with by default. I can take some solace in the fact that it was built by one person and that one person is a Rebecca Black fan but as far as a Linux Distribution is concerned there is not much here. Some could say “Well its not supposed to be taken as a serious Distribution.” True except it is listed and kept up with on DistroWatch therefor it should be held as a system ready distribution especially when it was not released as a beta or an RC. If this distribution is ever going to be considered a real platform it has a long way to go. I give it about as many thumbs down as the Rebecca Black Friday video. Read more

Android More Leftovers