swestrup: (Default)
Now, it may just be that I have no idea of what commands to issue to correct these problems that I've been correcting by rebooting my Linux box, but I haven't had much success trying to google for other solutions, so any information folks might have would help.

1) I have a 1TB disk with an XFS filesystem that, until recently, had a 500GB file on it. I deleted the file to make room for more stuff, and started copying onto the drive, only to be told it was full. A quick check got me very confused as df claimed the drive was full, while du over the drive said it was half-full. I couldn't unmount the drive because it said it was 'busy'. I couldn't figure out what process (if any) was holding the drive open. Certainy none that I could figure out. I'm guessing that something had a handle on the now-missing 500GB file and it wasn't really gone until that handle was released, but I could find no way to sort that out short of rebooting.

2) I've been doing a LOT of data transfers between separate drives lately. As such it really matters to me if that transfer happens at 1.2MB/s or 35MB/s.  For some reason, the exact same setup with the exact same commands will sometimes give me one, sometimes the other. Again, I usually solve this by rebooting.  (... although I'm beginning to wonder if its because on the second try I usually mount manually, where on the first I just click on the mount icon. I wonder if the mount parameters are different enough to cause the problem...)
swestrup: (Default)
Okay, look, I understand how the introduction of info pages rather than the fixing of man was a really bad idea, and why folks would want to push back. BUT, you know, the average user needs documentation.

So, Debian, having a man page that says that there is no man page, and to use info instead, and then to automatically generate an info-page from the man page is like a WAY stupid idea!

So now there's three or four major system tools that I've discovered have no real documentation, because its all in 'info' pages which have been replaced by stub man pages...
swestrup: (Default)
I think Thunar just destroyed all of my music files. I was moving them from the backup to their new home using Thunar, since Konqueror kept crashing, and it seems to have only moved the directories, while deleting both the directories and the files from my backup drive. Tomorrow I'll see if anything is recoverable off the backup. (And I was doing a move, which is somewhat unsafe, I know, because every time Konqueror crashed I had to start over. At least with a move I could see how much I had done.)

Oh yeah, tell me how much better Linux is...
swestrup: (Default)
Here's another Linux Pet Peeve. I've been writing them down here to document them, since when I'm not actively working on a Linux system I don't remember them. Then way I say to someone "Linux still doesn't seem ready for Prime Time", they want examples. (Of course when I CAN give examples, as I've been doing, they usually respond with "Oh, that's only an issue with P on distro Q. Use distro R and you won't have that." which, naturally, ignores the hundreds of issues that distro Q has...

In any case, I expect to spend all day trying to configure MLDonkey on my box. Its the 'default' P2P file service on Debian KDE. It comes with a set of documentation that is horribly broken. Mostly that's because the package, as shipped by Debian, uses none of the configuration or setup methods documented by the package. It seems the Debian folks have decided to use some other homebrew method of setting it up and/or configuring it, none of which work, and none of which they have documented. Certainly the install wizard that came with the debian package fails spectacularly.

See, here's a real problem with the Linux community in general. They assume you'll use a command-line system to install everything since everyone is intimately familiar with every subsystem a package could touch, and how to make them play nicely. The GUI is added as an afterthought, is seldom tested, and is often horribly broken in a large number of ways. Now even this, I could live with, if the documentation that accompanied the package for the CLI install (and which is absolutely required from the command line -- you could get away without it if the GUI "just worked") was A) present and B) accurate. Often it manages to be neither which is quite a feat when you think about it.

January 2017



RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 23rd, 2017 12:22 am
Powered by Dreamwidth Studios