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]
Date:	Sun, 4 Feb 2007 00:50:13 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Elimar Riesebieter <riesebie@...ec.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.20-rc7: hid on PPC

On Fri, 2 Feb 2007, Elimar Riesebieter wrote:

> it would be great, if we can choose pb_fnmode while configure the 
> kernel. I have a PowerBook5,6 but want fkeysfirst. So I have to # echo 2 
> >| /sys/module/hid/parameters/pb_fnmode by hand after each boot. The 
> module-parm pb_fnmode doesn't work either in /etc/modules nor in a 
> modprobe instruction while boot. An modprobe -r usb-hid hid; sleep 2; 
> modprobe hid pb_fnmode=2; modprobe usb-hid works on a fresh booted 
> machine. Else module-parm isn't available with a built-in hid, though.

Hi Elimar,

sorry, but I don't seem to understand your problem. There are two 
situations - either you have hid bultin in kernel, or compiled as a 
module. In the first case, you simply modify the kernel boot commandline 
to contain a string 

	hid.pb_fnmode=2 

and that's it. In the latter case, you add something like 

	options hid     pb_fnmode=2

into the /etc/modprobe.conf file (or you can use any distro-specific way 
to pass parameters to modules, such as /etc/modprobe.d). This is standard 
way to do things, and it works also with hid.

I don't think there is a need to have this as a separate kernel 
configuration option.

Thanks,

-- 
Jiri Kosina
SUSE Labs
-
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