Re: What is the usage of an empty RPM ?

wrote: > > > > On Tue, Feb 4, 2014 at 11:30 AM, Kevin Wilson wrote: >> >> Hi, >> What is the usage of an empty RPM ? What it is for ? >> For example, on Fedora 20: >> >> rpm -qpl libvirt-1.1.3.3-2.fc20.x86_64.rpm >> shows: >> (contains n

What is the usage of an empty RPM ?

Hi, What is the usage of an empty RPM ? What it is for ? For example, on Fedora 20: rpm -qpl libvirt-1.1.3.3-2.fc20.x86_64.rpm shows: (contains no files) Regards, Kevin Wilson -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora

shared flag of mounts in F18

Hello, I found out that in F18, the shared flag is set for many partitions, including "/" (I found it by cat /proc/self/mouintinfo). As far as I remember, it was not so in F17 (but I am not sure) My question is : why is this flag set ? who sets it ? regards, Kevin -- devel mailing list devel@

Re: building kernel - fedora 17: no success with insmod

thnks! On Tue, Oct 2, 2012 at 3:15 PM, drago01 wrote: > On Tue, Oct 2, 2012 at 3:13 PM, Kevin Wilson wrote: >> Hi, >> Thanks! >> >>> If you actually build the kernel with RPM as >>>suggested on the custom kernel wiki page, it will do the proper thing. >

Re: building kernel - fedora 17: no success with insmod

Hi, Thanks! > If you actually build the kernel with RPM as >suggested on the custom kernel wiki page, it will do the proper thing. can somebody provide a link to this wiki page ? rgs, Kevin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/dev

Re: building kernel - fedora 17: no success with insmod

Hi, Update: I found a workaround: adding EXTRAVERSION = -5.fc17.x86_64 in the Makefile. But shouldn't it be so when applying the src.rpm without any change from me ? rgs, Kevin On Mon, Oct 1, 2012 at 6:32 PM, Kevin Wilson wrote: > Hello, > I am running Fedora 17 on x86_64. > I w

building kernel - fedora 17: no success with insmod

Hello, I am running Fedora 17 on x86_64. I wanted to build bluetooth kernel module for f17 so I could use it under f17. I did this: download kernel-3.3.4-5.fc17.src.rpm. ran: rpm -ivh kernel-3.3.4-5.fc17.src.rpm rpmbuild -bp /root/rpmbuild/SPECS/kernel.spec It went well. Then , I went to /root/r

Re: biosdevname in fedora 15 - why is this inconsistency?

32 PM, Peter Robinson wrote: > > > On Fri, Jul 8, 2011 at 2:13 PM, Kevin Wilson wrote: >> >> Hello, >> I have biosdevname-0.3.8-1.fc15.x86_64 on fedora 15 machine. >> >> I see from >> man biosdevname , that the name of the devices should be:

biosdevname in fedora 15 - why is this inconsistency?

Hello, I have biosdevname-0.3.8-1.fc15.x86_64 on fedora 15 machine. I see from man biosdevname , that the name of the devices should be: .. em for embedded NICs pci#_ for cards in PCI slots .. ifconfig shows I have em1, p2p1; indded em1 is embedded NICs.