Ubuntu deployment : imaging across different hardware
-
I was wondering if anyone has experience imaging Ubuntu across different hardware? With windows machines I know there are different steps to take when imaging across different hardware. Does anybody know if this is the same for Linux?
-
I request you search the forums. In Particular for the SAD2 tutorial written by andyroo54. That or Liam Sullivan’s post?
[url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url]
-
[quote=“Ericsj860, post: 36176, member: 25563”]I was wondering if anyone has experience imaging Ubuntu across different hardware? With windows machines I know there are different steps to take when imaging across different hardware. Does anybody know if this is the same for Linux?[/quote]
If I get this correctly, your asking about deployment for Linux (Ubuntu) clients?
If yes, then here’s what I would surmise:
A) most current distro’s/kernels are all modular - EG, the kernel will load any needed modules (other than disk access) as needed for most hardware. HBA modules should be for the most part included (ata for the large majority of client computers).
B) Video support could be an issue - Linux frame buffer and X11 (Gnome) settings are usually tailored to the client computer’s video adapter and monitor.
C) Ethernet devices tend to get static names if they are not virtualized = EG, a NIC that came up as ETH0 in the master computer is not available in the client computer, and while there’s only one NIC available, the “new” NIC will be ETH1. A script would have to be written to remove the persistent-net-dev entries.Other than that, I don’t see anything off the top of my head that would pose an issue. If your familiar with linux (Ubuntu), this should all be scriptable. FOG itself does not have any “oobe” type prep tools, and I’m not aware of any that are available otherwise for Ubuntu.
