Although quite basic I just want to be sure what I'm doing in terms of procedure, is correct.
I have three machines, all have ext4 file systems and a separate /home drive or partition.
I want to change the UUID of /home on two of those to match that of the first, i.e. all three machines have the same UUID for /home. [1]
As I understand it from the "manual", one can use tune2fs as follows:
So I would:
1) boot from a live USB
2) use tune2fs to change /home's UUID
3) edit the relevant entry in /etc/fstab to reflect the changed UUID
I assume as home is mounted after "switch root" there is no need to mkinitrd ?
4) reboot normally and the new UUID should be in effect
Normally I'd be quite happy to just try, but in this instance I want to be sure I'm not making some basic (stupid) error... ;)
[1] All three machines have an area below ~/ that I keep synchronised using "unison" ( https://software.opensuse.org/package/unison ). In general this works well. However "digikam" (https://software.opensuse.org/package/digikam ) stores within it's database not only the path(s) to it's image collection(s) but also the UUID of the partition. Each time digikam is opened following a synchronisation which includes it's database files from another machine, it is necessary to tell digikam it is dealing with the same collection, as the UUID has changed. My rationale was if /home's UUID was the same on each machine then digikam would no longer think the collection is (possibly) the wrong one.
I have three machines, all have ext4 file systems and a separate /home drive or partition.
I want to change the UUID of /home on two of those to match that of the first, i.e. all three machines have the same UUID for /home. [1]
As I understand it from the "manual", one can use tune2fs as follows:
Code:
tune2fs /dev/{device} -U {uuid}1) boot from a live USB
2) use tune2fs to change /home's UUID
3) edit the relevant entry in /etc/fstab to reflect the changed UUID
I assume as home is mounted after "switch root" there is no need to mkinitrd ?
4) reboot normally and the new UUID should be in effect
Normally I'd be quite happy to just try, but in this instance I want to be sure I'm not making some basic (stupid) error... ;)
[1] All three machines have an area below ~/ that I keep synchronised using "unison" ( https://software.opensuse.org/package/unison ). In general this works well. However "digikam" (https://software.opensuse.org/package/digikam ) stores within it's database not only the path(s) to it's image collection(s) but also the UUID of the partition. Each time digikam is opened following a synchronisation which includes it's database files from another machine, it is necessary to tell digikam it is dealing with the same collection, as the UUID has changed. My rationale was if /home's UUID was the same on each machine then digikam would no longer think the collection is (possibly) the wrong one.