[HowTo] bulletproof your personal effects (save your stuff!)

Cleaned up terminology because I wrote most of this in a semi-conscious state. So for my sake, I am writing about data terminology to compare against and also to enhance people’s understanding of digital storage, regardless if it were used in the OP:

Media: Any device used to communicate with a medium via a transport.
Medium: The host controller, with attached transport to media.
Transport: Any method of transfer, wireless or cabled.
Disk: Generally short for hard disk, as most people store data on those (if not using a solid-state media).
Partition: A defined range of space on any media to keep a finite amount of data.
Symbolic link: A reference by file ID, index node or absolute path to an existing file.

As I am also a Windows user, I was prone to using the word “Drive” a whole lot. I should have grown up in my eleven years and ventured to kick that habit real fast because drive could mean just about anything and mixing this in with disks and media wasn’t a good look, but I guess as with many other things I do that’s bad regarding Linux, old habits die hard.

Most recent edits were basically to clarify between “Disk”, “Media” and “Partition”, and to excise any instance of “Drive” as unnecessary and useless verbiage. The intent of this article is to explain how a common storage space is a great idea, but somehow I avoided mention of that at all in a post that’s about creating a common space for cross-platform access and ease of backup by excluding system files, which was a failure of my ability to communicate this idea directly.

I also waffle about between using one device and multiple, even though I mentioned I were assuming the worst and discussing about use of only a single media device. There are multiple scenario resolutions which accommodate both instances, leaving readers to resolve their data woes with what they have already. For novices, this article may overload them with too much information, which in future may be wholly re-written to further clarify the intent of this post.

Apologies for any confusion this may have caused.

Thank you, I was not sure where to put this information.

1 Like

This is great info, but it’s also “a wall of text” which won’t be read unless you split the commands, logic and explanations by using the [details=""] section much more than you’ve done now.

Have a look here. That one is also a “wall of text” when you expand all sections, and this one too but the point is: you don’t need to expand all sections: you just expand the ones you need to do what you want to do…

E.G. You can have detail sections within detail sections:

Headline
  • Lorem ipsum dolor sit amet,

    consectetur

    adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

  • Ut enim ad minim veniam,

    quis

    nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

by doing this:

[details="Headline"]
* Lorem ipsum dolor sit amet,
   [details="consectetur"]
   adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
   [/details]
* Ut enim ad minim veniam, 
   
   [details="quis"]
   nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
   [/details]
[/details]

(Yeah, it’s a bitch getting the spacing correct)

:innocent: :+1:

1 Like

I am use to dealing with that. Especially painful when writing about code, but if one already deals in code, one also is probably dealing in spacing of code and thus is use to the pain. (That, or one uses a text editor and does /n[spaces] performing find and replace operations.)

I understand the wall of text issue. I understand it too well. Manuals often suffer from this, so I suppose you could say as a compromise to accessibility, the way I write is more consistent with software manuals.

That is done by @admins not moderators.

1 Like

This is fantastic! I haven’t updated my desktop yet; I am going to follow this guide before I do. I really appreciate the step by step and the explanations. Thank you for taking your time to share this!

4 posts were split to a new topic: Correct size for root partition

The only reason why they do that is because of FlatPak being sandboxed. You’ll have 10+ copies of the same library across multiple applications, which is stupid in comparison to a shared library setup which takes up much less space.

As much as I love FlatPak and Snap in concept and understand how much dep hell it can prevent, I would rather just different version packages for different software. If something needs to be that specific to require its own libs, I wouldn’t mind it. And reallly, that is this topic’s target — the user who installs conventional packages, and maybe the occasional sandboxed software.

Not to say you’re wrong for what you’re doing, testing is great! And not everybody is conventional, nor should follow my advice. @Persephone should evaluate what software on the system is necessary and one’s own use habits before committing to the above advice. But I believe I provided sane defaults for most people trying any Linux system out.

Per my understanding, this configuration makes backing up more tenable for the average user than what OEMs provide for Windows by default because less thinking and configuration is involved. It can better integrate into a typical user lifestyle so when stuff goes wrong, it can become right faster.

Doing the dishes? Back up home.
Mowing the lawn? Back up root.
Working AFK or socializing? Back up effects.

Nice Article! Well done.

There are methods to access ext4 on windows – some of them are awkward, require programs or are read only. It’s been years since i’ve had to dual-boot and havent had windows in a long while, but I used to do it quite regularly.

think this is the one I used to use: https:// www.ext2fsd. com/

Other links a quick search found
https:// www.thewindowsclub. com/how-to-read-ext4-in-windows-10
https:// www.howtogeek. com/112888/3-ways-to-access-your-linux-partitions-from-windows/

(remove spaces from links to make them work)

I should had said, by default. Everything about data accessibility in the OP is about accommodating what your firmware / system allows normally rather than pulling out tricks to make systems do things they don’t perform by design.

The best part about this is every example provided doesn’t require the installation of additional software. A common space for effects which all systems respect is infinitely better than a configuration where you happen to need that one file from your home part, so you have to spin up your Ext2+ hack in Windows to grab it. Rather, this common space is what Windows and open-source systems can tap into without odd pieces of kit.

OS X, I am not sure about — Paragon still provides a utility for reading NTFS partitions but since I lack experience there, and I am not sure if Apple allows this by default now, I’d recommend exfat for Apple systems since in Apple’s own documentation they mention it as something which can be used in their Disk Utility application.

1 Like

Yeah,this is incorrect. @admins please give me additional time to edit so I can fix this. ntfs on OS X only applies to users of Paragon NTFS for OS X (or some other free solution) whereas exfat is suited for OS X as a common space.

So for practically everything, exfat, for Windows only, ntfs.

Yes… If they stick to vanilla (I never expect a new user to stick to vanilla) and if you consider today’s norm.
My two cents are there to allow for long run installs. Several years as I see on my 50+ converted friends.

:wink:

I’ve been using Ubuntu for years with my figures. Though, if someone isn’t sure and feel they need more space for the time being 48GB or even 64GB is a good bet.

Another thing I never mentioned (but should had) is the idea of making a backup that you can boot from to continue work. If it can fit on a USB stick, then you can continue to perform work if for some reason the primary media no longer functions and you kept work off of it. That’s actually a really good point I would love to append — the capability to become portable with use of a monolithic kernel.

That is why in scenarios where a RAID setup isn’t in anyone’s future, at the very least doing work on a USB stick can save the trouble of trying to recover most recent work if using a common area as a vault after work is no longer necessary to persist on the portable media.

1 Like

I will make a proper post on this later but it might be worth mentioning a project with a related but different aim:

I was finally given the capability to edit this post (and made an effort to remove my pleas from this topic), so I’ve tightened everything up and excised the fat I added previous so that the message conveyed comes across more clearly with correct information and additional reasoning for performing as described in the OP.

Half of the OP is a complete re-write, so it might behoove previous readers to look through it again.

1 Like

I added a ToC but the ToC is broken? Does it even work here?

Code:

> <big><a href='heading--one'>Preface</a></big>
> <big><a href='heading--two'>Preparation</a></big>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href='heading--twoA'>Assumptions</a>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href='heading--twoB'>Dual-boot</a>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href='heading--twoC'>File systems</a>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href='heading--twoD'>Media configuration</a>
> <big><a href='heading--three'>Execution</a></big>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href='heading--threeA'>Enabling the common space</a>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href='heading--threeB'>Using the common space</a>
> <big><a href='heading--four'>Why even?</a></big>

Sample heading

<H1 id='heading--one'>Preface</H1>

Very complete edition !
For unknown reason, here, I see the table of content, my cursor “sees” the links, but nothing happens : doesn’t move to the anchors.

Edited last post.

For anyone wondering what advice I followed, it’s here: Deep Linking to Headings (Anchors) - faq - Discourse Meta

1 Like

33 edits:pencil2: later and I think I am done with this. Unless there are outstanding grammatical issues I have no intention on tightening up the language further and bumping this topic since other posts deserve their time in the limelight as well.

I would still like to know what i am doing wrong with the table of contents. Could any @moderators please look at my code and figure it out? The last post I submitted has a URL to the article @nam1962 linked me (which was split off into its own topic about root part size) that shows a functional example but my issue may be due to Discourse meta using a later version of the software or deep linking is disabled.

:pencil2: In hindsight, some of those edits were from moderators but I wasn’t fussed about that when I made this post. Apologies to @moderators for constantly pinging them but I still need their help.

4 Likes

Hey, good we made some progress. The issue in your edit is that you missed the # where you have:
a href='heading--
Should be:
a href='#heading--
on each line from the content table …
Also, you can drop the > at the the beginning of each line of code in your edit, unless you want it to look like is a quoted part. Hope this will help you make the 34th edit :smiley:

Right, so uhm the reason why I made the ToC a quote block is to distinguish it from the body text, similarly to how Wikimedia foundation has a distinguishing of ToC in its software.

I’ll fix it later, rl stuff rn. :+1:

1 Like