You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes partition tables are corrupted, harddrives are damaged or disfunctional and pertinent data needs to be retreived. In certain situations when you're dealing with deployment strange stuff happens. Like sometimes people will want to get the entirety of their systems from one harddrive to another. Dealing with Windows without their new imagex system has many a time been a pain in my tuchus. But Nix(OS) however should be able to "automagically" facilitate this process easily. Now before you go on about how this filesystem supports this kind of redundancy and that kind redundancy remember: we want a general tool that can be used with Nix, to not only install and manage systems, but IMHO to easily reinstall them without much hastle (just a couple of nix files, a copy of the partition, and you're set).
So what I would suggest is adding a new file to /etc/nix/ that contains a store of information required to identify partitions, that is created or added to under the install or rebuild process. To coin a function like this is hard though, so I'll just call recognise:
As you see this setup does three things: it mounts root, it formats /nix/store partition on install/rebuild and the /home partition just has a partID. The reason the partID is even included (and maybe need re-coining) is to use it as an index number, really. The process should then check something like /etc/nix/partid.bin, through a secure process (in any case only nix and root should have access to it), for recognizable values or patterns that may identify this partition. In any case if you have a damaged partition we can start discussing how to facilitate an interactive "attempt to fix" process, or through declarations for that matter.
In any case it would make moving from system to system a breeze, which is again more of usability than functionality. But I'd still like to see something like this...
The text was updated successfully, but these errors were encountered:
third3ye
changed the title
Adding filesystems-id.nix and a partition recognition process
Adding partID and a partition recognition process
May 15, 2014
Sometimes partition tables are corrupted, harddrives are damaged or disfunctional and pertinent data needs to be retreived. In certain situations when you're dealing with deployment strange stuff happens. Like sometimes people will want to get the entirety of their systems from one harddrive to another. Dealing with Windows without their new imagex system has many a time been a pain in my tuchus. But Nix(OS) however should be able to "automagically" facilitate this process easily. Now before you go on about how this filesystem supports this kind of redundancy and that kind redundancy remember: we want a general tool that can be used with Nix, to not only install and manage systems, but IMHO to easily reinstall them without much hastle (just a couple of nix files, a copy of the partition, and you're set).
So what I would suggest is adding a new file to /etc/nix/ that contains a store of information required to identify partitions, that is created or added to under the install or rebuild process. To coin a function like this is hard though, so I'll just call recognise:
As you see this setup does three things: it mounts root, it formats /nix/store partition on install/rebuild and the /home partition just has a partID. The reason the partID is even included (and maybe need re-coining) is to use it as an index number, really. The process should then check something like /etc/nix/partid.bin, through a secure process (in any case only nix and root should have access to it), for recognizable values or patterns that may identify this partition. In any case if you have a damaged partition we can start discussing how to facilitate an interactive "attempt to fix" process, or through declarations for that matter.
In any case it would make moving from system to system a breeze, which is again more of usability than functionality. But I'd still like to see something like this...
The text was updated successfully, but these errors were encountered: