|
Bugzilla – Full Text Bug Listing |
| Summary: | installkernel confused by RAID | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | stephen hemminger <shemminger> |
| Component: | Basesystem | Assignee: | Joachim Plack <jplack> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
stephen hemminger
2006-01-06 03:15:34 UTC
Stephen, this is *not* a bugzilla bug - this component is ONLY for bugs in bugzilla itsself. So, if you can't report a bug, report it here ;-) Please move this bugreport to Product "SUSE Linux X.Y" (choose your version) and a matching component, then set the bugreport back to ASSIGNED. Tsts. jack? Well the problem comes from 'udevinfo' giving no output. Dunno nothing about that tool.
Will change that Tools.pm handles that gracefully.
Code in question:
open (OUT, "udevinfo -q name -p /block/$udev |") || die "Cannot run udevinfo";
my $dev = <OUT>;
close OUT;
chomp ($dev);
ok submitted to svn. Kay can you give me advice what might have gone wrong?. May be the output 'no record for '/block/sda/uevent' in database' from up there can give you a hint You can't call udevinfo for the device _attribute_ "uevent", it expects a _real_ device. Udevinfo does only print stuff that custom rules have stored in the udev database. "Default" device names are the same as the sysfs names. What information does the perl code expect from udevinfo? the code path that call udevinfo is actually a little bit hacky and could need some major rewrite. But errors are handled ok for now. so -> fixed |