Bug 28395 - 00_scripts.sh sollte auch Skripte von Profildevice kopieren
00_scripts.sh sollte auch Skripte von Profildevice kopieren
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UCS Installer
UCS 3.0
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Installer maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-03 12:03 CEST by Sönke Schwardt-Krummrich
Modified: 2017-08-08 07:07 CEST (History)
0 users

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2012-09-03 12:03:49 CEST
Aktuell werden Installerskripte nur von der DVD in die initramfs kopiert, sofern auf der DVD welche im Unterverzeichnis scripts/ vorhanden sind.

Für profilbasierte SW-RAID-Installation wäre es gut, wenn auch Skripte von einem Profilmedium in das initramfs kopiert und verwendet würden.
Eine Anpassung der InstallationsDVD wäre dann nicht mehr notwendig.

Siehe auch Bug #28394.
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:36:01 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 2 Stefan Gohmann univentionstaff 2017-08-08 07:07:18 CEST
This issue has been filed against UCS 3.0.

UCS 3.0 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.