Live data from Hacker News

I'm “still afraid to use spaces in file names” years old

twitter.com

781–790 of 817 posts

Re: I'm “still afraid to use spaces in file names” years old

#781
post #235

Earlier quoted context omitted.

work/client/project/2021-11-11-file.ext is great until you've got a '2021-11-11-project-status.txt' in a few directories and you need to find one quickly! I do a combination: clients/client/project/2021-11-11-client-project-update.txt

It sounds like what everyone in this thread needs is a database file system. This was always my favorite proposed feature of Windows Longhorn that never made the cut. Almost 2 decades later and Microsoft's latest OS still doesn't have this feature.

Have you used BeOS?

Re: I'm “still afraid to use spaces in file names” years old

#782

Earlier quoted context omitted.

It sounds like what everyone in this thread needs is a database file system. This was always my favorite proposed feature of Windows Longhorn that never made the cut. Almost 2 decades later and Microsoft's latest OS still doesn't have this feature.

Have you used BeOS?

For sure! I actually used Be before I ever used Linux.

Re: I'm “still afraid to use spaces in file names” years old

#783
post #686

Earlier quoted context omitted.

> Docker relies on LXC, so it's Linux-only. Docker hasn't supported LXC since 2016, and stopped relying on it in 2014 https://www.docker.com/blog/docker-0-9-introducing-execution...

I thought the name for the collection of kernel features was LXC, I didn't realize (until just now) that was the name only for the also-kernel-level wrapper for those features, which name does not cover the features themselves. That is, I didn't realize that LXC is to Cgroups+Namespaces as Libvirt is to KVM—I thought LXC, as a label, covered the whole feature-set—but regardless, it's still married to Linux kernel fea…

> it's still married to Linux kernel features and runs on other platforms under virtualization, no?

Actually no. At least on Windows Docker can do native Windows containers too

https://poweruser.blog/lightweight-windows-containers-using-...

Re: I'm “still afraid to use spaces in file names” years old

#785

Earlier quoted context omitted.

All of that was very cool and impressive and extremely user-friendly. However, I found the lack of a command-line to be restricting.

On the other hand Mac had some great GUI programs. Sometimes i think that the command-line is a crutch that keeps programmers from learning how to make good UIs.

True, but most Mac apps were virtually inaccessible by keyboard, and with the slow cursor rate made them a nightmare for the wrist.

Re: I'm “still afraid to use spaces in file names” years old

#786

Earlier quoted context omitted.

alias mouseoff='xinput set-prop 11 "Device Enabled" 0' alias mouseon='xinput set-prop 11 "Device Enabled" 1' Kind of ridiculous if you ask me.

It is, but they actually have a shortcut for that (--disable, --enable).

Direct quote from my console:

    $ xinput --disable
    Segmentation fault (core dumped)

Re: I'm “still afraid to use spaces in file names” years old

#787
post #631
post #480

Earlier quoted context omitted.

It’s not just you: Every distro is its own special snowflake and patches the programs they distribute to store files in a different place. The “standard” doesn’t tell you what directory structure to use inside /etc to group related config files. The “standard” doesn’t tell you where an HTTP server should serve its files. Everyone just does their own thing which makes upstream docs incorrect and useless for newcomers.

> The “standard” doesn’t tell you what directory structure to use inside /etc to group related config files. The “standard” doesn’t tell you where an HTTP server should serve its files. Everyone just does their own thing which makes upstream docs incorrect and useless for newcomers. The FHS, does actually answer both of of those questions. Files inside /etc/ should be grouped in subdirectories[0] andd the HTTP server…

> HTTP server should serve user-specified website files from /srv

I’ve never seen that in my life, but I’m sure someone does that. This is one of those cases where the people who follow the standard are increasing fragmentation

Re: I'm “still afraid to use spaces in file names” years old

#790
post #569
post #453

Earlier quoted context omitted.

Oh, my young friend, you have no idea what POSIX has done to you. "While no one sane would put newlines in directory names, such corruption of the results could lead to exploitable vulnerabilities in scripts." http://www.etalabs.net/sh_tricks.html

He he. Want to see true craziness? POSIX file names are just a bag of bytes. They don't even have to be text, they can be anything (almost), there's no standard text encoding: https://lwn.net/Articles/325304/ And in typical Open Source fashion, someone actually claims it's a feature: https://lwn.net/Articles/325398/ because hey, you 99.999% percenters can suffer so that I, 0.001% percenter can implement my wacky syst…

It's basically the same on Windows with NTFS. Just a bag of 16-bit words instead of bytes.
Post reply on HN