|
Bugzilla – Full Text Bug Listing |
| Summary: | Please provide sfdisk during installation and on rescue image | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Hans-Peter Jansen <hpj> |
| Component: | Basesystem | Assignee: | Steffen Winterfeldt <snwint> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | hpj |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Steffen, what do you think? fine with me cool, nice to hear. Can I take my wish granted? For what version? in beta-2 |
The most dominant reason to create a customized rescue image here (besides asigning a root passwd) is the missing sfdisk. Why? If you have to set up a complex sw raid 5 system with e.g. 10 partitions on each of 5 disks, it's a lot easier to create the partition layout once, and then copy it over. With sfdisk, it's as simple as running: for d in sd{b,c,d,e}; do sfdisk -d /dev/sda | sfdisk /dev/$d; done Easy, isn't it? If you do this with yast, you're going mad with creating those 50 partitions (at least I'm..), and I bet nobody get through this without doing some errors! Not to speak of the gain in time. In the rescue case, it's also preferable to be able to clone the partition layout quickly.