<!-- This page is crated automaticaly by a script.This part is commented and shall not show--><!--At the top of the page can be visible one of the following tags..-->{{WorkInProgressNeedsUpdate}}{{NeedsMerge | [[Main Page]]}}<!--{{NeedsExpantion}}--><!--{{NeedsDelete |[[Main Page]]}}--><!--Please remove or place comment accordingly--><!--Your text bellow this line--> <b>Post-Install Hardware Changes</b>

=<b>Preliminary:</b> =Swapping hardware in a Linux system such as Amahi(Fedora/Fedora Ubuntu) is very forgiving and simple for the most part. Amahi does depend, however, on having the eth0 network interface and your shares depend on having the right drives and SATA ports identified between hardware changes to avoid lengthly <i>lengthy</i> repair processes. Note that all of these apply mostly the same if you're running within a virtual machine. Some VM hypervisors abstract the parts enough that the OS will not notice new hardware and not rename it (eg: eth0 to eth1).

If swapping:<br />>> =Motherboard/ SATA-controller/ RAID-card <<<br />=- you have no changes to make when booting back into FedoraLinux, which will just re-fit drivers to the new part. <br />- It is VERY advisable though, to reconnect your drives in the same sequence they were before the swap of the motherboard/ sata-controller/ RAID-card..<br />

- In the BIOS/ UEFI, ensure that the boot sequence is also the sameas before the upgrade or swap. <br />>> Finally, after replacing or even adding drives, run a 'greyhole -f' and a 'greyhole -l' as sudo in terminal to completely re-discover what you may have had in the greyhole storage pool.

If swapping:<br b></b>>> network card << <br />=Network Card=

- If anything eth0 may become eth1 afterwards, so you will need to rename it to eth0 via the Network Manager in the Fedora desktop. You'll want to reboot to finalize changes. (((command-line process coming soon)))<br />- use your favourite command line editor and edit with sudo/su.. $/etc/udev/rules.d/70-persistent-net.rules

<!--Your text above this line-->=CPU / RAM / video card=<!--This page must bellong no changes need to one be done after boot. These drivers and modules should automatically load on a reboot of the following categories please remove comment-->Linux VMs.<!--[[category:Apps]]--br />[[Category:Fedora]]<!--[[Category:Platform]]--><!--[[Category:Pro Version]]--><!--[[Category:Services]]--><!--[[Category:VPN]]-->this is because the hypervisor is abstracting the CPU to the VM regardless.

<noincludeb>[[Category:WikiModTools]]</noincludeb><br />