Actually, I think this is fix released. Since this bug was opened, oem-
config mode provided by ubiquity fully satisfies the requirements
outlined in this bug report.
** Changed in: ubiquity (Ubuntu)
Status: Invalid => Fix Released
** Changed in: oem-config (Baltix)
Status: New => F
For a brand new idea, you should create a blueprint. Since this doesn't
describe a bug in ubiquity, I am closing it.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Hello,
I know this thread is a bit old, but I am running into the same issue
and was wondering if there have been any news since the "sysprep
problem" was raised?
If no news, any suggestions regarding an effective way to deploy ubuntu
images without having to do all the small post install configs
** Package changed: oem-config (Ubuntu) => ubiquity (Ubuntu)
** Tags added: oem-config
--
Ubuntu needs a "sysprep"-like tool, like Windows has
https://bugs.launchpad.net/bugs/117084
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
** Also affects: oem-config (Baltix)
Importance: Undecided
Status: New
--
Ubuntu needs a "sysprep"-like tool, like Windows has
https://bugs.launchpad.net/bugs/117084
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Dustin,
My company is a system builder, and we run into similar issues. I made a
suggestion in Bug #191417 that oem-config automagically write a preseed
file so that subsequent installs could be replicated easily. Would that
accomplish what you are after?
--
Ubuntu needs a "sysprep"-like tool, l
System76, for one, are already using the facility we already provide for
this, namely oem-config. See the "Text mode install for manufacturers"
menu item on 7.04 CDs, and similar items on earlier versions, all the
way back to 5.10.
Some of your comments would be useful enhancements to oem-config (
There are deeper system implications for use case number 3: After
cloning a system, the UUIDs of the disk partitions will be different.
The partitions might be different: for example the root partition might
have been /dev/sda1 on the original machine, but on the cloned machine
it might be /dev/sda
Oh yeah, a third use case:
-imagine you work in the IT department of a large corporation that saves
time by cloning Ubuntu desktop machines: just after you've managed to
clone an Ubuntu machine, you want to hand it off to a new user. And
the freshly cloned machine needs to have a new hostname or
