this post was submitted on 04 Jun 2024
29 points (100.0% liked)
196
17057 readers
715 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts require verification from the mods first
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
for some reason i feel like i shouldn't run that command
it creates a file with a size that'll keep growing until you stop it, filled with garbage data. it makes it extremely easy to create a file of 50 gigabytes or so. it does it over the course of about 8 minutes or so, so it's not like it's filling your hard drive to the brim immediately.
how does that work with the allocation of individual file sizes? Like what happens if you overflow your buffer before the system checks on it again to resize? or is that not possible/not a realistic risk factor?
it's probably possible, but it's not a realistic risk imo. i didn't track exactly how much time it takes to fill up 50 gigabytes, in practice it probably takes longer, i was just eyeballing how long it took lmao