SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is a small thing: There's a bit of magic for filenames with spaces where a filename like 'Program Files' gets the space escaped, so it becomes 'Program\ Files.' All good so far, and very handy with wine.
But 'Program Files (x86)' becomes 'Program\ Files\ (x86) and the brackets have to be escaped manually to 'Program\ Files\ \(x86\).' Surely that can be achieved?
Last edited by business_kid; 03-11-2024 at 12:32 PM.
This is a small thing: There's a bit of magic for filenames with spaces where a filename like 'Program Files' gets the space escaped, so it becomes 'Program\ Files.' All good so far, and very handy with wine.
But 'Program Files (x86)' becomes 'Program\ Files\ (x86) and the brackets have to be escaped manually to 'Program\ Files\ \(x86\).' Surely that can be achieved?
Windows is unused. That said, I had to take it to get the PC at that price, so I'm not deleting it. People I know freeze at the sight of something unfamiliar. They might need it.
I do have to use one Library program, and do that in wine. The full path is: ~/.wine/drive_c/Program\ Files\ \(x86\)/blah/blah.
That, of course, is a link to another filename in windoze speak. So I only have to use the Unix version when the shortcut doesn't work. When you look at it, trouble isn't hard to imagine. I sometimes have replaced all that with the Unix version.
But there's torrents also which are ok in the EU. They will close down internet sites that host torrents here on the basis of foreign court orders (I think), but nobody can go after end users. So as long as I don't host a site, I'm fine. The filenames of torrents are mainly windows based, with all sorts of nonsense in them.
Yes, we previously used the "correct" UID for nobody and GID for nogroup (65534), but when our good friends at Red Hat standardized on 99:99, we followed because things were starting to hardcode 99 and causing issues for systems that used 65534:65534. I see that they've put up a page explaining why they later changed to 65534, and once I get a Red Hat subscription I'll be able to read the "subscriber exclusive content" and see why.
It does get a little tiresome to keep covering the same ground. One can only quote Henry Spencer so many times.
Perhaps it would help to add as alternate nobody:nogroup something like:
Life was simpler before systemd began a deep rooted infestation where even desktop environments have become dependent. Maybe start a subreddit Volkerding was Right.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
