[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#259420: marked as done (partconf-mkfstab: S/390 creates /dev/dasdX fstab, but uses devfs-named devices)

Your message dated Mon, 13 Jul 2009 12:57:08 +0100
with message-id <20090713115708.GT11691@riva.ucam.org>
and subject line s390 uses partman now
has caused the Debian Bug report #259420,
regarding partconf-mkfstab: S/390 creates /dev/dasdX fstab, but uses devfs-named devices
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
259420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=259420
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: partconf-mkfstab
Version: 0.31
Severity: important

When installing S/390 with debian-installer, I have swap on Partion 1 of
device 0151.  The fstab is written to use /dev/dasdb1, but when I IPL, I
get a devfs-style device, /dev/dasd/0151/part1, and there is no
/dev/dasdb1 device node.  Either S/390 should not use devfs, or the
fstab should be written to use devfs names. 

For some reason, /dev/dasda1, for the root partition, works fine even
though there's no /dev/dasda or /dev/dasda1 node; I think this is
because device 150, which is the first DASD listed in my parameter line,
is the device I IPL from, and so when it's detected there's no way to
tell whether it's going to be /dev/dasd/0150/disc or /dev/dasda.

Adam

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (700, 'testing')
Architecture: s390
Kernel: Linux 2.4.17
Locale: LANG=C, LC_CTYPE=C

--- End Message ---
--- Begin Message --- 
Since s390 has used partman rather than partconf for the last three
years, I don't think these bugs are relevant any more. In the case of
#259420, I believe that the fact that we no longer use devfs should
ensure that this has been fixed properly, but if it hasn't, then please
reopen the bug and reassign it to partman-target.

Thanks,

-- 
Colin Watson                                       [cjwatson@debian.org]

--- End Message ---
Reply to: