The /etc/fstab written for S/390 assumes old-style, static /dev entries:
/dev/dasda1, /dev/dasdb1, and so on.
Unfortunately, the installed system does not have those device nodes,
but instead has devfs: /dev/dasd/address/part1, etc.
The first device (/dev/dasda) works in /etc/fstab and in the
On Fri, Jul 23, 2004 at 12:03:00PM -0500, Adam Thornton wrote:
I *think* this should go into subarch-dev in userdevfs, but I definitely
would like some confirmation of that before committing any changes.
userdevfs was written for systems that couldn't use devfs, 2.2 kernels
for instance. I far
Adam Thornton wrote:
The /etc/fstab written for S/390 assumes old-style, static /dev entries:
/dev/dasda1, /dev/dasdb1, and so on.
Unfortunately, the installed system does not have those device nodes,
but instead has devfs: /dev/dasd/address/part1, etc.
AFAICS the installed system shouldn't
On Fri, 2004-07-23 at 12:23, Thiemo Seufer wrote:
AFAICS the installed system shouldn't mount devfs. It also should have
static /dev entries, managed by makedev.
In that case where in the debian-installer build do I need to put the
script to generate the static /dev entries that the parmfile
Adam Thornton wrote:
On Fri, 2004-07-23 at 12:23, Thiemo Seufer wrote:
AFAICS the installed system shouldn't mount devfs. It also should have
static /dev entries, managed by makedev.
In that case where in the debian-installer build do I need to put the
script to generate the static /dev
On Fri, 2004-07-23 at 13:23, Thiemo Seufer wrote:
Are you sure this doesn't simply hide the static entries by mounting
devfs over it?
Well, no, I'm not. In fact, it probably does, and that's why the very
first /dev/dasda works.
So it looks like the right answer is to rebuild the kernel so as
6 matches
Mail list logo
