|
Bugzilla – Full Text Bug Listing |
| Summary: | Strange Partitioning Proposal | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Karl Eichwalder <ke> |
| Component: | YaST2 | Assignee: | Thomas Fehr <fehr> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | Beta 4 | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Documentation | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | log | ||
|
Description
Karl Eichwalder
2006-02-02 07:42:43 UTC
Created attachment 66143 [details]
log
Please attach the output of `fdisk -l' and your /etc/fstab of this system. Isn't this in the attachment? Now, it's too late because the new system is already installed. OK let's reassign it to Thomas. Thomas: With problems which are related to the partitioner, what additional information do you need? Is the information in the logs really sufficient? In general the y2log files are sufficient for storage related problems (these contain partitions layout and fstab content as well). There are of course rare cases where one needs additional data, but I am perfectly fine with gettings these from reporter directly if needed. It simply would not make sense to generally demand files that are only needed very seldom cases (eg if device-mapper, sw raid, LVM is involved). Of course y2log files are always needed it is virtually impossible for me to debug nontrivial things without complete y2log files. This one is a duplicate that will be fixed in beta#4. *** This bug has been marked as a duplicate of 147651 *** |