Bug 470233
Summary: | RFE: allow firstboot to run system-config-users | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom Horsley <horsley1953> |
Component: | firstboot | Assignee: | Martin Gracik <mgracik> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 14 | CC: | amcnabb, dmach, kas |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | firstboot-1.111-1 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-01-18 12:54:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tom Horsley
2008-11-06 12:26:56 UTC
I notes this has some overlap with bug 212939, but it seems more important to do something like this since logging in as root became impossible (or very convoluted anyway :-). Yes, I definitely want to rework the firstboot add user module for F11. In particular I want to add something that lets you add the created user to sudoers, etc. I'm having a similar problem. If I could easily skip the account creation, I would be perfectly happy. I'm happy to do advanced stuff (like creating accounts with specific UIDs) on the command-line. Or even better, just have a button to bypass firstboot completely. Fixed in version firstboot-1.111-1 Yep, I was happy to discover the "Advanced" button in my F14 alpha firstboot that let me run s-c-u and specify all the details of the initial user. Thanks! In F14, I am able to create users and group using the Advanced button (s-c-u), but firstboot still thinks no users has been created yet, and does not allow me to continue unless a trick described in bug #543008 is used. This bug is probably related to bug #474007. |