Shell WTF
-
-
Much lower memory requirements, 30-40% reduction in disk space usage, and hardening since most things hackers would use as attack surfaces are unavailable. You give up .NET and local PowerShell if you're on Server 2008, and locally command prompt and task manager is all you get, but you can still install almost all the server roles you'd actually use (including ASP.NET on Server 2012) as well as other services (SQL and Exchange, for example), and you don't actually give up UI control since all the stuff you do in MMC you can do from another machine, using MMC, over WMI.
-
If all you want is a chainguard on rm, you can get that with alias rm='rm -I' in your .bashrc.
As discussed in another thread a couple weeks ago, that's a crappy non-solution to the problem. In the best case, it prevents against typos. It doesn't protect against actually thinking that you want to delete something but later changing your mind, which trash cans provide some protection against. The first case is even not so convincing, because deleting stuff is common enough that you'll just start reflexively hitting 'y' anyway.The real solution is something like the
trash-cli
package, which I really wish (and think really should be) installed by default.
-
It doesn't protect against actually thinking that you want to delete something but later changing your mind
Better fix your thinking. The world is full of things you cannot really undo, and you can't be careful in one department while being prohibitively careless in another. You either think ahead of doing, or you don't.
-
How much would you pay for a trash-cli package?
-
alias rm='mv ~/.local/share/Trash'
There, now it's even integrated with your GUI.
-
Did you test it? ;-D
-
I honestly believe the whole Gnome team just went mad by this point. They have "everything's a webpage" brainworms. Hamburgers everywhere.
Actually, it looks to me more like they have "everything's a cell phone" syndrome. Same as Microsoft. As indicated by
- "everything must be big, so it can be read because the display is small"
- "everything must be on one view because the display is small"
- "lots of features are bad because the memory is small"
Essentially, these people place several devices side-by-side: A PC, a laptop, a pad, and a cellphone. Then they boldly make false assumptions:
- All users are too stupid to learn to use multiple devices.
- Therefore our software must work identically on every device.
Then they look at the devices and realize that, advanced as they are getting, cell phones are the most restrictive device. Therefore:
- All software must be designed for the cell phone.
- Who would want anything else?
It's driving me crazy.
-
Not really, no.
Oh...
Well, you get the idea, I'm too lazy to write a script that does it properly :P
-
it looks to me more like they have "everything's a cell phone" syndrome
Sorry, that is what I meant. Brainfart.
-
I suggest
alias rm='mv -it ~/.local/share/Trash'
-
alias rm='mv ~/.local/share/Trash'
alias rm='mv -it ~/.local/share/Trash'
Anything that you do in a couple line shell function is going to be a pretty crappy trash operation.The problems it has, from least to most problematic, are:
- It does not record information about where files are deleted from.
- You can't trash two files with the same name, even from different source directories. (At least PleegWat's won't overwrite those files previously-deleted.)
- Trashing files needs to do cross-volume copies.
Fortunately, the aforementioned
trash-cli
package (Debian name) provides atrash
command that isn't crappy. In addition, the readme for that package suggests not aliasing it torm
because of differences in the interface.(I should credit @ben_lubar; while I know about that package when he mentioned it last time that this discussion came up, that discussion and his post in particular got me to actually try to start using it as my usual delete-this command. With the help of
function rm() { echo "Ah ah ah, you didn't say the magic word\!" }
, it actually didn't take long to beak my habit of just hittingrm
.)
-
Better fix your thinking. The world is full of things you cannot really undo, and you can't be careful in one department while being prohibitively careless in another. You either think ahead of doing, or you don't.
Mistakes are a part of life. Don't you think that when we can make things more resistant to them, we should?
-
Right; but that's not what you're claiming. You're claiming you get a "tremendous advantage" by installing core. What advantage?
Primarily a decreases memory and disk footprint. This adds up as one virtualizes, based on a few sample configurations, you can get up to 30% more virtual machines with equivalent performance levels on a well powered host. This can result in up to a 25% savings in the number of physical machines.
There are secondary performance improvements due to the lower number of processes (and in some cases the number of threads within a process) along with a few core DLL's that end up with optimized routines (this last is the smallest by far.
-
Reminder: you're arguing with someone who breaks out in hives any time he sees a command line ;)
-
A command line is only needed if you forgot to domain join/create during setup or you need to fix broken clock or firewall settings. You can use all the GUI tools, just from another computer.
-
-
- All users are too stupid to learn to use multiple devices. - Therefore our software must work identically on every device.
These people do exist, but they are certainly not the kind of people that go and install Linux on anything, so they've fucked up royally.
And it's Linux, so you end up with a GUI made for people who are unwilling to learn, on top of an OS that requires you to shell out if you want to actually do anything.
-
-
This is the Year of the Linux Desktop (again), so they're assuming people who'd normally never touch Linux will "try it out again and see how it's improved!"
Dumb.
-
Piffle. All the discerning desktopistas will tell you this is the Year of the FreeBSD Desktop...
-
For me, this is The year of not giving a flying fuck and using whatever gets the job done.
-
For me, this is The year of not giving a flying fuck and using whatever gets the job done.
AKA every year.
-
How do you expect to get your job done if your tools are all shitty and open sores? Eh?
-
shitty and open sores?
Well that doesn't qualify as "whatever gets the job done" so problem solved.
-
Well clearly you don't care enough about your choice of tools. Pick a fucking side already!
-
I use C++.NET on Linux through Wine.
-
OK... because
mono
isn't a thing?
Badge granted: [Started a discussion @blakeyrat disapproved of](http://what.thedailywtf.com/badges/6/nice-post) -staff
-
Oh great, now we're gonna get "whoosh" posts and 47 "does that whoosh deserve a badge???" posts. Thanks Tar. Moron.
-
Why?
-
Nope, just one "weak troll, must try harder".
-
Oh great, now we're gonna get "whoosh" posts and 47 "does that whoosh deserve a badge???" posts. Thanks Tar. Moron.
And they'll all be in the section of the forum added because you kept whining
-
Nope, just one "weak troll, must try harder".
I'm sure we were talking about something but this conversation seems to have derailed...
-
...as every conversation in here seems to have done sooner or later. Isn't there a rule about that or something?
-
Started a discussion @blakeyrat disapproved of
Is not a real thing, is it?
-
Only because it would be too easy to earn.
-
Maybe we should try for the inverse:
Gee, Windows sure is awesome isn't it?! It must be the best OS evar!
-
I see three possibilities:
- TDEMSYR
- What's the point of a thread just to restate the obvious
- What's the point of posting even more flamebait aren't we flaming enough yet
-
-
-
-
-
So you're denying it?
-
Am I?
-
It's hard to tell. There are spaces in your "answer" and so it's ambiguous by the rules of my shell.
-
Hey guys, the questions thread is
-
The thing Windows does-- encrypted-by-default, graphical, remote control-- doesn't even exist in Linux regardless of what packages you have installed.
Eh? Never run X11-over-SSH before? I'd almost rather have that than VNC, as long as you aren't talking over a skinny pipe...
Every desktop-like GUI that runs on Linux implements that functionality, which is also missing from the Windows CLIs; so this is really a GUI vs CLI thing than a *nix vs everything else thing.
That said, I like being able to use the CLI chainsaw without worrying about accidentally losing a leg. That's why I do all my Linux installs on top of LVM2 and keep at least one snapshot active for each partition.
If all you want is a chainguard on rm, you can get that with
alias rm='rm -I'
in your .bashrc.
Yeah -- unfortunately, putting that particular chainguard on rm by default (i.e. having it turned on by default in rm itself, rather than in a shell alias) breaks the auto-feed functionality (i.e. using it in shell scripts); you'd have to condition it on whether stdin is a tty...
-
Eh? Never run X11-over-SSH before? I'd almost rather have that than VNC, as long as you aren't talking over a skinny pipe...
No; but you missed the point I was making entirely.
No Linux is installed with X11-over-SSH available by default. I believe, given the design of SSH, it's literally impossible. (Since you have to do that key exchange bullshit before you can connect.)
If you install a Windows VM, the remote-control GUI is right there and available from the first minute. It's all securely encrypted by default. You don't need to ever touch the CLI to make it work, it's just there and just works.
-
I believe, given the design of SSH, it's literally impossible.
SSH supports password authentication.
-
SSH supports password authentication.
...and even if it didn't, you could provide your key to the administrator of the machine who is setting up your account, like when you emailed him or opened a support ticket or whatever where you asked him to set it up.