lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <200801291259.54262.gene.heskett@gmail.com>
Date:	Tue, 29 Jan 2008 12:59:54 -0500
From:	Gene Heskett <gene.heskett@...il.com>
To:	Daniel Barkalow <barkalow@...ervon.org>
Cc:	Mikael Pettersson <mikpe@...uu.se>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Richard Heck <rgheck@...jweil.com>, Zan Lynx <zlynx@....org>,
	Calvin Walton <calvin.walton@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux ide Mailing list <linux-ide@...r.kernel.org>
Subject: Re: Problem with ata layer in 2.6.24

On Tuesday 29 January 2008, Daniel Barkalow wrote:
>On Tue, 29 Jan 2008, Gene Heskett wrote:
>> >For starters, enable CONFIG_BLK_DEV_SR.
>>
>> That could stand to be moved or renamed, it is well buried in the menu for
>> the REAL scsi stuffs, which I don't have any of.  Enabled & building now.
>
>The "SCSI support type (disk, tape, CD-ROM)" section of that menu actually
>applies to all ATA-command-set devices that don't use the old IDE code.
>For example, usb-storage uses "SCSI disk" out of that section, and
>I've only seen "Probe all LUNs on each SCSI device" be needed for a
>particular USB card reader with two slots. At this point, most of the
>things in the kernel that refer to SCSI probably should say "storage" (or
>"ATA", really, but that would make the acronyms confusing).
>
>Incidentally, you should be able to save debugging time for problems like
>missing "sr" by building it as a module, which will build really quickly
>and not require a reboot to test.
>
>	-Daniel
>*This .sig left intentionally blank*

I did, Daniel, but while that has worked, its not been 100% foolproof in the 
past, so I just waste the 9 minutes building a new kernel as cheap insurance.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Mal: "If it's Alliance trouble you got, you might want to consider another
ship. Some onboard here fought for the Independents."
				--Episode #8, "Out of Gas"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ