| 23 May 2024 |
|  Infinidoge 🏳️⚧️ changed their display name from Infinidoge to Infinidoge🏳️⚧️. | 01:31:17 |
| Infinidoge 🏳️⚧️ changed their display name from Infinidoge🏳️⚧️ to Infinidoge 🏳️⚧️. | 01:31:27 |
|  zoechi joined the room. | 05:33:26 |
|  lazycaaat joined the room. | 10:47:09 |
| 26 May 2024 |
|  @user6372:matrix.org left the room. | 17:25:48 |
|  arndot joined the room. | 19:53:37 |
| 28 May 2024 |
|  netpleb joined the room. | 17:50:30 |
| netpleb | I have a flake nixos system but where the root partition is ext4 and I would like to convert it to btrfs. There are some tutorials for non-nixos systems to do this, but I am a little confused how to do it on nixos. | 17:52:10 |
 K900 | Generally, reinstall is your best option | 17:54:49 |
| K900 | If you really want to avoid that, boot a live CD, btrfs convert, mount as btrfs, adjust config, nixos-install | 17:55:20 |
| netpleb | the git repo / flake which declares the system is currently on the root partition itself, so my thinking is something like the following should work:
- clone git repo to thumbdrive
- boot into some sort of recovery mode (or do I need a full live distro on another thumbdrive and boot into it?)
- do the conversion to btrfs (
btrfs convert ...), mount it, and so on
nixos-generate-config and grab the relevant parts of the new hardware config, put them in flakenixos-rebuild switch
| 17:55:53 |
| netpleb | In reply to @k900:0upti.me
If you really want to avoid that, boot a live CD, btrfs convert, mount as btrfs, adjust config, nixos-install Ok, thanks. I probably should just reinstall it seems, and properly backup beforehand. | 17:57:13 |
 Ramses 🇵🇸 | You don't need to wipe the disks, you can do an installation as usual, but instead of creating new partitions, you do the conversion, and then continue with the installation as usual | 17:58:05 |
| Ramses 🇵🇸 | I'd still take a backup beforehand just in case though | 17:58:20 |
| netpleb | In reply to @rvdp:infosec.exchange
You don't need to wipe the disks, you can do an installation as usual, but instead of creating new partitions, you do the conversion, and then continue with the installation as usual what about doing the whole thing over ssh? too risky? | 18:01:23 |
| Ramses 🇵🇸 | If you're comfortable with kexec'ing into an image in memory, then it's doable. If you've never done that before, then I'd make sure that you're able to get to the machine in case you mess up | 18:03:13 |
| K900 | I would generally not do anything but routine updates over SSH with no backup plan | 18:04:40 |
| netpleb | In reply to @rvdp:infosec.exchange
If you're comfortable with kexec'ing into an image in memory, then it's doable. If you've never done that before, then I'd make sure that you're able to get to the machine in case you mess up I have never done that before, but it sounds like that is what I would like to do. I can get to the machine physically if I mess up. Is kexec'ing better than, say, this: https://lord.re/en/posts/58-pivot_root-unmount-son-root/ ? | 18:05:02 |
| K900 | Honestly | 18:05:25 |
| K900 | If you can get physical access to the machine | 18:05:29 |
| K900 | And it doesn't require, like, driving to a data center | 18:05:35 |
| K900 | Just reinstall | 18:05:36 |
| K900 | It's not worth the trouble | 18:05:39 |
| Ramses 🇵🇸 | Unless you do it for educational purposes, I agree | 18:06:14 |
| netpleb | In reply to @k900:0upti.me
If you can get physical access to the machine Yeah, but this is practice for when such physical access is too much of a pain. | 18:06:32 |
| K900 | Uhh | 18:06:41 |
| K900 | If you actually have a production system you have to attempt this on | 18:06:53 |
| K900 | You have a MUCH bigger problem | 18:06:57 |
| K900 | btrfs convert is something you do as a joke | 18:07:15 |
| K900 | Not something you do to systems you care about | 18:07:24 |
