From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000417]: makedevs behavior differs from documentation
Date: Mon, 12 Feb 2007 05:48:52 -0800 [thread overview]
Message-ID: <265e8c8dc174a0ffce0470ad40a33d96@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=417
======================================================================
Reported By: sho
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 417
Category: Other
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 09-07-2005 11:37 PDT
Last Modified: 02-12-2007 05:48 PST
======================================================================
Summary: makedevs behavior differs from documentation
Description:
According to the documentation, the makedevs interprets the value in the
last column of its input file as the number of devices to create. This is
not true, for exampele should the default configuration create hda[1-15],
but hda15 is missing. Changing the statement
for (i = start; i < count; i++)
in makedevs.c into
for (i = start; i < start+count; i++)
should fix the problem.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
09-07-05 11:37 sho New Issue
09-07-05 11:37 sho Status new => assigned
09-07-05 11:37 sho Assigned To => uClibc
01-25-06 07:27 prpplague Status assigned => closed
01-25-06 07:27 prpplague Resolution open => won't fix
01-25-06 07:27 prpplague Additional Information Updated
02-12-07 05:48 vapier Status closed => assigned
02-12-07 05:48 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=265e8c8dc174a0ffce0470ad40a33d96@bugs.busybox.net \
--to=bugs@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox