Similarly, I always leave some space unallocated on LMV volume groups. It means that I can temporarily expand a volume easily if needed.
It also serves to leave some space unused to help out the wear-levelling on the SSDs on which the RAID array that is the PV¹ for LVM. I'm, not 100% sure this is needed any more² but I've not looked into that sufficiently so until I do I'll keep the habit.
--------
[1] if there are multiple PVs, from different drives/arrays, in the VG, then you might need to manually skip a bit on each one because LVM will naturally fill one before using the next. Just allocate a small LV specially on each and don't use it. You can remove one/all of them and add the extents to the fill LV if/when needed. Giving it a useful name also reminds you why that bit of space is carved out.
I do that + script to auto resize within sane limits. So for most servers the partitions will automatically fit the usage while still leaving some spare space.
Usually something like "expand if there is less than 5% left, with monitoring triggering when there is 4% free space left", so there is still warning when the automatic resize is on limit
carving space per PV like that is pointless
> It also serves to leave some space unused to help out the wear-levelling on the SSDs on which the RAID array that is the PV¹ for LVM. I'm, not 100% sure this is needed any more² but I've not looked into that sufficiently so until I do I'll keep the habit.
YMMV but most distros set up a cron/timer that does fstrim monthly. So it shouldn't be needed, as any free space will be returned to SSD.
> [1] if there are multiple PVs, from different drives/arrays, in the VG, then you might need to manually skip a bit on each one because LVM will naturally fill one before using the next. Just allocate a small LV specially on each and don't use it. You can remove one/all of them and add the extents to the fill LV if/when needed. Giving it a useful name also reminds you why that bit of space is carved out.
other options is telling LVM this LV is striped (so it uses space from both drives equally), or manually allocating from drive with more free space when expanding/adding LV
Not needed. All your unused/unfilled space is that space for wear-leveling. It wasn't needed even back then besides some corner cases. And most importantly 10% of the drive in ~2010 were 6-12GB, nowadays it's 50-100GB at least.
But even ignoring the wear-levelling issue, the spare space still fulfils a need in providing the ballast space which is the main thing we are talking about here. Of course there are other ways to manage that issue¹ but a bit of spare space in the volume group is the one I go for.
In fact since enlarging live ext* filesystems has been very reliable² for quite some time and is quick, I tend to leave a lot of space initially and grow volumes as needed. There used to be a potential problem with that in fragmenting filesystems over the breadth of a traditional drive's head seek meaning slower performance, but the amount of difference is barely detectable in almost all cases³ and with solid state drives this is even more a non-issue.
> And most importantly 10% […] nowadays it's 50-100GB at least.
It doesn't have to be 10%. And the space isn't lost: it can be quickly brought into service when needed, that is the point, and if there is more than one volume in the group then I'm not allocating space separately to every filesystem as would be needed with the files approach. It is all relative. My /home at home isn't nearly 50GB in total⁴, nor is / anywhere I'm responsible for even if /var/log and friends are kept in the same filesystem, but if I'm close to as little as 50GB free on a volume hosting media files then I consider it very full, and I either need to cull some content or think about enlarging the volume, or the whole array if there isn't much slack space available, very soon.
--------
[1] The root-only-reserved blocks on ext* filesystems, though that doesn't help if a root process has overrun, or files as already mentioned above.
[2] Reducing them is still a process I'd handle with care, it can be resource intensive, has to move a lot more around so there is more that could go wrong, and I've just not done it enough to be as comfortable with the process as I am with enlarging.
[3] You'd have to work hard to spread things far and randomly enough to make a significant difference.
[4] though it might be if I wasn't storing 3d print files on the media array instead of in /home
Empty space is good for wear-leveling but enforcing a few percent extra helps.
> And most importantly 10% of the drive in ~2010 were 6-12GB, nowadays it's 50-100GB at least.
Back then you were paying about $2 per gigabyte. Right now SSDs are 1/15th as expensive. If we use the prices from last year they're 1/30th, and if we also factor in inflation it's around 1/50th.
So while I would say to use a lower percentage as space increases, 50-100GB is no problem at all.
Only if you fill the drive up to 95-99% and do this often. Otherwise it's just a cargo-cult.
> So while I would say to use a lower percentage as space increases
If your drive is over-provisioned (eg 960GB instead of 1024GB) then it's not needed. If not and you fill your drive to the full and just want to be sure then you need the size of the biggest write you would do plus some leeway, eg if you often write 20GB video files for whatever reason then 30-40GB would be more than enough. Leaving 100GB of 1TB drive is like buying a sneakers but not wearing them because they would wear.
> If your drive is over-provisioned (eg 960GB instead of 1024GB) then it's not needed.
I disagree. That much space isn't a ton when it comes to absorbing the wear of background writes. And normal use ends up with garbage sectors sprinkled around inflating your data size, which makes write amplification get really bad as you approach 100% utilization and have to GC more and more. 6% extra is in the range where more will meaningfully help.
> Leaving 100GB of 1TB drive is like buying a sneakers but not wearing them because they would wear.
50GB is like $4 of space the last time most people bought an SSD. Babying the drive with $4 is very far from refusing to use it at all. The same for 100GB on a 4TB drive.
Nah, we used some consumer SSD for write heavy but not all that precious data, and time to live was basically directly dependant on the space left free on device.
Of course, doesn't matter for desktop use as the spare on drive is enough, but still, if you have 24/7 write heavy loads, making sure it's all trimmed will noticably extend lifetime
Yep. That is why doing both can be beneficial. Alerts are more proactive if acted upon, but often too easy to ignore meaning ballast is more fail-safe in that respect.
I didn't read Idiocracy as eugenics/anti-eugenics. It wasn't saying that stupid people breeding made the population stupid, it was saying that the less educated breeding resulted in the more educated being pushed to the periphery and eventually fading out.
The people of the film's future were not stupid, just massively uninformed and misinformed. They were able to grasp the problem and solution in the end.
Unless I'm misremembering, and it did make direct reference to intelligence rather than education and access to it. It is a good few years since I last watched it. There is the title, of course, but educationally-disasavantaged-ocracy would not have been catchy enough!
> Unless I'm misremembering, and it did make direct reference to intelligence rather than education and access to it.
You are misremembering; they had a scene of an intelligence test that had adults matching shapes (stars -. tars, squares -> squares) and getting it wrong.
I'm afraid you are misremembering. The movie is explicitly eugenicist. The people of the future are explicitly biologically stupid. The opening transcript is unambiguous:
[Man Narrating] As the 21st century began… human evolution was at a turning point.
Natural selection, the process by which the strongest, the smartest… the fastest reproduced in greater numbers than the rest… a process which had once favored the noblest traits of man… now began to favor different traits.
[Reporter] The Joey Buttafuoco case-
Most science fiction of the day predicted a future that was more civilized… and more intelligent.
But as time went on, things seemed to be heading in the opposite direction.
A dumbing down.
How did this happen?
Evolution does not necessarily reward intelligence.
With no natural predators to thin the herd… it began to simply reward those who reproduced the most… and left the intelligent to become an endangered species.
What is "explicitly eugenicist" in observing that the unprecedented way mankind has dominated its environment has changed the selection pressures we are subject to?
My quest to survive to adulthood and pass on my genes looked nothing like the gauntlet an Homo erectus specimen would have run.
Yep. The studio didn't know what the hell to do with it.
I'm guessing that we (those of us who have seen it despite the lack of promotion) are lucky that they didn't just can it completely, or demand it get cut to ribbons and reformed as something else.
I think director's in that era can avoid this by not doing extra takes for scenes that would never make it anyways. Mike Judge did not have the budget for that anyways.
Nowadays they just change the scenes in post anyways, leading to some of the worst and most atrocious continuity errors.
Yes, but platforms need to make a case for why we should feel inclined to make the effort.
Is the ROI from the potential audience going to be worth it?
Or does it help some people enough that I might want to do it despite no real ROI (i.e. I make the effort to make things not compatible with common assistive tech, even where there is little or no end benefit for me so it is sunk time in that respect, does this new platform quality for my time & attention enough in that way?).
Or is it simply cool enough for me to be interested in playing with it myself?
If none of the above, is there any other reason we should care?
This is especially true if building for the platform means building something new, not just making tweaks to ensure your existing output is compatible.
> First, referencing "Nazi" has an age old tradition of immediately meaning you lose the debate.
True. Though to be frank, before typing my longer response I did consider just telling you the same about the “but forget everything else and think of the children” line of reasoning.
> To paint every job which requires a clearance as morally bankrupt, to paint working for the government to be morally bankrupt, is frankly disgusting.
Sometimes you don't know the exact nature of the task until after you've gone through the rigmarole of applying, getting clearance, etc. In that case if you consider some of the jobs to be morally bankrupt, you consider all of them to potentially be morally bankrupt. You could go through all the hassle then turn it down, or leave during a probationary period when you discover the details, but that is a significant wasted time risk to take.
> You should literally be ashamed of yourself.
Many people state-side are ashamed of their government, and don't want to feel their reputation is tarnished by working directly for it, and quite frankly I don't blame them right now nor would I have at all at numerous points over recent years. And that is before considering those who want “conscientious objector” status with regard to anything military related.
> If you make working for the government a badge of shame, it will become true in time?
For some, it has become true. That time is now or before.
As much as “join and fight the corruption from within” is a laudable goal, I entirely understand people not thinking that they've got the nerve for that. Especially given that the first thing a bad administration does to someone raising concerns is to sack and blacklist them in a way that will affect future employment opportunities.
> such as helping to feed poor children
The “but think of the children” argument cuts both ways: many governments have, directly or indirectly, done and continue to do, terrible things to children. It may not be possible in the short/medium term to do anything truly useful about that (you go try tell the current administration over there to refund the good works that have been gutted recently and see how seriously they take you!) and dealing with the crap until things stear back towards the good is too much for some.
Not everyone has the fortunate needed to fight a bad system from within, or the desire to, no matter how many heartstrings you pull to try shame them into reconsidering the good within the bad.
> To paint every job which requires a clearance as morally bankrupt, to paint working for the government to be morally bankrupt, is frankly disgusting.
Sometimes you don't know the exact nature of the task until after you've gone through the rigmarole of applying, getting clearance, etc.
I literally said "every job". You're saying "sometimes" they might be. What is your point? It certainly doesn't counter or answer the point I raise.
> You should literally be ashamed of yourself.
Many people state-side are ashamed of their government, and don't want to feel their reputation is tarnished by working directly for it, and quite frankly I don't blame them
Well I do blame them. And I specifically excluded the military. As I mentioned, the government is a vast and immense entity. Further, my response was to someone saying that to get a clearance would be morally bankrupt. I provided examples as to why that may not be the case. What you are doing, is painting all government as bad, because a specific team is in play right now.
This is literally what is wrong with the US currently. 90% of the issues are due to team politics on both sides. Politics before people. Politics before sensibility. Politics, instead of examining the moral and ethical considerations of each action one takes.
> If you make working for the government a badge of shame, it will become true in time?
As much as “join and fight the corruption from within” is a laudable goal,
You do not have to fight corruption to take a job feeding babies. Or the large amount of good that the government does. You can simply take and do that job. That's my point here. You're doing what the poster upstream did, painting the entire body of the US government as a single entity.
It's OK to say "I don't think this part of government is ethical, I won't work for that part of government", but to say that any government job is morally repugnant is disgusting.
> such as helping to feed poor children
The “but think of the children” argument
It's not a "think of the children" argument in any traditionally way. That argument is typically defined by taking rights away from someone, to "protect kids". This is simply feeding the poor, and babies. No comparison.
Not everyone has the fortunate needed to fight a bad system from within, or the desire to, no matter how many heartstrings you pull to try shame them into reconsidering the good within the bad.
The government is not bad. A tiny part (the current administration) is the problem.
To give context, you'd need a string of "one team" government for decades to turn the course of the entire government. Programs enacted by both US teams are currently in play. Some programs are decades old, and supported by both parties.
Anyone who thinks that a certain team gets into power, and then "all government bad" is not thinking clearly. What you need to do, is look at what each department and each program does. Determine if they are good. It absolutely does not matter which administration passed it, or when. All that matters is "is this thing good?".
The government should be viewed as series of literally tens of thousands of companies. Each has its own task, provides specific services, and so on. To paint them all bad is nutty.
> I literally said "every job". You're saying "sometimes" they might be. What is your point?
You are completely ignoring the “you don't always know the full nature of the task until after clearance” part. If you don't know it isn't one that will be a problem for you, it could be one that is. My point there is that bit.
> And I specifically excluded the military.
So did I. Hence I explicitly said afterwards “And that is before considering those who want “conscientious objector” status with regard to anything military related."
I stopped reading at this point because if you didn't bother properly reading my previous before blurting out a response, then explaining more, giving you more to not fully read, will likely achieve nothing beyond consuming my time.
I'd say up to a couple of hundred is much more than 40. Not a full decimal order of magnitude, but even without compression the 170KB on one side is up to 4½×.
> isometric on the C64 with such an amazing level of detail - simply gorgeous
Or a convincing representation of that. A lot of old tricks mean that the games are doing less than you think that they are, and are better understood when you stop thinking “how do they do that” and “how are they convincing my brain that is what they are doing”.
Look at how little RAM the original Elite ran in on a BBC Model B, with some swapping of code on disk⁰. 32KB, less the 7.75KB taken by the game's custom screen mode² and a little more reserved for other things¹. I saw breathy reviews at the time and have seen similar nostalgic reviews more recently talking about “8 whole galaxies!” when the game could easily have had far more than that and was at one point going to. They cut it down not for technical reasons but because having more didn't feel usefully more fun and might actually put people off. The galaxies were created by a clever little procedural generator so adding more would have only added a couple of bytes (to hold the seed and maybe other params for the generator) each.
Another great example of not quite doing what it looks like the game is doing is the apparently live-drawn 3D view in the game Sentinel on a number of 8-bit platforms.
--------
[0] There were two blocks of code that were swapped in as you entered or self a space station: one for while docked and one for while in-flight. Also the ship blueprints were not all in memory at the same time, and a different set was loaded as you jumped from one system to another.
[1] the CPU call stack (technically up to a quarter K tough the game code only needed less than half of that), scratch-space on page-zero mostly used for game variables but some of which was used by things like the disk controller ROM and sound generator, etc.
[2] Normal screen modes close to that consumed 10KB. Screen memory consumption on the BBC Master Enhanced version was doubled as it was tweaked to use double the bit depths (4ppb for the control panel and 2bbp for the exterior, instead of 2bbp and 1ppb respectively).
It also serves to leave some space unused to help out the wear-levelling on the SSDs on which the RAID array that is the PV¹ for LVM. I'm, not 100% sure this is needed any more² but I've not looked into that sufficiently so until I do I'll keep the habit.
--------
[1] if there are multiple PVs, from different drives/arrays, in the VG, then you might need to manually skip a bit on each one because LVM will naturally fill one before using the next. Just allocate a small LV specially on each and don't use it. You can remove one/all of them and add the extents to the fill LV if/when needed. Giving it a useful name also reminds you why that bit of space is carved out.
[2] drives under-allocate by default IIRC
reply