|
Bugzilla – Full Text Bug Listing |
| Summary: | no partitions available in YaST2 partitioner | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Wolfgang Engel <wolfgang.engel> |
| Component: | YaST2 | Assignee: | Thomas Fehr <fehr> |
| Status: | VERIFIED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | al4321, dev |
| Version: | RC 4 | ||
| Target Milestone: | --- | ||
| Hardware: | S/390 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Wolfgang Engel
2005-09-21 13:30:40 UTC
Tried calling you but failed. I need either access to a test system or the logs from /var/log/YaST2 detection has been fixed in preview1 for SL 10.0 you need yast2-storage-2.13.1 or newer for that. being able to partition a dasd needs some more work. well, yes, I experience the *same* problems - Yast's Partitioner doesn't work ! My hardware: AMD Sempron CPU, 1GB RAM, VIA KM400 chipset, 200 GB Hard Disk (WD2000JB, IDE, Western Digital) OS: SUSE Linux 10 RC1 The only 3 things I think of, that may have different non-standard. those are: a) my hard disk is >128 GB (it causes errors/problems with some OSes) b) My hard disk is connected to /dev/hdd c) I have lots of partitions: (having different filesystems on them) hdd1 hdd5 hdd6 hdd7 hdd8 hdd9 hdd10 hdd11 hdd12 Some are: ext3, reiserfs, linux-swap, FAT16, FAT32, NTFS... I do notreally see what comment #3 has to do with the original bug report. Original bug report was about missing detection of DASD disks on a IBM S/390, so it is certainly something completely different. Attaching ones reports to completely unrelated bug report is not really advisable. Nevertheless. to be able to do something about the report in comment#3 I need the files from /var/log/YaST2 to do something about it. All DASD handling should be fine with yast2-storage-2.13.3 Closed. *** Bug 1182512 has been marked as a duplicate of this bug. *** |