-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
The "Linux questions (and other stuff)" thread
- Thread starter MoodyBlues
- Start date
Ha ha, no, Mom was stuck in her hospital bed in her room by then. Good theory, though!Were you in a Delorean when you took those videos?
Good theory, but it's not a file manager, it's a photo app.
What about other photo apps, are they reading the same “1947" metadata?
I'll have to install some to see. I've been on an austerity program when it comes to apps on my new phone. I'm trying to avoid ending up with dozens of apps I never use...and sometimes don't even recall what they're for! Just trying to keep the new phone clean.
So I went to the Play store to find some photo apps; I tried one called "Gallery" (from SB Studio) that was so ad-laden I couldn't delete it fast enough! (Why do they think making an ad-riddled free version--which gives the user a terrible experience--will entice people to upgrade to the paid version? This may have been an awesome app, but I'll never know!)
Then, thinking of my computers, I searched for "digiKam"--and ended up at "F-Stop Gallery." A few minutes of using the free version (no ads!, just not full-featured) convinced me to buy the paid version, F-Stop Gallery Pro--and I've lost myself in it! It's a really good app.
Oh--it doesn't replicate the 1947 date; I think it was just "Amazon Photos" that did that.
Then, thinking of my computers, I searched for "digiKam"--and ended up at "F-Stop Gallery." A few minutes of using the free version (no ads!, just not full-featured) convinced me to buy the paid version, F-Stop Gallery Pro--and I've lost myself in it! It's a really good app.
Oh--it doesn't replicate the 1947 date; I think it was just "Amazon Photos" that did that.
GameTheory
Android Expert
So this was on my google feed today...
https://github.com/dylanaraps/fff
https://www.tecmint.com/fff-fast-file-manager-for-linux/
I also stumbled upon this one which seems just as good if not better...
https://github.com/jarun/nnn
https://itsfoss.com/nnn-file-browser-linux/
Very interesting. They're written in bash. Has anyone tried any of these file managers?
https://github.com/dylanaraps/fff
https://www.tecmint.com/fff-fast-file-manager-for-linux/
I also stumbled upon this one which seems just as good if not better...
https://github.com/jarun/nnn
https://itsfoss.com/nnn-file-browser-linux/
Very interesting. They're written in bash. Has anyone tried any of these file managers?
They look interesting; I hadn't heard of either, so, no, I haven't tried them yet.
I like the full name of the fff one!
Although Dolphin is my default file manager, I do anything 'root' at a command line, so I probably can't help, but what issues are you having?
Oh, I see. Doesn't Nautilus have that built in? I don't like Nautilus, but maybe in a pinch...?
GameTheory
Android Expert
From what I've seen over the years in the linux community is that you shouldn't use "sudo" to open any GUIs. Instead suppose to use "gksudo or gksu", which have been deprecated and now should be using "pkexec". Of course sudo is still used for anything non-gui.
https://askubuntu.com/a/270019
sudo apt install pkexec
pkexec nautilus
I'm old school! Using a fancy-schmancy, pretty GUI for root work just doesn't feel right somehow. Seeing that beautiful # prompt at a command line makes me feel like I'm home. 
GameTheory
Android Expert
I'm old school! Using a fancy-schmancy, pretty GUI for root work just doesn't feel right somehow. Seeing that beautiful # prompt at a command line makes me feel like I'm home.
Well I'm with you on that, but we need them purdy GUIs
if we are to de-throne windows from the consumer desktop dominance. Linux needs to appeal to them windows users that are afraid of it.
Oh, I'm all for them purdy GUIs--just look at my copious writing about my beloved, beautiful KDE.Well I'm with you on that, but we need them purdy GUIs
No, I just mean for any work as root, you'll find me at a command line.
Speaking of window$ users: does their UI still look ugly and childish? Seriously, when I see screenshots from window$ boxes, it hits me how ugly its icons and toolbars and...everything look so amateurish compared to KDE. Can they customize everything, like with KDE? Or are they still basically stuck with whatever Redmond gives them?
GameTheory
Android Expert
Speaking of window$ users: does their UI still look ugly and childish? Seriously, when I see screenshots from window$ boxes, it hits me how ugly its icons and toolbars and...everything look so amateurish compared to KDE. Can they customize everything, like with KDE? Or are they still basically stuck with whatever Redmond gives them?
Not sure on the looks. I hear they finally got a dark theme which we've had forever.
I don't think they can customize much outside of their god mode if that's still a thing. Since theirs is called god mode and doesn't do much, then what would ours be called that does everything you can think of? Mind Blown! 
Dngrsone
Android Expert
Microsoft absolutely hates "Power Users"; that is, anyone who likes to rummage around under the hood, and have been making things more and more difficult for us since Vista.
They have said as much in writing, even. Their customer base is corporate, and the millions of home users of all grades are secondary, if that, so they really don't care about their wants and needs unless or until a corporate concern makes a request. Then, likely, it will only be something available at a price.
They have said as much in writing, even. Their customer base is corporate, and the millions of home users of all grades are secondary, if that, so they really don't care about their wants and needs unless or until a corporate concern makes a request. Then, likely, it will only be something available at a price.
None of this surprises me.
The elegance and gracefulness of KDE, along with its infinite customization possibilities, should be shown to every window$ user. If they only knew how beautiful--and stable and secure!--their PCs could be, maybe they'd switch.
Okay, guys, here's a head-scratcher. And it's a totally LOW priority problem.
I use KSnapshot for taking screenshots. I've always loved its auto-incrementing way of suggesting names for files as you're saving them. Say that I'd taken a screenshot and saved it as SeaMonkey_112204_1.jpeg (where 112204 is a date), then I took another screenshot and went to "save as," it would show SeaMonkey_112204_2.jpeg. Very handy when you're taking/saving a bunch of related screenshots.
If I'd named the initial file SeaMonkey_112204.jpeg, the auto-incremented one would be SeaMonkey_112205.jpeg. Not what I'd want, so I just don't ever put the date at the end.
A file name ending in an alpha character, like SeaMonkey.jpeg, would get auto-incremented to SeaMonkey1.jpeg.
Just recently, it's doing something new.
A file I'd named Ancestry_JohnDoe_1930census.jpeg had its suggested next file named Ancestry_JohnDoe_1931census.jpeg, instead of the expected Ancestry_JohnDoe_1930census1.jpeg.
As always, I'm running old versions of everything, including Kubuntu and KSnapshot, and do not allow any automatic updates--so nothing could've changed. And it's been eons since I even looked at KSnapshot's settings, so no changes there either.
I use KSnapshot for taking screenshots. I've always loved its auto-incrementing way of suggesting names for files as you're saving them. Say that I'd taken a screenshot and saved it as SeaMonkey_112204_1.jpeg (where 112204 is a date), then I took another screenshot and went to "save as," it would show SeaMonkey_112204_2.jpeg. Very handy when you're taking/saving a bunch of related screenshots.
If I'd named the initial file SeaMonkey_112204.jpeg, the auto-incremented one would be SeaMonkey_112205.jpeg. Not what I'd want, so I just don't ever put the date at the end.
A file name ending in an alpha character, like SeaMonkey.jpeg, would get auto-incremented to SeaMonkey1.jpeg.
Just recently, it's doing something new.
A file I'd named Ancestry_JohnDoe_1930census.jpeg had its suggested next file named Ancestry_JohnDoe_1931census.jpeg, instead of the expected Ancestry_JohnDoe_1930census1.jpeg.
As always, I'm running old versions of everything, including Kubuntu and KSnapshot, and do not allow any automatic updates--so nothing could've changed. And it's been eons since I even looked at KSnapshot's settings, so no changes there either.
Dngrsone
Android Expert
Possibly because I hate myself, I am once again messing around with my laptop...
History
My Toshiba P55t-B5154 has a 2TB drive on it. Of course, initially it was a pure Win 10 machine, but I quickly disabused it of that notion: I shrunk the drive as far as I could from within Win (Fun fact, WIndows will only shrink your hard drive down by half the drive size. This means my Windows main Partition went down to just under 1 TB)
I then used a Mint (at the time 17.1) Live disc, and repartitioned the drive using KParted. I squeezed that Windows partition down to a paltry 250GB, created a 500GB NTFS partition for all my common data (think photos, music, etc), made a swap drive at the very end of the drive and then a bunch of 100GB partitions as I needed them.
For each Linux OS, I would create two 100GB partitions: the primary (root) partition, and a /home partition.
I installed rEFInd for my bootloader and set it as the primary bootloader, so none of my subsequent installs will mess things up (much)
That initial Mint 17.1 KDE was upgraded at some point to 17.3, and as I added more OSes, it ended up getting plowed under in favor of something else.
Current installations
As of this moment, I have the following:
Win 10 (250GB)
/Data (500GB)
Neon 5.15 (100GB root + 100GB /home)
Mint 18.1 KDE (100GB root + 100GB /home)
Mint 18 xfce (100GB root + 100GB /home)
Mint 18.3 KDE (100GB root + 100GB /home)
Kaos (108GB)
Okay, so I had an extra partition, and I thought Kaos, being a minimal KDE install could go in there for giggles. It is painfully white at the moment, which makes it doubly painful in this dark bedroom, hah.
Newly generated problems
With the exception of Kaos, the rest of my Linux installs are *buntu derivatives, and play fairly nicely with rEFInd.
Kaos, though... it uses a systemd (formerly gummi?) bootloader and it has muddied things up. SOmewhere along the way, I ended up filling the entire 100MB /boot partition, so I had make some room by deleting what I thought were unnecessary files (18 old versions of vmlinuz, for instance), but rEFINd didn't seem to be seeing Kaos at all. I could only get to it via Neon's GRUB (which I luckily haven't deleted yet).
I finally figured out which of the extra generic logins belonged to Kaos, but somewhere I broke it-- booting into the systemd.efi file results in a hung computer which requires me to force-shutdown to recover from.
I wanted to clean up the /boot folder and fix things up a little, because it takes forever for rEFInd to scan a 2TB drive for bootloaders. Ideally, I again teach myself to write actual entries for each OS and turn off the search function, but that's pretty close to work at this point in time.
Not to mention I have recently got it in my head that I want to drop an SSD in this thing, and a friend convinced me that I should remove my optical drive and put a second HDD in its place.
Therefore, the near-term goal (as in, maybe this year) would be to invest in a 1TB SSD to put all the OSes in, and pointing the important /home folders to the second drive, probably the original 2TB spinny, and the optical in a separate enclosure (SATA to USB 3.0) for those times when I want to watch a movie or something.
If I do that, then I will definitely need to know what I am doing for rEFInd and get things settled in for the longer term.
TL;DR
I'm bitching because i started rummaging around in the /boot partition and shit is ugly with a big UH!
...and it's 2335, and way too late for me to be thinking clearly, anyway.
History
My Toshiba P55t-B5154 has a 2TB drive on it. Of course, initially it was a pure Win 10 machine, but I quickly disabused it of that notion: I shrunk the drive as far as I could from within Win (Fun fact, WIndows will only shrink your hard drive down by half the drive size. This means my Windows main Partition went down to just under 1 TB)
I then used a Mint (at the time 17.1) Live disc, and repartitioned the drive using KParted. I squeezed that Windows partition down to a paltry 250GB, created a 500GB NTFS partition for all my common data (think photos, music, etc), made a swap drive at the very end of the drive and then a bunch of 100GB partitions as I needed them.
For each Linux OS, I would create two 100GB partitions: the primary (root) partition, and a /home partition.
I installed rEFInd for my bootloader and set it as the primary bootloader, so none of my subsequent installs will mess things up (much)
That initial Mint 17.1 KDE was upgraded at some point to 17.3, and as I added more OSes, it ended up getting plowed under in favor of something else.
Current installations
As of this moment, I have the following:
Win 10 (250GB)
/Data (500GB)
Neon 5.15 (100GB root + 100GB /home)
Mint 18.1 KDE (100GB root + 100GB /home)
Mint 18 xfce (100GB root + 100GB /home)
Mint 18.3 KDE (100GB root + 100GB /home)
Kaos (108GB)
Okay, so I had an extra partition, and I thought Kaos, being a minimal KDE install could go in there for giggles. It is painfully white at the moment, which makes it doubly painful in this dark bedroom, hah.
Newly generated problems
With the exception of Kaos, the rest of my Linux installs are *buntu derivatives, and play fairly nicely with rEFInd.
Kaos, though... it uses a systemd (formerly gummi?) bootloader and it has muddied things up. SOmewhere along the way, I ended up filling the entire 100MB /boot partition, so I had make some room by deleting what I thought were unnecessary files (18 old versions of vmlinuz, for instance), but rEFINd didn't seem to be seeing Kaos at all. I could only get to it via Neon's GRUB (which I luckily haven't deleted yet).
I finally figured out which of the extra generic logins belonged to Kaos, but somewhere I broke it-- booting into the systemd.efi file results in a hung computer which requires me to force-shutdown to recover from.
I wanted to clean up the /boot folder and fix things up a little, because it takes forever for rEFInd to scan a 2TB drive for bootloaders. Ideally, I again teach myself to write actual entries for each OS and turn off the search function, but that's pretty close to work at this point in time.
Not to mention I have recently got it in my head that I want to drop an SSD in this thing, and a friend convinced me that I should remove my optical drive and put a second HDD in its place.
Therefore, the near-term goal (as in, maybe this year) would be to invest in a 1TB SSD to put all the OSes in, and pointing the important /home folders to the second drive, probably the original 2TB spinny, and the optical in a separate enclosure (SATA to USB 3.0) for those times when I want to watch a movie or something.
If I do that, then I will definitely need to know what I am doing for rEFInd and get things settled in for the longer term.
TL;DR
I'm bitching because i started rummaging around in the /boot partition and shit is ugly with a big UH!
...and it's 2335, and way too late for me to be thinking clearly, anyway.
In my humble opinion, and experience, you're allocating a lot more space to your / partitions than you'll ever need. Personally, I wouldn't make it more than 50GB, and even that is ridiculously huge.