Re: What is the correct way to overide hal defaults?
On Sat, 13 Jun 2009 18:05:14 +0200, Tom Rauchenwald wrote: Micha Feigin writes: I want to change the default settings for my synaptic touchpad in X. I tried changing /usr/share/hal/fdi/policy/20thirdparty/11-x11-synaptics.fdi but it keeps getting written over during upgrades. Is there a better way to do this so it won't get erased every time? Put your changed file in /usr/share/hal/fdi/policy/, and it should be used by hal and it won't be touched on upgrades. Thanks -tom The corect place for these modified files is in /etc/hal/fdi/policy/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
How to make Fn+F3 (suspend) combo work in Debian?
Hi all! My laptop is HP Compaq nx7300. I want to make my suspend button (Fn+F3) work in debian. I want to do this through hal by properly editing file /usr/share/hal/fdi/information/10freedesktop/30-keymap-hp.fdi and copy it to /etc/hal/fdi/policy. My question is, how to find out what keycode I must to use in this file to make hal understand it? Regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Re: Ctrl-Alt-Backspace disabled?
Jan Willem Stumpel wrote: > Andrei Popescu wrote: (about getting ctl-alt-backspace back): >> You need >> >> Option "DontZap" "false" >> >> in the ServerFlags section of your xorg.conf (check the manpage for >> xorg.conf, I'm writing from memory). > > This worked for about a week -- but nannyism has crept further. In > the latest Sid, even this trick doesn't work anymore. How to get > it back, I wonder. I just enabled keyboard layout in K>Systemsettings>Regional&Language>Keyboard Layout, and there, in advanced tab I check: Key sequence to kill X server (Control+Alt+Backspace). Regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: apt pinning and getting linux-image-686 from unstable
H.S. wrote: > I suppose you meant 'wrong'. What is the correction? How about the > following? > > ~$ cat /etc/apt/preferences > Package: * > Pin: release a=testing > Pin-Priority: 700 > > Package: * > Pin: release a=unstable > Pin-Priority: 200 > > > and to use "-t" with the package I want. > > Would this work in tracking the newer version of the kernel package from > unstable once I install it using -t? > Yes. Once you installed kernel with -t from unstable aptitude will tracking any upgrades to this kernel. It will stop if the kernel migrates from unstable to testing. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: apt pinning and getting linux-image-686 from unstable
H.S. wrote: > Hello, > > Can somebody tell me if the following is possible using apt pinning? I > want to install the newer version of kernel (linux-image-2.6-686, ver > now is, I think, 2.6.29-3) from Untable to my Testing machine. > > I am thinking of using apt pinning. I know that I need to set the > default release to "testing" in apt.conf, add unstable sources to > sources.list and then create /etc/apt/preferences file specifying the > package I want from unstable and its priority. Something like: > > ~$ cat /etc/apt/preferences > Package: * > Pin: release a=testing > Pin-Priority: 700 > > Package: > Pin: release a=unstable > Pin-Priority: 1000 > > Package: * > Pin: release a=unstable > Pin-Priority: -1 > > > Now, what do I put in place of ? > Should be linux-image-2.6.29-1-686? In this case, only this version of > the kernel would be pulled from Unstable and no updates? > > Or should it be linux-image-2.6-686? But this would then just check > unstable for updates to the default kernel in testing and ignore the > updates to the default testing package of the same name, right? > > Or should I use: > Package: linux-image-2.6-686 > Pin: release a=unstable, version 2.6.29* > Pin-Priority: 1000 > > > Thanks. > Would it be easier to just pin unstable repo like this? : Package: * Pin: release a=testing Pin-Priority: 700 Package: * Pin: release a=unstable Pin-Priority: 500 and then install newer kernel by: aptitude -t unstable install linux-image-2.6.29-2-686 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: missing the initrd file in the kernel package
Manoj Srivastava wrote: > Now, nothing is created automatically. you need to provide a > hook script for this to happen. The user provides such scripts. For > example, to invoke mkinitramfs, I did: > --8<---cut here---start->8--- > cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs \ > /etc/kernel/postinst.d/ > cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/initramfs \ > /etc/kernel/postrm.d/ > --8<---cut here---end--->8--- > > To run grub, I have in /etc/kernel-img.conf: > --8<---cut here---start->8--- > postinst_hook = update-grub > postrm_hook = update-grub > --8<---cut here---end--->8--- > > You can look at other example in the examples directory: > /usr/share/kernel-package/examples/ > to see if there are other example script you want to cp into > /etc/kernel -- and you can create your own scripts. > Now everything is clear to me ;) Big thanks! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: missing the initrd file in the kernel package
Manoj Srivastava wrote:
> On Wed, Apr 29 2009, Antonio Diaz wrote:
>
>> When I compile the kernel the file "initrd" is not created in spite
>> of I'm specifying the "--initrd" option in the command line. Exactly,
>> the command that I'm using to compile the kernel is:
>>
>> "make-kpkg --initrd --revision=1:xps.10 kernel_image"
>>
>> May be there is a problem with the application that creates the
>> initrd file.
>>
>> Any suggestions?
>
> ,[ Manual page make-kpkg(1) ]
> | --initrd
> | If make-kpkg is generating a kernel-image package, arrange to
> | convey to the hook scripts that this image requires an initrd,
> | and that the initrd generation hook scripts should not short
> | circuit early. Without this option, the example initramfs hook
> | scripts bundled in with ker‐ nel-package will take no action on
> | installation. The same effect can be achieved by setting the
> | environment variable INITRD to any non empty value. Please note
> | that unless there are hook scripts in /etc/kenel or added into
> | the hook script parameter of /etc/kernel-img.conf. no initrd
> | will be created.
> `
>
> So, drop in scripts in /etc/kernel/post{inst,rm}.d/ to
> create/delete the initramfs files. You can use yaird, or
> initramfs-tools. For the latter, there are example scripts that you
> could use as a starting point:
> /usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/initramfs
>
> manoj
I upgraded to kernel-package 12.010
If i use a :
make-kpkg --initrd kernel_image
then created .deb will have a initrd image ?
And it will install it ?
Sorry but my english is not so good, so i'm trying to get this clear.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
