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.
Not urgent, nothing broken, just a passing new-to-me mystery.
How does dolphin determine a file's mimetype? There are install scripts in "/var/lib/pkgtools/scripts" that dolphin thinks are Type: "Amiga SoundTracker audio". For example, bash-5.0.011-x86_64-1
When I tried to open it, I had to manually open Kate, then drag/drop the script into the Kate window. Dolphin's Open with: vlc, xmms, audacious (other->hunt for kate). I thought it might be the file signature, since the audio scripts begin with "if" or "69 66" but I couldn't find that signature in the usual lists.
I honestly don't understand why people use GUI file managers ( or text editors for that matter )
Command line is faster
and
Code:
file /var/lib/pkgtools/scripts/*
seems to be correct output
maybe you miss configured your GUI
I think much of it is what people get used to but a flat, broad statement that CLI is always faster is simply mistaken when the global workflow process is considered and a few other deep level applications. There are times for example when a project requires viewing and editing a couple or several files in /etc as one example. Having a File Manger up makes for fast access, viewing and editing with fewer strokes including both key and mouse strokes. I approach such work with "kdesu dolphin" and avoid complication and gain quick access to multiple choices and can see the flow of it all in front of me. For a single operation I almost always just use CLI except for deep level operations like partition management where seeing all drives and every partition on them reassures me I am not making errors, less evident from CLI especially with udev mounted volumes that can change designation numbers.
I love CLI and all my systems boot to multi-user CLI excepting a few test distros that make that a royal pita. I still force them into allowing root login to X so I can alter the appearance of root enabled apps so there can be no mistakes or misgivings and I dislike sudo and enable a fully working root account instead on every distro I've ever tried or used for any length of time.
It seems to me CLI and GUI are tools and it is best to use the tools that hold the most advantages for the user and the least disadvantages. There is some value to vision or we wouldn't have the fairly obvious cliche that "a picture is worth 1000 words".. or "one man's meat is another man's poison".
I think much of it is what people get used to but a flat, broad statement that CLI is always faster is simply mistaken when the global workflow process is considered and a few other deep level applications. There are times for example when a project requires viewing and editing a couple or several files in /etc as one example. Having a File Manger up makes for fast access, viewing and editing with fewer strokes including both key and mouse strokes. I approach such work with "kdesu dolphin" and avoid complication and gain quick access to multiple choices and can see the flow of it all in front of me. For a single operation I almost always just use CLI except for deep level operations like partition management where seeing all drives and every partition on them reassures me I am not making errors, less evident from CLI especially with udev mounted volumes that can change designation numbers.
I love CLI and all my systems boot to multi-user CLI excepting a few test distros that make that a royal pita. I still force them into allowing root login to X so I can alter the appearance of root enabled apps so there can be no mistakes or misgivings and I dislike sudo and enable a fully working root account instead on every distro I've ever tried or used for any length of time.
It seems to me CLI and GUI are tools and it is best to use the tools that hold the most advantages for the user and the least disadvantages. There is some value to vision or we wouldn't have the fairly obvious cliche that "a picture is worth 1000 words".. or "one man's meat is another man's poison".
I honestly don't understand why people use GUI file managers ( or text editors for that matter )
Command line is faster
Sure CLI is faster for navigating and moving files through the directory structure but GUIs have their place too. E.g. I have lots of photos I take stored on my computer. I'd rather look through them in a GUI file manager with thumbnails to find the one I want than look at lists of hundreds of IMG_1341.JPG etc in the CLI and guess what's in the picture. No need to be condescending about it
Sure CLI is faster for navigating and moving files through the directory structure but GUIs have their place too. E.g. I have lots of photos I take stored on my computer. I'd rather look through them in a GUI file manager with thumbnails to find the one I want than look at lists of hundreds of IMG_1341.JPG etc in the CLI and guess what's in the picture. No need to be condescending about it
Oh Come on Firerat. I thought you were tongue-in-cheek kidding but apparently not. So, please try to name even one profession in which a single tool is best for all jobs and all workers. There is a valid reason for toolboxes, no? OK so some Harley mechanics joke that the only Harley toolbox essentials are baling wire and vise grips, but even that joke has two tools.
Additionally why are you posting incompatible "guidance" in the Slackware sub forum as a Debian user who relies on automated package management and systemd with a disabled root account? Whatever twirls ur beanie, cousin, but your suggestion of "file /var/lib/pkgtools/scripts/*" fails here as Slackware does not have a pkgtools directory in /var/lib or in /var anywhere. The concept isn't bad but it does paint you as something of a guy with an axe to grind and a pose to support. Please, if you wish to comment in a Slackware sub-forum know some Slackware.
Oh Come on Firerat. I thought you were tongue-in-cheek kidding but apparently not. So, please try to name even one profession in which a single tool is best for all jobs and all workers. There is a valid reason for toolboxes, no? OK so some Harley mechanics joke that the only Harley tool box essentials are baling wire and vise grips, but even that joke has two tools.
Sure. Lets spend countless hours taking time to name each of the thousands of photos with a specific name so I can enjoy using the CLI on something that's inherently graphical in nature. Please stop being so condescending, its getting ridiculous.
ORLY? If you do a web search for "tools of philosophy" you will discover they include grammar, speech, imagination, mathematics and logic just to name a few. You are reaching and it exceeds your grasp.
ORLY? If you do a web search for "tools of philosophy" you will discover they include grammar, speech, imagination, mathematics and logic just to name a few. You are reaching and it exceeds your grasp.
Do not post any messages that are obscene, vulgar, sexually-orientated, hateful, threatening, hostile or insulting.
Personal attacks on others will not be tolerated.
Flame Wars will not be tolerated.
Do not post if you do not have anything constructive to say in the post.
Additionally why are you posting incompatible "guidance" in the Slackware sub forum as a Debian user who relies on automated package management and systemd with a disabled root account? Whatever twirls ur beanie, cousin, but your suggestion of "file /var/lib/pkgtools/scripts/*" fails here as Slackware does not have a pkgtools directory in /var/lib or in /var anywhere. The concept isn't bad but it does paint you as something of a guy with an axe to grind and a pose to support. Please, if you wish to comment in a Slackware sub-forum know some Slackware.
you may want to recheck that
are you on current?
because here on lackware64-current they do exist.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.