SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I'm going to attempt building LibreOffice. Normally this would work fine because I would simply put everything on Slackware without any changes. However, this time when I installed Slackware I used LVM (but didn't put / on an LVM, it's on it's own logical partition). In addition to that, I've also put /tmp on my RAM disk by editing /etc/fstab this time:
From Googling around it appears LibreOffice is quite huge, and it's counterpart OpenOffice is just as large. Varied results say it's 9-10GB, but simply put it's not enough for my RAM (or so I believe). But I'm wondering (without editing the LibreOffice.SlackBuild) file if I should just build it somewhere else on my computer.
I would prefer not to use my hard drive for this process because it's a 64GB SSD which I recently bought and despite the fact that SSD's are better than they were in the past and will last longer now, I still would like to use my SSD to a minimum.
If it matters, my /home partition is using btrfs, while everything else is using ext4 and this is on a laptop.
If nothing works, I'm just going to buy a cheap hard disk on CraigsList or something, hook it up to my computer and build it on that but I'm looking for a faster solution.
Actually you have a faster solution: Your SSD. Buying an expensive fast drive and then not using it for tasks that will have a great benefit from that speed is somewhat pointless, I would think. Or did you spent all that money only to get a faster boot time?
But anyways, having a second larger disk can be quite handy for tasks that don't need the speed and as file storage and, if you really are that concerned about your SSD, for large compile jobs. If your mainboard supports it you may also get more RAM and compile it in RAM, RAM is really cheap right now.
Maybe you know this already, but it wasn't clear from your question: the LibreOffice Slackbuild from slackbuilds.org doesn't actually compile LibreOffice, but rather repackages the official binaries. You'll only need a few hundred MB for the whole process.
You mention the Slackbuild in the subject, which is why I thought I'd point this out. If you are actually planning to compile, just ignore me.
Well that's what I was actually talking about. My /tmp is mounted on RAM (assuming my /etc/fstab is right). However, I've heard LibreOffice goes up to 9 or 10 GB so I'm not sure if it will work if I try to compile it in RAM. I'm assuming I'll get a "no space left on disk" message.
Although my SSD can do it, I'm trying to use it less in order to extend it's life. It's the only hard drive in my computer right now, so everything I stated about my other files are all on my SSD, but compiling such a large program would use quite a few writes wouldn't it?
You could always use AlienBob's packages that were compiled for Slackware 13.37. I see no benefit in compiling such a massive program when the work has been done for you by a respected member of the Slackware community.
Well isn't one of it's disadvantages also it's write limit, or how it does them? Seeing as LibreOffice is a huge package wouldn't it have quite a few writes to do? That was my first concern with a lot of programs until I saw that they don't take up too much space so I could compile them in RAM.
If I had bought a piece of hardware, I'd hope to use it for what it is worth. If the SSD only had enough writes 2-3 years under casual desktop use, and that a frequent compilation could kill it, I'd run, away. Far away. People have also suggested that filesystem journals can kill an SSD. That is even a more extreme reason to fear the write limitations, considering that really is a typical use case for a consumer disk.
When I researched SSDs back in 2010, I found that the manufacturers reported write capabilities that would give 15-20 years worth of use before seeing 'any' problems. In that, I knew that I could just use an SSD for what it is worth, a fast, slightly more expensive disk. I run have run compilations on my SSD, and I've seen a speed increase of 3x-5x, and that is worth it on the time saved.
If I took an approach of limiting my writes, that would could maybe give me another 2-3 years over 15-20 years, I would have probably regretted the hassle, considering I would have much rather upgraded in only 5 years. Really, a 64 GB disk pushing 150 MB/s pales against a 128MB or 256MB pushing 300 MB/s, and after 5 years, the price would be attractive. Even spinning media has advanced so much, and can still be worth the replacement after 5 years. And spinning media's reliability is not really any different.
Now compiling in memory is no big deal. But now your are using a much more expensive 'disk' than even the SSD.
However, I've heard LibreOffice goes up to 9 or 10 GB so I'm not sure if it will work if I try to compile it in RAM. I'm assuming I'll get a "no space left on disk" message.
Well, I guess you've heard some wrong stuff. I have my tmpfs of 2 GB and I managed to compile successfully both LibreOffice and latest QT in it (2 GB vs 6 GB you have). On the other side, installer for the latest 3.5.0 version is only 165 Mb and rest assured - you won't see that dreadful message.
Regarding your SSD dilemmas I really don't see the point getting that kind of hardware and not using it to the max. I have one myself and I just love to abuse it. Mine has 3 years warranty and it's regularly backed up. If it dies - who cares?