|
Bugzilla – Full Text Bug Listing |
| Summary: | Partitioner Mount Point field(s) do not have /boot in list (feature?) | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Leah Cunningham <leah> |
| Component: | YaST2 | Assignee: | Thomas Fehr <fehr> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
short straight y2log
another clean y2log |
||
|
Description
Leah Cunningham
2005-08-18 22:57:01 UTC
The /boot field is only available during initial installation. If it's not present at that time please provide YaST2 logs. Can you explain what "during initial installation" means? This was field was
not available in the drop down "Mount Point" list in any of the installation
YaST2 menues. If that is intentional, that's fine, but I wasn't sure as it has
been there in the past. See attachment 46624 [details]
"during initial installation" is when you have booted from CD. You make a new installation and partition your harddisk. In this case the /boot entry is present. When you start YaST from the running system the /boot entry and others are missing since you already have a /boot partition or directory. In your log from the other bug I can see: FileSystems.ycp:861 suggest_m_points:["/", "/boot", "/usr", "/var", "/opt", "/home", "/srv", "/tmp", "/local", ""] The entry is also missing if you have already assigned /boot to a partition. /boot was never seen in any drop down menu. I created a RAID device /dev/md0, and then was presented with the screen to set mount point, format, etc. At that screen, /boot was not in the drop down menu, so it was typed in. I can try to reproduce that with a cleaner installation path, as several things were tried in that installation. Is it possible that if a /boot disk label had existed in the partition table before that it would not be available? You are right: In the RAID dialog it's missing. Created attachment 46689 [details]
short straight y2log
Thomas, I think in custom_part_lib.ycp around line 540 /boot is filtered out for RAID. Leftover from time where /boot on RAID wasn't supported? Created attachment 46697 [details]
another clean y2log
I went over it again with a clean partition table and saw the same thing with
RAID.
I changed the code that it allows /boot for raid type "raid1", other raid types are usuitable as /boot partition. |