Guillaume Cottenceau wrote:
> Felix Miata <[EMAIL PROTECTED]> writes:
> [...]
> > > bugged and doesn't report failures, or your floppy has an
> > > hardware failure that didn't report to the floppy drive during
> > > bootdisk creation but lead to a misread when you tried to boot
> > > with it. I would favor the second option.
> > Not likely on mine. 8.2 installed just fine, but beta 3, beta 4, RC1, &
> > RC2 all did the same thing as above with me, except Beta 3 created
> > several zero byte files on the floppy. No zero byte files on the three
> > latter, but same error message when attempting boot as above. On all
> Is the floppy full? What happens when you try to copy the
> contents to the hd? And when you try to mount it? And when you
> try to read the files on it?
OS/2 listing of floppy:
The volume label in drive A is Al.
The Volume Serial Number is 3D7C:C2D3.
Directory of A:\
LDLINUX SYS 8092 9-09-02 3:48p
VMLINUZ 880519 9-06-02 11:25p
INITRD IMG 136292 9-09-02 3:48p
SYSLINUX CFG 133 9-09-02 3:48p
BOOT MSG 204 9-09-02 3:48p
5 file(s) 1025240 bytes used
431104 bytes free
BOOT.MSG contents (copied from floppy to HFPS HD):
Press <return> (or wait 10 seconds) to boot your Mandrake Linux system
from
/dev/hda7. You may override the default linux kernel parameters by
typing
"linux <params>", followed by <return> if you like.
SYSLINUX.CFG contents (copied from floppy to HPFS HD):
default linux
prompt 1
display boot.msg
timeout 100
label linux
kernel vmlinuz
append initrd=initrd.img root=/dev/hda7 devfs=mount
Would you like a diskette image emailed to you?
> > four 9.0 installs, installation boot was initiated from floppy,
> > network.img on the first, and hd.img on the latter three. On RC1 I
> > attempted mkbootdisk & drakfloppy after booting the HD, but got no
> > improvement. I emailed cooker list about this Thu, 29 Aug 2002 00:29:20
> > -0400 & Tue, 03 Sep 2002 03:00:11 -0400 & Thu, 05 Sep 2002 21:32:33
> > -0400 and got no replies.
> When no one answers on this list, it generally means that either:
> 1- the bug is likely to be invalid (happens when only one person
> reports something which is unlikely to happen)
> 2- the bug is considered non important, or we have more important
> bugs pending
> 3- the reporter doesn't report enough information
> 4- the reporter writes 200 lines talking about his life, so no
> one bothers wasting time to read
> 5- it would need much investigation from the reporter and we
> consider it would be a useless effort to try to initiate it
> 6- we don't have the knowledge to fix it
> 7- serveral people reported the same problem but the reports are
> inconsistent with each other
> 8- a similar problem has recently been fixed and the reporter
> doesn't clearly specify the version of software with failure
> (of course, I may have forgotten other situations ;p)
9-Everyone is frantically rushing against an unreasonable deadline to
release a distro that isn't ready yet.
> In this situation, I'd favor `2', but it's true that the problem
> also needs investigation from the people involved. Also, a big
I don't see how you can release a product incapable of creating a rescue
floppy either during or post install. I've seen several others report
this same problem I've encountered as long as several weeks ago.
> problem is that floppies are very likely to have hardware
> failures. Many times with similar bugs we spent time trying to
The exact same floppy worked just fine on the exact same machine using
the exact same floppy drive with 8.2. The same drive started the install
with a floppy made on the same drive using hd.img (and also network.img
for the beta 3 install).
> investigate, just to see that it was only due to h/w failure, so
> most of the times we don't bother.
Users should be able to see that Bugzilla is working. No matter what I
query there, I get "Zarro Boogs found". I've yet to get any response
from a MandrakeExpert posting either.
OTOH, Bugzilla at Mozilla works. Users can find existing bugs and not
duplicate them, or they can find that bugs have not been reported, and
file a report. They can also see what bugs have been fixed in a newer
release. Both users and developers can see what bugs are getting
attention, as well as what bugs exist.
Mandrake Bugzilla won't let me file a new bug.
--
". . . . in everything, do to others what you would have them do
to you . . . ." Matthew 7:12 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://members.ij.net/mrmazda/
