|
Bugzilla – Full Text Bug Listing |
| Summary: | Download release notes in 1st stage | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Ludwig Nussel <lnussel> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED FEATURE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | snwint |
| Version: | 13.1 Milestone 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Ludwig Nussel
2013-06-04 00:57:13 UTC
It's not clear to me where the network setup should happen. But I wouldn't burden linuxrc when yast can do it better with some nice ui. I think this belongs to the sles12 install workflow discussion. YaST doesn't do any networking setup during installation, does it? If you install from e.g. http linuxrc runs the dhcp client already IIRC. It does, when you add community repos or add-on products, afaik. In 1st stage? I didn't know that. Yes, in the first stage. Even SLES allows to add an add-on product from a remote repository during installation. This should be a FATE request. Suche fundamental changes in install logic should go through Product Management. Please create FATE request. This request comes directly from openSUSE "product management" ... Anyways, here you have a feature request: https://features.opensuse.org/315266 |