-
Notifications
You must be signed in to change notification settings - Fork 10
[Review needed] Swap file creator #18
Copy link
Copy link
Open
Labels
CFor issues on the topic of C source code.For issues on the topic of C source code.File systemFor issues on the topic of file systems.For issues on the topic of file systems.IssueFor WacOS project issues that are raised.For WacOS project issues that are raised.Memory managementFor issues on the topic of memory management.For issues on the topic of memory management.Review neededFor issues that need review.For issues that need review.SWAP MakerFor issues related to the SWAP Maker component.For issues related to the SWAP Maker component.SWAP MemoryFor issues on the topic of SWAP Memory.For issues on the topic of SWAP Memory.help wantedExtra attention is neededExtra attention is neededquestionFurther information is requestedFurther information is requested
Metadata
Metadata
Assignees
Labels
CFor issues on the topic of C source code.For issues on the topic of C source code.File systemFor issues on the topic of file systems.For issues on the topic of file systems.IssueFor WacOS project issues that are raised.For WacOS project issues that are raised.Memory managementFor issues on the topic of memory management.For issues on the topic of memory management.Review neededFor issues that need review.For issues that need review.SWAP MakerFor issues related to the SWAP Maker component.For issues related to the SWAP Maker component.SWAP MemoryFor issues on the topic of SWAP Memory.For issues on the topic of SWAP Memory.help wantedExtra attention is neededExtra attention is neededquestionFurther information is requestedFurther information is requested
[Review needed] Swap file creator
I created a new component of the system today, which is a SWAP file creator. It isn't functional yet, but I have already run into a design problem:
Modern SWAP files are very large. For reference, my laptops SWAP file is 2 gigabytes (2 trillion bytes) the SWAP file maker I made is designed to take up less memory in its source code, but build a SWAP file byte by byte, running a command for every blank byte added to the SWAP file located at SWAPFILE.bin (which I will change to .swp in the future) I can't just upload a SWAP file to GitHub, as 1. It would be too large and 2. Not every SWAP file for every installation is the same size.
This is a fragment of the 3rd variation of the C code for reference. It is not functional yet and is mostly pseudocode (you might need to view the full file to get all the context)
The full source code can be viewed here or here
I have been told by family members that this sounds like a virus. I don't know enough about it to agree, but I feel like doing this could damage/destroy a storage device easily. I wonder if there is a better way of doing this. Does anyone know?
File version:
1 (2022, Friday, January 14th at 7:37 pm)