Question

Question

[Michael van Rooyen]

[-- Attachment #1: Type: text/plain, Size: 616 bytes --]

Hello,

Are you looking for more B2B leads for your company?

We are selling a database of more than 313 thousand companies in South Africa.

Over 215 Thousand emails, 106 Thousand cells, and 226 thousand phones.

I have attached a sample for your reference. It is categorized into 2084 different industries.

It shouldn't cost an arm and a leg to land a new client. The entire database is R2000.

Let me know if you have any questions!

All data is POPI Compliant.

Have a lovely day!

Let me know if you have any questions.

-- 
Regards,
Michael Van Rooyen
065 837 2339
cardsman89@gmail.com

[-- Attachment #2: ZaCompleteSample.xlsx --]
[-- Type: application/octet-stream, Size: 22380 bytes --]

[-- Attachment #3: CategoriesFull.xlsx --]
[-- Type: application/octet-stream, Size: 47190 bytes --]

[-- Attachment #4: Type: text/plain, Size: 169 bytes --]

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Re: QUESTION

[Milan Broz]

I think you already got a reply, see
https://lore.kernel.org/cryptsetup/CACJx3YpDV2=J8rStSG685iBSW6OSEV2UaS4oRL6=qVGGSsoRvQ@mail.gmail.com/T/#t

cryptsetup is just tool to unlock disks, to handle input you need to load
all proper drivers and sw before it (in initramfs usually cryptsetup just
receive input (passphrase) from other tool, it does not handle query directly.

I am not sure if there is an easy way to do it, but this is definitely question
for your distribution. Systemd has a way how to ask external application for input,
but I have no idea if anyone use touch screen this way.

Milan


On 7/3/23 15:18, Alvaro a-m wrote:
> HI everyone,
> 
> My name is Álvaro. I'm texting you this email about LUKS. I have a USB
> with 3 partitions (/efi, /boot and /data with LVMs encrypted by LUKS).
> I have a problem entering the password as I don't have a keyboard and
> I need to enter the password with a touch screen. I tried to search
> for information about that but nothing was successful.
> 
> Do you know any solution for this? Can I enable the touch screen
> before LUKS gets up?
> Thank you, have a nice day.
> 
> Kind regards,
> Álvaro
> 
> El mié, 28 jun 2023 a las 10:45, Alvaro a-m (<alvaroam007@gmail.com>) escribió:
>>
>> HI everyone,
>>
>> My name is Álvaro. I'm texting you this email about LUKS. I have a USB
>> with 3 partitions (/efi, /boot and /data with LVMs encrypted by LUKS).
>> I have a problem entering the password as I don't have a keyboard and
>> I need to enter the password with a touch screen. I tried to search
>> for information about that but nothing was successful.
>>
>> Do you know any solution for this? Can I enable the touch screen
>> before LUKS gets up?
>> Thank you, have a nice day.
>>
>> Kind regards,
>> Álvaro
> 

Re: QUESTION

[Alvaro a-m]

HI everyone,

My name is Álvaro. I'm texting you this email about LUKS. I have a USB
with 3 partitions (/efi, /boot and /data with LVMs encrypted by LUKS).
I have a problem entering the password as I don't have a keyboard and
I need to enter the password with a touch screen. I tried to search
for information about that but nothing was successful.

Do you know any solution for this? Can I enable the touch screen
before LUKS gets up?
Thank you, have a nice day.

Kind regards,
Álvaro

El mié, 28 jun 2023 a las 10:45, Alvaro a-m (<alvaroam007@gmail.com>) escribió:
>
> HI everyone,
>
> My name is Álvaro. I'm texting you this email about LUKS. I have a USB
> with 3 partitions (/efi, /boot and /data with LVMs encrypted by LUKS).
> I have a problem entering the password as I don't have a keyboard and
> I need to enter the password with a touch screen. I tried to search
> for information about that but nothing was successful.
>
> Do you know any solution for this? Can I enable the touch screen
> before LUKS gets up?
> Thank you, have a nice day.
>
> Kind regards,
> Álvaro

QUESTION

[Alvaro a-m]

HI everyone,

My name is Álvaro. I'm texting you this email about LUKS. I have a USB
with 3 partitions (/efi, /boot and /data with LVMs encrypted by LUKS).
I have a problem entering the password as I don't have a keyboard and
I need to enter the password with a touch screen. I tried to search
for information about that but nothing was successful.

Do you know any solution for this? Can I enable the touch screen
before LUKS gets up?
Thank you, have a nice day.

Kind regards,
Álvaro

Re: Question

[Karel Zak]

On Tue, Jun 22, 2021 at 01:17:56PM +0300, Андрей Петров wrote:
> Hi, i have a question about devname.c https://github.com/karelzak/util-linux/blob/master/libblkid/src/devname.c#L377
> 
> Why is there size is equal 110? Can't the device name be greater then 110?
> In linux https://github.com/torvalds/linux/blob/13311e74253fe64329390df80bed3f07314ddd61/include/linux/genhd.h#L27
> 
> DEVICE_NAME_LEN is defined as 32, wouldn't be better if you use this define
> in your program?

I have a better way how to fix it -- let's remove entire EVMS code from
the library. EVMS is dead project since year 2006.

 Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

Question

[Андрей Петров]

Hi, i have a question about devname.c 
https://github.com/karelzak/util-linux/blob/master/libblkid/src/devname.c#L377

Why is there size is equal 110? Can't the device name be greater then 110?
In linux 
https://github.com/torvalds/linux/blob/13311e74253fe64329390df80bed3f07314ddd61/include/linux/genhd.h#L27 

DEVICE_NAME_LEN is defined as 32, wouldn't be better if you use this 
define in your program?

RE: Question...

[Samuel P. Felton - GPT LLC]

[-- Attachment #1.1: Type: text/plain, Size: 3431 bytes --]

Bonjour, Bertrand,



Thank you for your reply. I am a newbie to Xen but I’ve used Bhyve, Vmware and MSFT Hyper-V before so I am somewhat familiar with how type-1 hypervisors work. Still. 🤔



I've enclosed:



  1.  The script I used to try to set up Dom0. It’s basically the script I found here: https://angryelectron.com/how-to-install-ubuntu-as-xen-dom0-and-domu/, except, slightly modified for AArch64/ARMv8 as close as I was able to determine it.
  2.  The grub.cfg file.



As I said, the serial port STDOUT goes dead so no logs. Please help me understand how to turn on logging so I can figure out what’s going on.







The machine I’m porting to is this one: https://www.gigabyte.com/tw/ARM-Server/R281-T94-rev-100#ov



It has 128G RAM and a total of 5TB of SAS and SSD disk. I’m booting off one of the SSDs.



It runs Ubuntu 20.04 LTS just fine; I even have a UEFI GOP driver for the AMD Radeon R9 GPU I plugged in. All of that works fine with Ubuntu.



Thanks in advance for any ideas

Rgds.,
~Sam

“Your best and wisest refuge from all troubles is in your science”
                          - Ada King, countess of Lovelace



-----Original Message-----
From: Bertrand Marquis <Bertrand.Marquis@arm.com>
Sent: Friday, May 1, 2020 2:52
To: Samuel P. Felton - GPT LLC <sam.felton@glacier-peak.net>
Cc: xen-devel@lists.xen.org
Subject: Re: Question...



Hi Samuel,



> On 1 May 2020, at 06:59, Samuel P. Felton - GPT LLC <sam.felton@glacier-peak.net<mailto:sam.felton@glacier-peak.net>> wrote:

>

> So, I’m trying to get a Xen Dom0 and DomU, both running Ubuntu 20.04 LTS up on our brand-new Gigabyte ThunderX2 ARM64 box. I can get Ubuntu up and running, but after installing the Xen bits, it dies after the UEFI layer launches GRUB. I haven’t been able to get any logfiles because it doesn’t get that far. Nothing shows up on the serial port log either – it just hangs.

>

> Has anyone over there been trying to get a similar setup running? Am I out to lunch for trying this, or is there something I’m missing? Any help at all would be appreciated.



I am currently porting Xen on an N1SDP arm board which is also using a EDK2/grub setup and I manage to start xen from grub and then start dom0 providing a DTB.



My grub configuration looks like this:

menuentry 'xen' {

    xen_hypervisor $prefix/xen.efi loglvl=all guest_loglvl=all console=dtuart dtuart=serial0 dom0_mem=1G

    xen_module $prefix/Image console=hvc0 efi=noruntime rw root=/dev/sda1 rootwait

    devicetree $prefix/n1sdp.dtb

}



Could you share your grub configuration ?



Bertrand



>

> If this doesn’t work, I’m going to have to go to FreeBSD and Bhyve because I know someone who has that working. I’d rather use Linux than BSD for this application, there are more drivers supporting this hardaware.

>

> Thanks,

> ~Sam

>

>

>

>

> <image001.png>

> Phone: +1 206 701-7321 ext. 101

> Email: info@glacier-peak.net<mailto:info@glacier-peak.net>



IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #1.2: Type: text/html, Size: 11157 bytes --]

[-- Attachment #2: Xen_Ubuntu_Dom0.bsh --]
[-- Type: application/octet-stream, Size: 812 bytes --]

#!/bin/bash
# Setup and configure Xen DomU
# Run as root/sudo on a fresh Ubuntu Server 12.04 LTS install.  Reboot when complete.

# Update
apt-get update
apt-get upgrade

# Install Xen hypervisor
apt-get install xen-hypervisor-4.11-arm64
sed -i 's/GRUB_DEFAULT=.*\+/GRUB_DEFAULT="Xen 4.11-arm64"/' /etc/default/grub
sed -i 's/TOOLSTACK=.*\+/TOOLSTACK="xm"/' /etc/default/xen

# Setup bridge network interface
cat >> /etc/network/interfaces << EOL
  
#Xen Bridge
auto xenbr0
iface xenbr0 inet dhcp
  bridge_ports eth0
EOL

# Limit Dom0 memory to 512M
echo 'GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=512M"' >> /etc/default/grub
update-grub

#Allow VNC connections from anywhere
sed -i "s/#(vnc-listen.*/(vnc-listen \'0.0.0.0\')/" /etc/xen/xend-config.sxp

#Fix keymap issue
ln -s /usr/share/qemu-linaro/ /usr/share/qemu/

Re: Question...

[Julien Grall]

Hi,

On 01/05/2020 10:52, Bertrand Marquis wrote:
> Hi Samuel,
> 
>> On 1 May 2020, at 06:59, Samuel P. Felton - GPT LLC <sam.felton@glacier-peak.net> wrote:
>>
>> So, I’m trying to get a Xen Dom0 and DomU, both running Ubuntu 20.04 LTS up on our brand-new Gigabyte ThunderX2 ARM64 box. I can get Ubuntu up and running, but after installing the Xen bits, it dies after the UEFI layer launches GRUB. I haven’t been able to get any logfiles because it doesn’t get that far. Nothing shows up on the serial port log either – it just hangs.

IIUC what you wrote, you don't see any prompt from GRUB. Am I correct?

>>
>> Has anyone over there been trying to get a similar setup running? Am I out to lunch for trying this, or is there something I’m missing? Any help at all would be appreciated.
> 
> I am currently porting Xen on an N1SDP arm board which is also using a EDK2/grub setup and I manage to start xen from grub and then start dom0 providing a DTB.
> 
> My grub configuration looks like this:
> menuentry 'xen' {
>      xen_hypervisor $prefix/xen.efi loglvl=all guest_loglvl=all console=dtuart dtuart=serial0 dom0_mem=1G
>      xen_module $prefix/Image console=hvc0 efi=noruntime rw root=/dev/sda1 rootwait
>      devicetree $prefix/n1sdp.dtb
> }

Depending on your GRUB configuration, this may not work. For older GRUB, 
you will want to use chainloading (see [1]).

I haven't used Thunder-X 2 yet, only the previous version. Both version 
are shipped with ACPI and is the preferred way to boot. You should be 
able to boot Xen using ACPI, but it is not yet in feature parity with DT.

So I would recommend to use DT if Thunder-X 2 provide one. If you still 
want to have a try with ACPI, then you will need to build Xen with 
CONFIG_ACPI=y.

Additionally, Thunder-X 2 is using GICv3 ITS. You will need to build Xen 
with CONFIG_GICV3_ITS=y.

Both options can only be selectable when using the expert mode. In order 
to access it you have to add XEN_CONFIG_EXPERT=y on *all* your make 
command line.

I hope this helps.

> 
> Could you share your grub configuration ?
> 
> Bertrand
> 
>>
>> If this doesn’t work, I’m going to have to go to FreeBSD and Bhyve because I know someone who has that working. I’d rather use Linux than BSD for this application, there are more drivers supporting this hardaware.
>>
>> Thanks,
>> ~Sam


[1] https://wiki.xenproject.org/wiki/Xen_EFI

-- 
Julien Grall

Re: Question...

[Bertrand Marquis]

[-- Attachment #1: Type: text/plain, Size: 2065 bytes --]



On 1 May 2020, at 10:52, Bertrand Marquis <bertrand.marquis@arm.com<mailto:bertrand.marquis@arm.com>> wrote:

Hi Samuel,

On 1 May 2020, at 06:59, Samuel P. Felton - GPT LLC <sam.felton@glacier-peak.net<mailto:sam.felton@glacier-peak.net>> wrote:

So, I’m trying to get a Xen Dom0 and DomU, both running Ubuntu 20.04 LTS up on our brand-new Gigabyte ThunderX2 ARM64 box. I can get Ubuntu up and running, but after installing the Xen bits, it dies after the UEFI layer launches GRUB. I haven’t been able to get any logfiles because it doesn’t get that far. Nothing shows up on the serial port log either – it just hangs.

Has anyone over there been trying to get a similar setup running? Am I out to lunch for trying this, or is there something I’m missing? Any help at all would be appreciated.

I am currently porting Xen on an N1SDP arm board which is also using a EDK2/grub setup and I manage to start xen from grub and then start dom0 providing a DTB.

My grub configuration looks like this:
menuentry 'xen' {
   xen_hypervisor $prefix/xen.efi loglvl=all guest_loglvl=all console=dtuart dtuart=serial0 dom0_mem=1G
   xen_module $prefix/Image console=hvc0 efi=noruntime rw root=/dev/sda1 rootwait
   devicetree $prefix/n1sdp.dtb
}

Could you share your grub configuration ?

Bertrand


If this doesn’t work, I’m going to have to go to FreeBSD and Bhyve because I know someone who has that working. I’d rather use Linux than BSD for this application, there are more drivers supporting this hardaware.

Thanks,
~Sam




<image001.png>
Phone: +1 206 701-7321 ext. 101
Email: info@glacier-peak.net<mailto:info@glacier-peak.net>

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

Sorry, I forgot to remove the disclaimer.
Bertrand


[-- Attachment #2: Type: text/html, Size: 13655 bytes --]

Re: Question...

[Bertrand Marquis]

Hi Samuel,

> On 1 May 2020, at 06:59, Samuel P. Felton - GPT LLC <sam.felton@glacier-peak.net> wrote:
>
> So, I’m trying to get a Xen Dom0 and DomU, both running Ubuntu 20.04 LTS up on our brand-new Gigabyte ThunderX2 ARM64 box. I can get Ubuntu up and running, but after installing the Xen bits, it dies after the UEFI layer launches GRUB. I haven’t been able to get any logfiles because it doesn’t get that far. Nothing shows up on the serial port log either – it just hangs.
>
> Has anyone over there been trying to get a similar setup running? Am I out to lunch for trying this, or is there something I’m missing? Any help at all would be appreciated.

I am currently porting Xen on an N1SDP arm board which is also using a EDK2/grub setup and I manage to start xen from grub and then start dom0 providing a DTB.

My grub configuration looks like this:
menuentry 'xen' {
    xen_hypervisor $prefix/xen.efi loglvl=all guest_loglvl=all console=dtuart dtuart=serial0 dom0_mem=1G
    xen_module $prefix/Image console=hvc0 efi=noruntime rw root=/dev/sda1 rootwait
    devicetree $prefix/n1sdp.dtb
}

Could you share your grub configuration ?

Bertrand

>
> If this doesn’t work, I’m going to have to go to FreeBSD and Bhyve because I know someone who has that working. I’d rather use Linux than BSD for this application, there are more drivers supporting this hardaware.
>
> Thanks,
> ~Sam
>
>
>
>
> <image001.png>
> Phone: +1 206 701-7321 ext. 101
> Email: info@glacier-peak.net

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

Question...

[Samuel P. Felton - GPT LLC]

[-- Attachment #1.1: Type: text/plain, Size: 967 bytes --]

So, I'm trying to get a Xen Dom0 and DomU, both running Ubuntu 20.04 LTS up on our brand-new Gigabyte ThunderX2 ARM64 box. I can get Ubuntu up and running, but after installing the Xen bits, it dies after the UEFI layer launches GRUB. I haven't been able to get any logfiles because it doesn't get that far. Nothing shows up on the serial port log either - it just hangs.

Has anyone over there been trying to get a similar setup running? Am I out to lunch for trying this, or is there something I'm missing? Any help at all would be appreciated.

If this doesn't work, I'm going to have to go to FreeBSD and Bhyve because I know someone who has that working. I'd rather use Linux than BSD for this application, there are more drivers supporting this hardaware.

Thanks,
~Sam




[cid:image001.png@01D61F42.F8BC9760]
Phone: +1 206 701-7321 ext. 101
Email: info@glacier-peak.net<mailto:info@glacier-peak.net?subject=Tell%20me%20about%20Evolucid(r)>



[-- Attachment #1.2: Type: text/html, Size: 4105 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 45509 bytes --]

Re: Question

[Sarah Newman]

On 2/7/20 3:21 PM, o1bigtenor wrote:
> On Fri, Feb 7, 2020 at 4:50 PM Sarah Newman <srn@prgmr.com> wrote:
>>
>> On 2/7/20 7:49 AM, o1bigtenor wrote:
>>> Greetings
>>>
>>> Running a Raid-10 array made up of 4 - 1 TB drives on a debian testing
>>> (11) system.
>>> mdadm - v4.1 - 2018-10-01 is the version being used.
>>>
>>> Some weirdness is happening - - - vis a vis - - - I have one directory
>>> (not small) that has disappeared. I last accessed said directory
>>> (still have the pdf open which is how I could get this information)
>>> 'Last accessed 2020-01-19 6:32 A.M.'  as indicated in the 'Properties'
>>> section of the file in question.
>>
> 
> Greetings
> 
> 
>> I assume you've looked at lsof?
> 
> No I hadn't - - - - thanks for the tip.
> only a few thousand line in a terminal - - - - - but nothing what I was
> looking for.
>>
>> https://www.linux.com/news/bring-back-deleted-files-lsof/
>>
>> If it is a software problem, it just as likely, if not more likely, that it is a file system problem rather than a raid problem. You don't mention
>> what file system. You're possibly also actually looking at data in the in-memory disk cache rather than what's actually stored on disk given there's
>> been no reboot.
> 
> The array (raid-10) is on ext4.
>>
>> Is there anything suspicious in dmesg?
> 
> I hadn't looked at the messages files in /var/log so I went back to
> date in question.
> Didn't see anything there either.

I said the command dmesg, not /var/log.

If systemd-journald is broken, or your file system is broken, you could have tons of error messages in dmesg and nothing logged to disk.

> 
> What about doing this:
> 
> Made the array read only.
> Copy the whole array using dd to a larger array on a different machine
> (good overnight job).
> Then run something like testdisk on the whole array.
> The last would largely be a waste of time as what has
> disappeared is one of about 40 upper level directories  and
> it likely contained about 10 to 50 GB of files (dunno how many
> levels of directories though - - - I use LOTS).
> 
> I'm looking for a reasonably solid method of trying to recover
> this directory and all of its contents (about 8 years worth of
> putting things into it so replicating it - - - - tough!).

Making the original data read-only and operating on a copy of it is a reasonable idea.

You probably want http://extundelete.sourceforge.net/ though I would first try

find / -name "somefileyouknowthenameof"

just to make sure it hasn't been moved elsewhere on accident. That seems like the most likely scenario given the lack of error messages, unless no 
messages at all have been logged due to previously mentioned issues.

--Sarah

Re: Question

[o1bigtenor]

On Fri, Feb 7, 2020 at 4:50 PM Sarah Newman <srn@prgmr.com> wrote:
>
> On 2/7/20 7:49 AM, o1bigtenor wrote:
> > Greetings
> >
> > Running a Raid-10 array made up of 4 - 1 TB drives on a debian testing
> > (11) system.
> > mdadm - v4.1 - 2018-10-01 is the version being used.
> >
> > Some weirdness is happening - - - vis a vis - - - I have one directory
> > (not small) that has disappeared. I last accessed said directory
> > (still have the pdf open which is how I could get this information)
> > 'Last accessed 2020-01-19 6:32 A.M.'  as indicated in the 'Properties'
> > section of the file in question.
>

Greetings


> I assume you've looked at lsof?

No I hadn't - - - - thanks for the tip.
only a few thousand line in a terminal - - - - - but nothing what I was
looking for.
>
> https://www.linux.com/news/bring-back-deleted-files-lsof/
>
> If it is a software problem, it just as likely, if not more likely, that it is a file system problem rather than a raid problem. You don't mention
> what file system. You're possibly also actually looking at data in the in-memory disk cache rather than what's actually stored on disk given there's
> been no reboot.

The array (raid-10) is on ext4.
>
> Is there anything suspicious in dmesg?

I hadn't looked at the messages files in /var/log so I went back to
date in question.
Didn't see anything there either.

What about doing this:

Made the array read only.
Copy the whole array using dd to a larger array on a different machine
(good overnight job).
Then run something like testdisk on the whole array.
The last would largely be a waste of time as what has
disappeared is one of about 40 upper level directories  and
it likely contained about 10 to 50 GB of files (dunno how many
levels of directories though - - - I use LOTS).

I'm looking for a reasonably solid method of trying to recover
this directory and all of its contents (about 8 years worth of
putting things into it so replicating it - - - - tough!).

Thanks for the assistance!

Re: Question

[Sarah Newman]

On 2/7/20 7:49 AM, o1bigtenor wrote:
> Greetings
> 
> Running a Raid-10 array made up of 4 - 1 TB drives on a debian testing
> (11) system.
> mdadm - v4.1 - 2018-10-01 is the version being used.
> 
> Some weirdness is happening - - - vis a vis - - - I have one directory
> (not small) that has disappeared. I last accessed said directory
> (still have the pdf open which is how I could get this information)
> 'Last accessed 2020-01-19 6:32 A.M.'  as indicated in the 'Properties'
> section of the file in question.

I assume you've looked at lsof?

https://www.linux.com/news/bring-back-deleted-files-lsof/

If it is a software problem, it just as likely, if not more likely, that it is a file system problem rather than a raid problem. You don't mention 
what file system. You're possibly also actually looking at data in the in-memory disk cache rather than what's actually stored on disk given there's 
been no reboot.

Is there anything suspicious in dmesg?

Re: Question

[Wols Lists]

On 07/02/20 17:30, Reindl Harald wrote:
> 
> 
> Am 07.02.20 um 17:26 schrieb o1bigtenor:
>> On Fri, Feb 7, 2020 at 9:53 AM Reindl Harald <h.reindl@thelounge.net> wrote:
>>>
>>> Am 07.02.20 um 16:49 schrieb o1bigtenor:
>>>> Running a Raid-10 array made up of 4 - 1 TB drives on a debian testing
>>>> (11) system.
>>>> mdadm - v4.1 - 2018-10-01 is the version being used.
>>>>
>>>> Some weirdness is happening - - - vis a vis - - - I have one directory
>>>> (not small) that has disappeared. I last accessed said directory
>>>> (still have the pdf open which is how I could get this information)
>>>> 'Last accessed 2020-01-19 6:32 A.M.'  as indicated in the 'Properties'
>>>> section of the file in question.
>>>>
>>>> Has been suggested to me that I make the array read only until this is resolved.
>>>> I have space on the the array on a different system to recover this array.
>>>> Suggestions on how to do both of the above would be aprreciated
>>>
>>> directories on a filesystem on top of a RAID don't disappear silently -
>>> my bet is a simple drag&drop move or deletion aka PEBCAK
>>
>> I checked with bash - - history  and in about 500 items there is no mention of
>> such. Looked in log files and can't find anything either. Quite
>> puzzling - - - -
>> that's why I'm asking here.
>>
>> And yes - - - I am aware that all too often I'm the problem. I've
>> gotten a lot more
>> careful that I was even 5 years ago - - - grin.
> 
> if you shave no system error showing any evidence you are wrong here -
> even if it would be true witout any errors message you are wrong here
> because it's the same as asking if your neighbours dog pissed on your wall

You're rather dogmatic here ... I agree if you're not getting any system
error then it's unlikely to be the system. Though I would ask has the OP
run a check on the array itself - if raid thinks the array is good then
it probably is.
> 
> even with a filesystem error you are wrong here and it's impossible that
> the raid forget about exactly one folder because that layer don't now
> about folders and the FS would puke if a complete area desiapperas at
> running fsck - period
> 
And here you are TOO dogmatic. Ever heard of file corruption where PART
of a file gets corrupted? And it's nothing to do with the disk. The
entry for the directory could easily have got damaged.

And I've had the exact same thing seem to happen where PEBKAC is highly
unlikely - unless pebkac can magically acquire root permissions on a
system where I almost never do things as root ... and like it seems the
OP, drag and drop is very unlikely also as I rarely have a file manager
running.

So yes, I know exactly where the OP is coming from, and I'm just as
confused as to what's going on, especially as I deliberately change
permissions on stuff that's meant to be write-once to make sure that it
*IS* write-once.

Cheers,
Wol

Re: Question

[o1bigtenor]

On Fri, Feb 7, 2020 at 11:30 AM Reindl Harald <h.reindl@thelounge.net> wrote:
>
>
>
> Am 07.02.20 um 17:26 schrieb o1bigtenor:
> > On Fri, Feb 7, 2020 at 9:53 AM Reindl Harald <h.reindl@thelounge.net> wrote:
> >>
> >> Am 07.02.20 um 16:49 schrieb o1bigtenor:
> >>> Running a Raid-10 array made up of 4 - 1 TB drives on a debian testing
> >>> (11) system.
> >>> mdadm - v4.1 - 2018-10-01 is the version being used.
> >>>
> >>> Some weirdness is happening - - - vis a vis - - - I have one directory
> >>> (not small) that has disappeared. I last accessed said directory
> >>> (still have the pdf open which is how I could get this information)
> >>> 'Last accessed 2020-01-19 6:32 A.M.'  as indicated in the 'Properties'
> >>> section of the file in question.
> >>>
> >>> Has been suggested to me that I make the array read only until this is resolved.
> >>> I have space on the the array on a different system to recover this array.
> >>> Suggestions on how to do both of the above would be aprreciated
> >>
> >> directories on a filesystem on top of a RAID don't disappear silently -
> >> my bet is a simple drag&drop move or deletion aka PEBCAK
> >
> > I checked with bash - - history  and in about 500 items there is no mention of
> > such. Looked in log files and can't find anything either. Quite
> > puzzling - - - -
> > that's why I'm asking here.
> >
> > And yes - - - I am aware that all too often I'm the problem. I've
> > gotten a lot more
> > careful that I was even 5 years ago - - - grin.
>
> if you shave no system error showing any evidence you are wrong here -
> even if it would be true witout any errors message you are wrong here
> because it's the same as asking if your neighbours dog pissed on your wall
>
> even with a filesystem error you are wrong here and it's impossible that
> the raid forget about exactly one folder because that layer don't now
> about folders and the FS would puke if a complete area desiapperas at
> running fsck - period

I understand that this is a highly unusual occurrence.

That's why I'm asking here.

Regards

Re: Question

[Reindl Harald]

Am 07.02.20 um 17:26 schrieb o1bigtenor:
> On Fri, Feb 7, 2020 at 9:53 AM Reindl Harald <h.reindl@thelounge.net> wrote:
>>
>> Am 07.02.20 um 16:49 schrieb o1bigtenor:
>>> Running a Raid-10 array made up of 4 - 1 TB drives on a debian testing
>>> (11) system.
>>> mdadm - v4.1 - 2018-10-01 is the version being used.
>>>
>>> Some weirdness is happening - - - vis a vis - - - I have one directory
>>> (not small) that has disappeared. I last accessed said directory
>>> (still have the pdf open which is how I could get this information)
>>> 'Last accessed 2020-01-19 6:32 A.M.'  as indicated in the 'Properties'
>>> section of the file in question.
>>>
>>> Has been suggested to me that I make the array read only until this is resolved.
>>> I have space on the the array on a different system to recover this array.
>>> Suggestions on how to do both of the above would be aprreciated
>>
>> directories on a filesystem on top of a RAID don't disappear silently -
>> my bet is a simple drag&drop move or deletion aka PEBCAK
> 
> I checked with bash - - history  and in about 500 items there is no mention of
> such. Looked in log files and can't find anything either. Quite
> puzzling - - - -
> that's why I'm asking here.
> 
> And yes - - - I am aware that all too often I'm the problem. I've
> gotten a lot more
> careful that I was even 5 years ago - - - grin.

if you shave no system error showing any evidence you are wrong here -
even if it would be true witout any errors message you are wrong here
because it's the same as asking if your neighbours dog pissed on your wall

even with a filesystem error you are wrong here and it's impossible that
the raid forget about exactly one folder because that layer don't now
about folders and the FS would puke if a complete area desiapperas at
running fsck - period

Re: Question

[o1bigtenor]

On Fri, Feb 7, 2020 at 9:53 AM Reindl Harald <h.reindl@thelounge.net> wrote:
>
>
>
> Am 07.02.20 um 16:49 schrieb o1bigtenor:
> > Running a Raid-10 array made up of 4 - 1 TB drives on a debian testing
> > (11) system.
> > mdadm - v4.1 - 2018-10-01 is the version being used.
> >
> > Some weirdness is happening - - - vis a vis - - - I have one directory
> > (not small) that has disappeared. I last accessed said directory
> > (still have the pdf open which is how I could get this information)
> > 'Last accessed 2020-01-19 6:32 A.M.'  as indicated in the 'Properties'
> > section of the file in question.
> >
> > Has been suggested to me that I make the array read only until this is resolved.
> > I have space on the the array on a different system to recover this array.
> > Suggestions on how to do both of the above would be aprreciated
>
> directories on a filesystem on top of a RAID don't disappear silently -
> my bet is a simple drag&drop move or deletion aka PEBCAK

I checked with bash - - history  and in about 500 items there is no mention of
such. Looked in log files and can't find anything either. Quite
puzzling - - - -
that's why I'm asking here.

And yes - - - I am aware that all too often I'm the problem. I've
gotten a lot more
careful that I was even 5 years ago - - - grin.

Thanks

Re: Question

[Reindl Harald]

Am 07.02.20 um 16:49 schrieb o1bigtenor:
> Running a Raid-10 array made up of 4 - 1 TB drives on a debian testing
> (11) system.
> mdadm - v4.1 - 2018-10-01 is the version being used.
> 
> Some weirdness is happening - - - vis a vis - - - I have one directory
> (not small) that has disappeared. I last accessed said directory
> (still have the pdf open which is how I could get this information)
> 'Last accessed 2020-01-19 6:32 A.M.'  as indicated in the 'Properties'
> section of the file in question.
> 
> Has been suggested to me that I make the array read only until this is resolved.
> I have space on the the array on a different system to recover this array.
> Suggestions on how to do both of the above would be aprreciated

directories on a filesystem on top of a RAID don't disappear silently -
my bet is a simple drag&drop move or deletion aka PEBCAK

Question

[o1bigtenor]

Greetings

Running a Raid-10 array made up of 4 - 1 TB drives on a debian testing
(11) system.
mdadm - v4.1 - 2018-10-01 is the version being used.

Some weirdness is happening - - - vis a vis - - - I have one directory
(not small) that has disappeared. I last accessed said directory
(still have the pdf open which is how I could get this information)
'Last accessed 2020-01-19 6:32 A.M.'  as indicated in the 'Properties'
section of the file in question.

Has been suggested to me that I make the array read only until this is resolved.
I have space on the the array on a different system to recover this array.
Suggestions on how to do both of the above would be aprreciated

Checked the drives that make up the array using smartctl and the
results are (I removed text from each result that did not seem to have
any bearing on the test results (I likely used the wrong 'code')):

# smartctl -a /dev/sdb
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-2-amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD10EFRX-68FYTN0
Serial Number:    WD-WCC4J3TC25D3
LU WWN Device Id: 5 0014ee 20cd9cd93
Firmware Version: 82.00A82
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Feb  7 08:35:51 2020 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail
Always       -       0
  3 Spin_Up_Time            0x0027   132   130   021    Pre-fail
Always       -       4391
  4 Start_Stop_Count        0x0032   100   100   000    Old_age
Always       -       165
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail
Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age
Always       -       0
  9 Power_On_Hours          0x0032   058   058   000    Old_age
Always       -       31314
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age
Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age
Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age
Always       -       148
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age
Always       -       81
193 Load_Cycle_Count        0x0032   187   187   000    Old_age
Always       -       39644
194 Temperature_Celsius     0x0022   115   101   000    Old_age
Always       -       28
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age
Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age
Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age
Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age
Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age
Offline      -       0

SMART Error Log Version: 1
No Errors Logged

# smartctl -a /dev/sdc
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-2-amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD10EFRX-68FYTN0
Serial Number:    WD-WCC4J6TTLZTE
LU WWN Device Id: 5 0014ee 2b784490e
Firmware Version: 82.00A82
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Feb  7 08:36:49 2020 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail
Always       -       0
  3 Spin_Up_Time            0x0027   132   130   021    Pre-fail
Always       -       4375
  4 Start_Stop_Count        0x0032   100   100   000    Old_age
Always       -       151
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail
Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age
Always       -       0
  9 Power_On_Hours          0x0032   056   056   000    Old_age
Always       -       32529
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age
Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age
Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age
Always       -       149
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age
Always       -       80
193 Load_Cycle_Count        0x0032   187   187   000    Old_age
Always       -       39651
194 Temperature_Celsius     0x0022   115   099   000    Old_age
Always       -       28
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age
Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age
Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age
Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age
Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age
Offline      -       0

SMART Error Log Version: 1
No Errors Logged

# smartctl -a /dev/sde
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-2-amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD10EFRX-68FYTN0
Serial Number:    WD-WCC4J6XRY5AN
LU WWN Device Id: 5 0014ee 20cd940c6
Firmware Version: 82.00A82
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Feb  7 08:37:21 2020 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail
Always       -       0
  3 Spin_Up_Time            0x0027   131   129   021    Pre-fail
Always       -       4441
  4 Start_Stop_Count        0x0032   100   100   000    Old_age
Always       -       152
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail
Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age
Always       -       0
  9 Power_On_Hours          0x0032   056   056   000    Old_age
Always       -       32530
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age
Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age
Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age
Always       -       150
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age
Always       -       83
193 Load_Cycle_Count        0x0032   187   187   000    Old_age
Always       -       39603
194 Temperature_Celsius     0x0022   113   094   000    Old_age
Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age
Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age
Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age
Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age
Always       -       1
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age
Offline      -       0

SMART Error Log Version: 1
No Errors Logged

# smartctl -a /dev/sdf
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-2-amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD10EFRX-68FYTN0
Serial Number:    WD-WCC4J4XV62F4
LU WWN Device Id: 5 0014ee 20cd9d7d1
Firmware Version: 82.00A82
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Feb  7 08:37:44 2020 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail
Always       -       8
  3 Spin_Up_Time            0x0027   135   134   021    Pre-fail
Always       -       4241
  4 Start_Stop_Count        0x0032   100   100   000    Old_age
Always       -       165
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail
Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age
Always       -       0
  9 Power_On_Hours          0x0032   059   059   000    Old_age
Always       -       30121
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age
Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age
Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age
Always       -       148
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age
Always       -       82
193 Load_Cycle_Count        0x0032   187   187   000    Old_age
Always       -       39528
194 Temperature_Celsius     0x0022   115   097   000    Old_age
Always       -       28
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age
Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age
Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age
Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age
Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age
Offline      -       0

question

[Shahin Ansari]

[-- Attachment #1: Type: text/plain, Size: 222 bytes --]

I have a question about hardware assisted encryption, and hash module for
the user space. I believe it is called qcedev. Would this be an appropriate
group to discuss this? I want to know how hash function behaves please.

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 4454 bytes --]

Question

[TAE HO MOON]

[-- Attachment #1.1: Type: text/plain, Size: 595 bytes --]

Hi there, it's my first question on Xen-devel email list.
I am glad to join here.

Could anybody guide me to some pointers on interrupt delivery procedure for
PV?
I tried to understand the way Xen delivers the interrupt by using xentrace.
I followed *do_IRQ* function but I am lost.

I want to know how Xen delivers the interrupt to Dom0 and Dom0 to DomU.

Thanks

-- 
In his heart a man plans his course, but the LORD determines his steps.
Proverbs 16:9

Tae Ho Moon
Master of Engineering
Operating System Laboratory
Department of Convergence Software
Korea University

Cell : +82-10-3645-4189

[-- Attachment #1.2: Type: text/html, Size: 2023 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Question

[Johannes Schindelin]

Hi,

On 2015-08-11 10:28, Jet Rey Maza wrote:

> I'm wondering why gitbash dont have wget?

Please take the time to write coherent questions in the future, giving enough context for others to understand what you are talking about. We are not dogs that you throw some bones, you know? We are highly skilled software developers and you might want to express some respect for that by crafting a pleasant email.

As to your question, I have to guess here because you are so parsimonious with context: are you referring to Git for Windows' "Git Bash" entry in the start menu?

Assuming that this is what you meant, the explanation is simple: Git does not require wget to work. So we do not ship it with Git for Windows.

Side note: Git for Windows *does* ship with curl.exe, for historical reasons. You can probably use curl instead of wget for your use case.

Second side note: you obviously seek more than just Git for Windows, so why not use MSys2 (https://msys2.github.io/) which comes with a wget package you can install via pacman?

Ciao,
Johannes

Question

[Jet Rey Maza]

Hi,

I'm wondering why gitbash dont have wget?

question

[lilofile]

when I compile 3.10.36 kernel,after install,zhe system unable to boot, through serial debug,the system hang at setup_idt(); what the reason? how to debug and resolve ?

question

[lilofile]

I modify part of memeory manage subsystem, when i compile and install, linux 3.10.36 unable to boot,After skip grub menu,cursor occur  The upper left corner,the system hang and have no output,  how i can debug it? what the reason? Any suggestions will be welcome.


 

Re: question

[Hugo Mills]

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

On Sun, Oct 20, 2013 at 11:19:26PM +0800, lilofile wrote:
> 
> when i read transaction_kthread function in disk-io.c 
> 
> delay = HZ * 30;
> 
> why commit transaction is 30 seconds,  Other values 20 seconds,10 seconds?
> what considerations about the commit transaction interval?

   It's a more or less arbitrary number. There's been a patch recently
(last couple of months) to allow modifying the value. If you make it
too large, you end up using lots of RAM for unflushed changes, you
risk losing those changes if the machine crashes. If you make it too
small, you end up writing lots more metadata, because that's always
changing as the FS is modified.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
  --- There are three things you should never see being made: laws, ---  
                        standards,  and sausages.                        

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

question

[lilofile]

when i read transaction_kthread function in disk-io.c 

delay = HZ * 30;

why commit transaction is 30 seconds,  Other values 20 seconds,10 seconds?
what considerations about the commit transaction interval?

Re: question

[Matthew Khouzam]

[-- Attachment #1.1: Type: text/plain, Size: 873 bytes --]

Hi Emy,

I'm a bit confused by your question, are you trying to modify an
obsolete system call let's say you want to instrument old code, it
should be moderately staightforward with kprobe. Lttng can read the
kprobes after.

Lttng can read the probes like this
http://lwn.net/Articles/491510/
here's some more info on kprobes
https://www.kernel.org/doc/Documentation/kprobes.txt

Hope this helps.
Matt


On 13-07-10 05:51 PM, emy moore wrote:
> hi all
>
> i try to understand how a system call is implemented so i do some
> modification in an obsolete system call.
>
> i want to know can i trace this system call using lttng knowing that
> it's an obsolete one ? if no how can i activate it's trace ?
>
>
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


[-- Attachment #1.2: Type: text/html, Size: 2118 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

question

[emy moore]

[-- Attachment #1.1: Type: text/plain, Size: 246 bytes --]

hi all

i try to understand how a system call is implemented so i do some
modification in an obsolete system call.

i want to know can i trace this system call using lttng knowing that it's
an obsolete one ? if no how can i activate it's trace ?

[-- Attachment #1.2: Type: text/html, Size: 324 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: Question

[Mathieu Desnoyers]

* tarek slaymia (tarek.slaymia@gmail.com) wrote:
> Hi all ,
> 
> did lttng provides some information about direct kernel object manipulation
> ?
> if yes , how can i get these infos ?

I'm afraid I don't understand what you mean by "direct kernel object
manipulation". Can you clarify with an example ?

Thanks,

Mathieu

> 
> Thanks in advance .
> Regards.

> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com

Question

[tarek slaymia]

[-- Attachment #1.1: Type: text/plain, Size: 155 bytes --]

Hi all ,

did lttng provides some information about direct kernel object manipulation
?
if yes , how can i get these infos ?

Thanks in advance .
Regards.

[-- Attachment #1.2: Type: text/html, Size: 173 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Question

[tchak adim]

[-- Attachment #1.1: Type: text/plain, Size: 457 bytes --]

Hi all,

i'm using lttng 2.0 and i didn't find any documentation that talk about the
signification of  kernel event listed by "lttng lisk -k" .
I want to know how can i retrieve system metrics from kernel traces ? i
already find a document named "Recovering System Metrics from Kernel Trace"
but it seems that this document isn't up to date because i'm using LTTng
2.0. is there any updated document that depicts that part ?

Can you help me please ?

THX.

[-- Attachment #1.2: Type: text/html, Size: 523 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Question

[tchak adim]

[-- Attachment #1.1: Type: text/plain, Size: 394 bytes --]

Hi all,

i wanna know the signification of every kernel event on LTTng but i didn't
find any documentation that depicts that part.
also i want to know how can i retrieve system metrics from kernel traces ?
i already find a document named "Recovering System Metrics from Kernel
Trace" but it seems that this document isn't up to date because i'm using
LTTng 2.0.

Can you help me please ?

THX.

[-- Attachment #1.2: Type: text/html, Size: 444 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: Question

[Arbiel Perlacremaz]

Can you precise your point, as, to my understanding, Grub is able to 
boot from CDs. For instance, Ubuntu distributions are available on CDs 
and nobody complained until now they are not bootable.

Le 04/07/2012 03:04, Andy Canfield a écrit :
> I have a question. Bruce Dubbs said "Ask on the grub-devel site".
>
> I went to http://www.gnu.org/software/grub/grub-development.html and 
> read this:
>
>     Those interested in its development should subscribe to the
>     _developers' mailing list_. As this list is a members-only list,
>     please subscribe to it then send e-mail to this list.
>
> Maybe I must subscribe to "the developer's mailing list" in order to 
> be able to get an answer to my question. So I clicked on the link, and 
> what I got was a blank e-mail addressed to "grub-devel@gnu.org". So I 
> am asking. If I must subscribe to the mailing list to get the answer, 
> please sign me up.
>
> Here is the question:
>
> *Why can't grub boot from an standard bootable CD*?
>
> I have many such CD's, such as the Microsoft Windows 98 install CD. 
> Why can't grub boot from that? There must be a technical reason, but 
> nobody says what it is. Grub can boot from all kinds of hard disks, 
> and from diskettes; why not CD's?
>
> I started on an IBM 360/20 many decades ago. You dialed "0080" on the 
> CPU and pressed the "LOAD" button. The CPU read the first card into 
> address 0x0080 and jumped to it. I still think of booting in terms of 
> "read it into memory and jump to it". Certainly grub should be able to 
> use the BIOS to read the CD into memory and jump to that memory image. 
> Why can the BIOS do that, but grub cannot?
>
> Thank you.
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel

Question

[Andy Canfield]

[-- Attachment #1: Type: text/html, Size: 1954 bytes --]

Question

[Francisco Manuel Cardoso]

[-- Attachment #1.1: Type: text/plain, Size: 707 bytes --]

Hello,

 

I know that mostly this list is used for development though I wanted to know
if there is any option to set values for thing as Gamma, Contrast and
Brightness on the driver or if there is any way they can be set ?

Will there ever be a Control Center like the Windows version ?

The question arises for a reason that alike some people I have a bit of a
problem with glossy screens and also with contrast levels and such.

Thought being a Linux System's Engineer for company it's odd not being able
to use Linux at work cause of the odd nuance. It's even more "odd" when
people see me using Linux on a VMware so that I can get my contrast set from
Windows J

 

Thanks for any reply

 

Francisco


[-- Attachment #1.2: Type: text/html, Size: 3695 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: Question

[Paul Lagasse]

You can do this pretty easily by specifying an application-launching 
command or batch file when launching Dosemu. For example, the command 
"dosemu edit" will immediately launch FreeDos Edit once Dosemu starts. 
If wp.bat launches Word Perfect, for example, then the command "dosemu 
wp" should get you up and running in Word Perfect. Etc. You don't need 
multiple copies of Dosemu to start multiple sessions of Dosemu.

On 02/22/2012 02:20 PM, John Vulchev wrote:
> Is there a way for me to have multiple copies of DOSEMU so that I can 
> have a separate unique icons to directly launch different 
> applications, as opposed to typing the executable name once the DOSEMU 
> window opens?  I would appreciate any help with this.
>
> Best Regards:
>
>
> John Vulchev
> High Temp Metals, Inc
> 12910 San Fernando Road
> Sylmar, CA 91342 USA
> PHN (818) 362-5357
> PHN (800) 500-2141
> FAX (818) 362-9884
> john@hightempmetals.com
>
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: Question

[Frank Cox]

You could probably script it, depending on what your exact needs are.

On Wed, 22 Feb 2012 11:20:56 -0800
John Vulchev wrote:

> Is there a way for me to have multiple copies of DOSEMU so that I can 
> have a separate unique icons to directly launch different applications, 
> as opposed to typing the executable name once the DOSEMU window opens?  
> I would appreciate any help with this.
> 
> Best Regards:
> 
> 
> John Vulchev
> High Temp Metals, Inc
> 12910 San Fernando Road
> Sylmar, CA 91342 USA
> PHN (818) 362-5357
> PHN (800) 500-2141
> FAX (818) 362-9884
> john@hightempmetals.com
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
www.creekfm.com - FIFTY THOUSAND WATTS of POW WOW POWER!

Question

[John Vulchev]

Is there a way for me to have multiple copies of DOSEMU so that I can 
have a separate unique icons to directly launch different applications, 
as opposed to typing the executable name once the DOSEMU window opens?  
I would appreciate any help with this.

Best Regards:


John Vulchev
High Temp Metals, Inc
12910 San Fernando Road
Sylmar, CA 91342 USA
PHN (818) 362-5357
PHN (800) 500-2141
FAX (818) 362-9884
john@hightempmetals.com

Question

[Miran Merljak]

[-- Attachment #1.1: Type: text/plain, Size: 281 bytes --]

Hello!

Can you give me some info on the development status of h.264 hardware
decoding support on the Intel G/GM45 platform in linux drivers? Is any
effort being done in including this feature in the upcomig drivers and when
(if) we can expect this to get implemented.

Thank you!

[-- Attachment #1.2: Type: text/html, Size: 522 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

question

[Steven]

Dear All:
I have a question about exporting some information to VMM. For
example, I would lile to let the VMM have the information of the
number of running processes in one guest domain. I know that this
information can be obtained by the per_CPU runqueue in each guest. But
how to copy this number to xen VMM? Should I use shared memory? Thanks
in advance.


- Steven

Re: question

[Alexey Klimov]

Hello, Juan

On Mon, Apr 6, 2009 at 7:07 PM, Juan Diego <juantascon@gmail.com> wrote:
> Hi, my name is Juan Diego
>
> I would like to make some tests using some v4l applications and I
> would like to know if there is a way to create a "virtual° v4l device
> using a video file to act as a camera
>
> thanks for your help
> bye

Well, i don't sure if i understand you correctly..
Vasily Levin (mail: vasaka at gmail.com) posted V4L2 loopback device
code in maillist to review. I don't know if his code was merged.
Probably this site can help you:
http://code.google.com/p/v4l2loopback/

The patch is here http://www.spinics.net/lists/linux-media/msg03630.html
Anyway, you can contact him by e-mail.

-- 
Best regards, Klimov Alexey

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

question

[Juan Diego]

Hi, my name is Juan Diego

I would like to make some tests using some v4l applications and I
would like to know if there is a way to create a "virtual° v4l device
using a video file to act as a camera

thanks for your help
bye

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Question...

[Eric Sandeen]

Ezzat, Ahmed wrote:
>  
> Hello,
>  
> Does XFS comes up as part of Red Hat Linux Enterprise 5 from HP? 

Not today, sorry.

> How to
> find out (any specific commands that I can issue man page to see if a
> Linux instance support XFS or not?
>  
> Where I can find documentation (user guide and administrative guide) for
> XFS?
> Thanks,

XFS tutorial - http://oss.sgi.com/projects/xfs/training/index.html is a
start.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Question...

[Ezzat, Ahmed]

[-- Attachment #1.1: Type: text/plain, Size: 295 bytes --]


Hello,

Does XFS comes up as part of Red Hat Linux Enterprise 5 from HP? How to find out (any specific commands that I can issue man page to see if a Linux instance support XFS or not?

Where I can find documentation (user guide and administrative guide) for XFS?
Thanks,

Ahmed




[-- Attachment #1.2: Type: text/html, Size: 877 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Question

[Venefax]

Dear Gentlemen
Suppose you need to know the overall load on the host, in terms if CPU,
bandwidth and disk IO, not per domu, but aggregated, and split per domu and
dom0. Xentop does not show aggregated totals, and also it does not show
percentages relative to available resources, so for management is kind of
useless. The only tool that shows (somehow) that information is graphic, the
libvirt virtual machine manager, but is there a text mode tool to manage a
node?
Federico

Re: question

[Steve Grubb]

On Monday 03 November 2008 12:21:23 David Flatley wrote:
> I am actually using the suggested parameters from the STIG for UNIX
> guide. I have searched and found the stig.rules on the internet and we are
> going to try them. I also saw the nispom.rules but apparently they are
> for Red hat 5 Kernel 2.6.25 it says in the file?

Yes, those rules use some recent kernel functionality in order to cover all 
the requirements. Those recent kernel updates are in the RHEL5 kernels and 
should work. They will take some re-engineeing to get working on RHEL4.


> We are not using keying but will once we get the stig.rules installed
> they appear to be using the -k flag.

On RHEL4, you can only use keys on the file watches. RHEL5 you can use them on 
both syscall and file watches.


>     We are using audit 1.0.15 and I see 1.0.16 is on the Red Hat site, is
> there a compelling reason to update to the
> 1.0.16 version of audit?.

The change log

1.0.16
- Update time handling for ausearch and aureport to add more keywords
- Fix the ausearch on keyword to tolerate records with no key (#402941)
- num_logs option wasn't working right on shifts (#325561)
- In auditd, resume logging on SIGUSR2 (#325561)
- ausearch needed update for escaped acct fields (#353241)
- Fix parsing filterkeys in fs_watch records

So, this has some fixups for using keys.

-Steve

Re: question

[David Flatley]

[-- Attachment #1.1.1: Type: text/plain, Size: 1955 bytes --]



    I am actually using the suggested parameters from the STIG for UNIX
guide. I have searched and found
the stig.rules on the internet and we are going to try them. I also saw the
nispom.rules but apparently they are
for Red hat 5 Kernel 2.6.25 it says in the file?    We are not using keying
but will once we get the stig.rules installed
they appear to be using the -k flag.
    We are using audit 1.0.15 and I see 1.0.16 is on the Red Hat site, is
there a compelling reason to update to the
1.0.16 version of audit?.
     Thanks Steve.



                                                                       
                                                                       
                                                                       
                                                                       




On Sunday 02 November 2008 21:42:47 David Flatley wrote:
> Presently I am using the S.T.I.G. recommendations but I may
> have to use more extensive rules which I am in the process of testing.

Are you using the stig.rules from the audit package or something else? If I

were you, I'd spend some time making sure your rules are tuned. Assuming
that
you have keys on you rules, you can run a key report to see what is causing

you the most events: aureport --start this-week --key --summary.

Then you'd want to dig into some of those records and see what kinds of
things
are happening. Assuming you have a key of delete and you wanted to see what

syscalls are the most often logged:

ausearch --start this-week -k delete --raw | aureport --syscall --summary
-i

Assuming that shows unlinkat the most prevalent syscall:

ausearch --start this-week -k delete -sc unlinkat --raw |
aureport --user --summary -i

And so on until you see what is causing so much logging. This doesn't help
with the archiving, but could help you get the right audit data recorded.

-Steve

[-- Attachment #1.1.2: Type: text/html, Size: 2500 bytes --]

[-- Attachment #1.2: graycol.gif --]
[-- Type: image/gif, Size: 105 bytes --]

[-- Attachment #1.3: pic28634.gif --]
[-- Type: image/gif, Size: 1255 bytes --]

[-- Attachment #1.4: ecblank.gif --]
[-- Type: image/gif, Size: 45 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: question

[Steve Grubb]

On Sunday 02 November 2008 21:42:47 David Flatley wrote:
> Presently I am using the S.T.I.G. recommendations but I may
> have to use more extensive rules which I am in the process of testing.

Are you using the stig.rules from the audit package or something else? If I 
were you, I'd spend some time making sure your rules are tuned. Assuming that 
you have keys on you rules, you can run a key report to see what is causing 
you the most events: aureport --start this-week --key --summary. 

Then you'd want to dig into some of those records and see what kinds of things 
are happening. Assuming you have a key of delete and you wanted to see what 
syscalls are the most often logged:

ausearch --start this-week -k delete --raw | aureport --syscall --summary -i

Assuming that shows unlinkat the most prevalent syscall:

ausearch --start this-week -k delete -sc unlinkat --raw | 
aureport --user --summary -i

And so on until you see what is causing so much logging. This doesn't help 
with the archiving, but could help you get the right audit data recorded.

-Steve

Re: question

[David Flatley]

[-- Attachment #1.1.1: Type: text/plain, Size: 3071 bytes --]








On Fri, 2008-10-31 at 15:50 -0400, Steve Grubb wrote:
>> On Friday 31 October 2008 14:21:12 David Flatley wrote:
> ...
>
>> Perhaps we need the capability of switching out partitions used for
logging?
>> Maybe that could be solved by using the space left action exec
capability to
>> run a custom program that re-writes the audit config file or changes a
>> symlink to point to another config file to point to a new dir and then
sends
>> sighup to the parent (auditd).
>>
>> Maybe some others have ideas about how they solve the same problem. If
we need
>> to make changes to the audit daemon to make this smoother, let me know
what's
>> needed.

>David, I will have similar requirements and I've been thinking about
>this also. Not sure about you, but my audit data has the following
>requirements (and others):
>* archive to off-site storage
>* restore from archive
>* search capabilities (mostly covered in ausearch and audit-viewer)
>* robust (cannot lose any data received)
>* etc.
  Yes my requirements are very similar.

>Like you, I'm planning a periodic shift. This enables straightforward
>time-based restore/search for humans. Ideally, it would be totally
>automated, as in:

>1: shift auditing to a new R/W partition each month.
>2: Make the previous month audit data RO.
>3: archive the previous month to tape/DVD
>4: put the RO partition back into the "available" queue
>5: ensure the current audit is also mirrored over to a big storage area
>with all the past data on it.
>6: Send an email to the administrator that all the above has
>successfully occurred.

>Steve, as my testing progresses I'll add comments in this area. I had
>thought a cron-activated logrotate on the month would cover this, but it
>means 2 admin areas; if there is a way to do it inside the audit
>structure, that would be preferable to me. It would simplify/consolidate
>the config rpm(s) I create. Anything you could do to help facilitate a
>scheme as described above would be welcome.

>David, a couple of questions for you:
>* Have you looked at the audit-viewer, and do you intend to use this?
No, have not looked at it, really would like to use Tivoli compliance
insight manager.
>* I assume "heavy usage systems" means lots of audit data...are your
>rules tuned appropriately? This is critical for me - one over-zealous
>rule will add a flood of unhelpful info.
Yes I am in the process of evaluating rules, using S.T.I.G.
recommendations.

>* You mention "balancing performance"  - are you talking about
>per-machine or network (via aggregation)?
Yes per machine, network is not an issue.

>When reading your post I
>assumed aggregation from my own perspective but you didn't actually
>specify so I thought maybe I should ask. I'm aggregating all audit from
>several machines to a single audit machine for
>storage/review/administration. You?
I remove the logs daily per machine and store them per system.

>Thx,
>LCB.

--
LC (Lenny) Bruzenak
lenny@magitekltd.com

--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

[-- Attachment #1.1.2: Type: text/html, Size: 4043 bytes --]

[-- Attachment #1.2: graycol.gif --]
[-- Type: image/gif, Size: 105 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: question

[David Flatley]

[-- Attachment #1.1.1: Type: text/plain, Size: 2413 bytes --]

    Sorry I am in error on the storage question. I do have limited storage
on some of my systems and depending on my rules
and what is running on the systems this could cause an issue. Presently I
am using the S.T.I.G. recommendations but I may
have to use more extensive rules which I am in the process of testing.







Thanks for the reply Steve.

Inactive hide details for Steve Grubb <sgrubb@redhat.com>Steve Grubb
<sgrubb@redhat.com>


On Friday 31 October 2008 14:21:12 David Flatley wrote:
>     If you would indulge my simpler in comparison question of the group.
I
> am setting up audit on heavy usage systems. I have setup my auditd.conf
to
> rotate the files once they get to 70 meg and allow up to 12 rotated
files.

You don't need to limit the files to 12 unless you are short on disk space.

you can use keep_logs as the max_log_file option and one will not be lost.

Disk space is not a problem if the day's logging is collected and stored,
which is required,

> I created a cron that runs hourly to look and see if a ninth rotated file
> exists and if so run "ausearch -i" outputted to a file and store the
> file,

You shouldn't need to ausearch the file? Are you doing that to split the
file
on a time hack? In that case you can just about as easily do a "service
auditd rotate" and force auditd to end at a certain time rather than by
size.

Yes and then I could use ausearch -if <file> when I need to look at the
logs
after they have been moved to storage. Or apply the ausearch -i when I do
the
storage of the file, I do this to convert from numerical to text on the
file.

> then remove the rotated files. I run the cron to avoid losing data if
> there is alot of activity and rotated files are rolled off. I also have
to
> balance performance with auditing in this arrangement.

Perhaps we need the capability of switching out partitions used for
logging?
Maybe that could be solved by using the space left action exec capability
to
run a custom program that re-writes the audit config file or changes a
symlink to point to another config file to point to a new dir and then
sends
sighup to the parent (auditd).

Maybe some others have ideas about how they solve the same problem. If we
need
to make changes to the audit daemon to make this smoother, let me know
what's
needed.

-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

[-- Attachment #1.1.2: Type: text/html, Size: 3326 bytes --]

[-- Attachment #1.2: graycol.gif --]
[-- Type: image/gif, Size: 105 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: question

[LC Bruzenak]

On Fri, 2008-10-31 at 15:50 -0400, Steve Grubb wrote:
> On Friday 31 October 2008 14:21:12 David Flatley wrote:
> ...
> 
> Perhaps we need the capability of switching out partitions used for logging? 
> Maybe that could be solved by using the space left action exec capability to 
> run a custom program that re-writes the audit config file or changes a 
> symlink to point to another config file to point to a new dir and then sends 
> sighup to the parent (auditd).
> 
> Maybe some others have ideas about how they solve the same problem. If we need 
> to make changes to the audit daemon to make this smoother, let me know what's 
> needed.

David, I will have similar requirements and I've been thinking about
this also. Not sure about you, but my audit data has the following
requirements (and others):
* archive to off-site storage
* restore from archive
* search capabilities (mostly covered in ausearch and audit-viewer)
* robust (cannot lose any data received)
* etc.

Like you, I'm planning a periodic shift. This enables straightforward
time-based restore/search for humans. Ideally, it would be totally
automated, as in:

1: shift auditing to a new R/W partition each month.
2: Make the previous month audit data RO.
3: archive the previous month to tape/DVD
4: put the RO partition back into the "available" queue
5: ensure the current audit is also mirrored over to a big storage area
with all the past data on it.
6: Send an email to the administrator that all the above has
successfully occurred.

Steve, as my testing progresses I'll add comments in this area. I had
thought a cron-activated logrotate on the month would cover this, but it
means 2 admin areas; if there is a way to do it inside the audit
structure, that would be preferable to me. It would simplify/consolidate
the config rpm(s) I create. Anything you could do to help facilitate a
scheme as described above would be welcome.

David, a couple of questions for you:
* Have you looked at the audit-viewer, and do you intend to use this?
* I assume "heavy usage systems" means lots of audit data...are your
rules tuned appropriately? This is critical for me - one over-zealous
rule will add a flood of unhelpful info.
* You mention "balancing performance"  - are you talking about
per-machine or network (via aggregation)? When reading your post I
assumed aggregation from my own perspective but you didn't actually
specify so I thought maybe I should ask. I'm aggregating all audit from
several machines to a single audit machine for
storage/review/adminstration. You?

Thx,
LCB.

-- 
LC (Lenny) Bruzenak
lenny@magitekltd.com

Re: question

[David Flatley]

[-- Attachment #1.1.1: Type: text/plain, Size: 1905 bytes --]

    Thanks for the reply Steve.




On Friday 31 October 2008 14:21:12 David Flatley wrote:
>     If you would indulge my simpler in comparison question of the group.
I
> am setting up audit on heavy usage systems. I have setup my auditd.conf
to
> rotate the files once they get to 70 meg and allow up to 12 rotated
files.

You don't need to limit the files to 12 unless you are short on disk space.

you can use keep_logs as the max_log_file option and one will not be lost.

Disk space is not a problem if the day's logging is collected and stored,
which is required,

> I created a cron that runs hourly to look and see if a ninth rotated file
> exists and if so run "ausearch -i" outputted to a file and store the
> file,

You shouldn't need to ausearch the file? Are you doing that to split the
file
on a time hack? In that case you can just about as easily do a "service
auditd rotate" and force auditd to end at a certain time rather than by
size.

Yes and then I could use ausearch -if <file> when I need to look at the
logs
after they have been moved to storage. Or apply the ausearch -i when I do
the>
storage of the file, I do this to convert from numerical to text on the
file.

> then remove the rotated files. I run the cron to avoid losing data if
> there is alot of activity and rotated files are rolled off. I also have
to
> balance performance with auditing in this arrangement.

Perhaps we need the capability of switching out partitions used for
logging?
Maybe that could be solved by using the space left action exec capability
to
run a custom program that re-writes the audit config file or changes a
symlink to point to another config file to point to a new dir and then
sends
sighup to the parent (auditd).

Maybe some others have ideas about how they solve the same problem. If we
need
to make changes to the audit daemon to make this smoother, let me know
what's
needed.

-Steve

[-- Attachment #1.1.2: Type: text/html, Size: 2427 bytes --]

[-- Attachment #1.2: graycol.gif --]
[-- Type: image/gif, Size: 105 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: question

[Steve Grubb]

On Friday 31 October 2008 14:21:12 David Flatley wrote:
>     If you would indulge my simpler in comparison question of the group. I
> am setting up audit on heavy usage systems. I have setup my auditd.conf to
> rotate the files once they get to 70 meg and allow up to 12 rotated files.

You don't need to limit the files to 12 unless you are short on disk space. 
you can use keep_logs as the max_log_file option and one will not be lost.


> I created a cron that runs hourly to look and see if a ninth rotated file
> exists and if so run "ausearch -i" outputted to a file and store the
> file,

You shouldn't need to ausearch the file? Are you doing that to split the file 
on a time hack? In that case you can just about as easily do a "service 
auditd rotate" and force auditd to end at a certain time rather than by size.


> then remove the rotated files. I run the cron to avoid losing data if 
> there is alot of activity and rotated files are rolled off. I also have to
> balance performance with auditing in this arrangement.

Perhaps we need the capability of switching out partitions used for logging? 
Maybe that could be solved by using the space left action exec capability to 
run a custom program that re-writes the audit config file or changes a 
symlink to point to another config file to point to a new dir and then sends 
sighup to the parent (auditd).

Maybe some others have ideas about how they solve the same problem. If we need 
to make changes to the audit daemon to make this smoother, let me know what's 
needed.

-Steve

question

[David Flatley]

[-- Attachment #1.1: Type: text/plain, Size: 642 bytes --]


    If you would indulge my simpler in comparison question of the group. I
am setting up audit
on heavy usage systems. I have setup my auditd.conf to rotate the files
once they get to 70
meg and allow up to 12 rotated files. I created a cron that runs hourly to
look and see if
a ninth rotated file exists and if so run "ausearch -i" outputted to a file
and store the
file, then remove the rotated files. I run the cron to avoid losing data if
there is alot of activity
and rotated files are rolled off. I also have to balance performance with
auditing in this
arrangement.
   My question is: is there a better way to do this?
       Thanks.

[-- Attachment #1.2: Type: text/html, Size: 719 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Question

[Artjom]

No possible to load compat-wireless modules in Fedora 8. What to do?
What is the reason?
The same with kernel 2.6.26.2-2.fc8.
                                               Best regards.
                                                     Artjom.

[root@localhost compat-wireless-2008-08-06]# make load
Loading ipw2100...
Loading ipw2200...
Loading libertas_cs...
Loading usb8xxx...
Loading p54pci...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting p54common
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54common.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting p54pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading p54usb...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting p54common
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54common.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting p54usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading adm8211...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting adm8211
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/adm8211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading zd1211rw...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting zd1211rw
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/zd1211rw/zd1211rw.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8180...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8180
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8180.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8187...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8187
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8187.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading p54pci...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting p54common
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54common.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting p54pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading p54usb...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting p54common
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54common.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting p54usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading iwl3945...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting iwl3945
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/iwlwifi/iwl3945.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading iwl4965...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting iwlcore
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/iwlwifi/iwlcore.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting iwl4965
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/iwlwifi/iwl4965.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8180...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8180
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8180.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8187...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8187
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8187.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8180...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8180
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8180.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8187...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8187
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8187.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading rt2400pci...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00lib
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rt2400pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2400pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rt2500pci...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00lib
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rt2500pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2500pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rt61pci...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00lib
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rt61pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt61pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rt2500usb...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00lib
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rt2500usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2500usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rt73usb...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00lib
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rt73usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt73usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rndis_wlan...
Loading at76_usb...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting at76_usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/at76_usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Module ath_pci not detected -- this is fine
Enabling ath5k ...      [OK]    Module renamed but another module file
is being preferred
Renamed
module:         /lib/modules/2.6.25.14-69.fc8/kernel/drivers/net/wireless/ath5k/ath5k.ko
Preferred
module:       /lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/ath5k/ath5k.ko
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting ath5k
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/ath5k/ath5k.ko): Unknown symbol in module, or unknown parameter (see dmesg)
ath5k loaded successfully
Module bcm43xx not detected -- this is fine
Enabling b43 ...        [OK]    Module renamed but another module file
is being preferred
Renamed
module:         /lib/modules/2.6.25.14-69.fc8/kernel/drivers/net/wireless/b43/b43.ko
Preferred
module:       /lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43/b43.ko
Enabling b43legacy ...  [OK]    Module renamed but another module file
is being preferred
Renamed
module:         /lib/modules/2.6.25.14-69.fc8/kernel/drivers/net/wireless/b43legacy/b43legacy.ko
Preferred
module:       /lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43legacy/b43legacy.ko
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting b43
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43/b43.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting b43legacy
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43legacy/b43legacy.ko): Unknown symbol in module, or unknown parameter (see dmesg)
b43 loaded successfully
b43legacy loaded successfully

[root@localhost compat-wireless-2008-08-06]# dmesg -c
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8180: Unknown symbol ieee80211_free_hw
rtl8180: Unknown symbol ieee80211_alloc_hw
rtl8180: Unknown symbol ieee80211_register_hw
rtl8180: Unknown symbol ieee80211_wake_queue
rtl8180: Unknown symbol ieee80211_tx_status_irqsafe
rtl8180: Unknown symbol ieee80211_stop_queue
rtl8180: Unknown symbol ieee80211_unregister_hw
rtl8180: Unknown symbol ieee80211_frequency_to_channel
rtl8180: Unknown symbol ieee80211_rx_irqsafe
rtl8180: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8187: Unknown symbol ieee80211_free_hw
rtl8187: Unknown symbol ieee80211_alloc_hw
rtl8187: Unknown symbol ieee80211_register_hw
rtl8187: Unknown symbol ieee80211_generic_frame_duration
rtl8187: Unknown symbol ieee80211_tx_status_irqsafe
rtl8187: Unknown symbol ieee80211_unregister_hw
rtl8187: Unknown symbol ieee80211_frequency_to_channel
rtl8187: Unknown symbol ieee80211_rx_irqsafe
rtl8187: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8180: Unknown symbol ieee80211_free_hw
rtl8180: Unknown symbol ieee80211_alloc_hw
rtl8180: Unknown symbol ieee80211_register_hw
rtl8180: Unknown symbol ieee80211_wake_queue
rtl8180: Unknown symbol ieee80211_tx_status_irqsafe
rtl8180: Unknown symbol ieee80211_stop_queue
rtl8180: Unknown symbol ieee80211_unregister_hw
rtl8180: Unknown symbol ieee80211_frequency_to_channel
rtl8180: Unknown symbol ieee80211_rx_irqsafe
rtl8180: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8187: Unknown symbol ieee80211_free_hw
rtl8187: Unknown symbol ieee80211_alloc_hw
rtl8187: Unknown symbol ieee80211_register_hw
rtl8187: Unknown symbol ieee80211_generic_frame_duration
rtl8187: Unknown symbol ieee80211_tx_status_irqsafe
rtl8187: Unknown symbol ieee80211_unregister_hw
rtl8187: Unknown symbol ieee80211_frequency_to_channel
rtl8187: Unknown symbol ieee80211_rx_irqsafe
rtl8187: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00pci: Unknown symbol rt2x00lib_suspend
rt2x00pci: Unknown symbol rt2x00lib_probe_dev
rt2x00pci: Unknown symbol ieee80211_free_hw
rt2x00pci: Unknown symbol ieee80211_alloc_hw
rt2x00pci: Unknown symbol rt2x00lib_rxdone
rt2x00pci: Unknown symbol rt2x00queue_get_entry
rt2x00pci: Unknown symbol rt2x00lib_remove_dev
rt2x00pci: Unknown symbol rt2x00lib_resume
rt2400pci: Unknown symbol rt2x00mac_add_interface
rt2400pci: Unknown symbol rt2x00queue_map_txskb
rt2400pci: Unknown symbol rt2x00mac_get_stats
rt2400pci: Unknown symbol rt2x00pci_initialize
rt2400pci: Unknown symbol rt2x00pci_uninitialize
rt2400pci: Unknown symbol rt2x00queue_get_entry
rt2400pci: Unknown symbol rt2x00pci_suspend
rt2400pci: Unknown symbol rt2x00mac_config_interface
rt2400pci: Unknown symbol rt2x00pci_remove
rt2400pci: Unknown symbol rt2x00mac_remove_interface
rt2400pci: Unknown symbol rt2x00lib_txdone
rt2400pci: Unknown symbol rt2x00mac_config
rt2400pci: Unknown symbol rt2x00queue_get_queue
rt2400pci: Unknown symbol rt2x00mac_conf_tx
rt2400pci: Unknown symbol rt2x00mac_start
rt2400pci: Unknown symbol rt2x00mac_stop
rt2400pci: Unknown symbol rt2x00mac_configure_filter
rt2400pci: Unknown symbol rt2x00mac_tx
rt2400pci: Unknown symbol rt2x00pci_resume
rt2400pci: Unknown symbol rt2x00pci_probe
rt2400pci: Unknown symbol rt2x00mac_get_tx_stats
rt2400pci: Unknown symbol rt2x00pci_rxdone
rt2400pci: Unknown symbol rt2x00lib_beacondone
rt2400pci: Unknown symbol rt2x00mac_bss_info_changed
rt2400pci: Unknown symbol rt2x00pci_write_tx_data
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00pci: Unknown symbol rt2x00lib_suspend
rt2x00pci: Unknown symbol rt2x00lib_probe_dev
rt2x00pci: Unknown symbol ieee80211_free_hw
rt2x00pci: Unknown symbol ieee80211_alloc_hw
rt2x00pci: Unknown symbol rt2x00lib_rxdone
rt2x00pci: Unknown symbol rt2x00queue_get_entry
rt2x00pci: Unknown symbol rt2x00lib_remove_dev
rt2x00pci: Unknown symbol rt2x00lib_resume
rt2500pci: Unknown symbol rt2x00mac_add_interface
rt2500pci: Unknown symbol rt2x00queue_map_txskb
rt2500pci: Unknown symbol rt2x00mac_get_stats
rt2500pci: Unknown symbol rt2x00pci_initialize
rt2500pci: Unknown symbol rt2x00pci_uninitialize
rt2500pci: Unknown symbol rt2x00queue_get_entry
rt2500pci: Unknown symbol rt2x00pci_suspend
rt2500pci: Unknown symbol rt2x00mac_config_interface
rt2500pci: Unknown symbol rt2x00pci_remove
rt2500pci: Unknown symbol rt2x00mac_remove_interface
rt2500pci: Unknown symbol rt2x00lib_txdone
rt2500pci: Unknown symbol rt2x00mac_config
rt2500pci: Unknown symbol rt2x00queue_get_queue
rt2500pci: Unknown symbol rt2x00mac_conf_tx
rt2500pci: Unknown symbol rt2x00mac_start
rt2500pci: Unknown symbol rt2x00mac_stop
rt2500pci: Unknown symbol rt2x00mac_configure_filter
rt2500pci: Unknown symbol rt2x00mac_tx
rt2500pci: Unknown symbol rt2x00pci_resume
rt2500pci: Unknown symbol rt2x00pci_probe
rt2500pci: Unknown symbol rt2x00mac_get_tx_stats
rt2500pci: Unknown symbol rt2x00pci_rxdone
rt2500pci: Unknown symbol rt2x00lib_beacondone
rt2500pci: Unknown symbol rt2x00mac_bss_info_changed
rt2500pci: Unknown symbol rt2x00pci_write_tx_data
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00pci: Unknown symbol rt2x00lib_suspend
rt2x00pci: Unknown symbol rt2x00lib_probe_dev
rt2x00pci: Unknown symbol ieee80211_free_hw
rt2x00pci: Unknown symbol ieee80211_alloc_hw
rt2x00pci: Unknown symbol rt2x00lib_rxdone
rt2x00pci: Unknown symbol rt2x00queue_get_entry
rt2x00pci: Unknown symbol rt2x00lib_remove_dev
rt2x00pci: Unknown symbol rt2x00lib_resume
rt61pci: Unknown symbol rt2x00mac_add_interface
rt61pci: Unknown symbol rt2x00mac_get_stats
rt61pci: Unknown symbol rt2x00pci_initialize
rt61pci: Unknown symbol rt2x00pci_uninitialize
rt61pci: Unknown symbol rt2x00queue_get_entry
rt61pci: Unknown symbol rt2x00pci_suspend
rt61pci: Unknown symbol rt2x00mac_config_interface
rt61pci: Unknown symbol rt2x00pci_remove
rt61pci: Unknown symbol rt2x00mac_remove_interface
rt61pci: Unknown symbol rt2x00lib_txdone
rt61pci: Unknown symbol rt2x00mac_config
rt61pci: Unknown symbol rt2x00queue_get_queue
rt61pci: Unknown symbol rt2x00mac_conf_tx
rt61pci: Unknown symbol rt2x00mac_start
rt61pci: Unknown symbol rt2x00mac_stop
rt61pci: Unknown symbol rt2x00mac_configure_filter
rt61pci: Unknown symbol rt2x00mac_tx
rt61pci: Unknown symbol rt2x00pci_resume
rt61pci: Unknown symbol rt2x00pci_probe
rt61pci: Unknown symbol rt2x00mac_get_tx_stats
rt61pci: Unknown symbol rt2x00pci_rxdone
rt61pci: Unknown symbol rt2x00mac_bss_info_changed
rt61pci: Unknown symbol rt2x00pci_write_tx_data
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00usb: Unknown symbol rt2x00lib_suspend
rt2x00usb: Unknown symbol rt2x00lib_probe_dev
rt2x00usb: Unknown symbol ieee80211_free_hw
rt2x00usb: Unknown symbol ieee80211_alloc_hw
rt2x00usb: Unknown symbol rt2x00lib_rxdone
rt2x00usb: Unknown symbol rt2x00lib_remove_dev
rt2x00usb: Unknown symbol rt2x00lib_txdone
rt2x00usb: Unknown symbol rt2x00queue_get_queue
rt2x00usb: Unknown symbol rt2x00lib_resume
rt2500usb: Unknown symbol rt2x00mac_add_interface
rt2500usb: Unknown symbol rt2x00mac_get_stats
rt2500usb: Unknown symbol rt2x00usb_init_rxentry
rt2500usb: Unknown symbol rt2x00usb_disable_radio
rt2500usb: Unknown symbol rt2x00usb_init_txentry
rt2500usb: Unknown symbol rt2x00usb_vendor_request_buff
rt2500usb: Unknown symbol rt2x00usb_kick_tx_queue
rt2500usb: Unknown symbol rt2x00usb_write_tx_data
rt2500usb: Unknown symbol rt2x00mac_config_interface
rt2500usb: Unknown symbol rt2x00mac_remove_interface
rt2500usb: Unknown symbol rt2x00usb_vendor_request
rt2500usb: Unknown symbol rt2x00usb_probe
rt2500usb: Unknown symbol rt2x00mac_config
rt2500usb: Unknown symbol rt2x00usb_suspend
rt2500usb: Unknown symbol rt2x00mac_conf_tx
rt2500usb: Unknown symbol rt2x00mac_start
rt2500usb: Unknown symbol rt2x00mac_stop
rt2500usb: Unknown symbol rt2x00mac_configure_filter
rt2500usb: Unknown symbol rt2x00usb_disconnect
rt2500usb: Unknown symbol rt2x00mac_tx
rt2500usb: Unknown symbol rt2x00usb_vendor_req_buff_lock
rt2500usb: Unknown symbol rt2x00mac_get_tx_stats
rt2500usb: Unknown symbol rt2x00usb_resume
rt2500usb: Unknown symbol rt2x00usb_uninitialize
rt2500usb: Unknown symbol rt2x00usb_initialize
rt2500usb: Unknown symbol rt2x00mac_bss_info_changed
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00usb: Unknown symbol rt2x00lib_suspend
rt2x00usb: Unknown symbol rt2x00lib_probe_dev
rt2x00usb: Unknown symbol ieee80211_free_hw
rt2x00usb: Unknown symbol ieee80211_alloc_hw
rt2x00usb: Unknown symbol rt2x00lib_rxdone
rt2x00usb: Unknown symbol rt2x00lib_remove_dev
rt2x00usb: Unknown symbol rt2x00lib_txdone
rt2x00usb: Unknown symbol rt2x00queue_get_queue
rt2x00usb: Unknown symbol rt2x00lib_resume
rt73usb: Unknown symbol rt2x00mac_add_interface
rt73usb: Unknown symbol rt2x00mac_get_stats
rt73usb: Unknown symbol rt2x00usb_init_rxentry
rt73usb: Unknown symbol rt2x00usb_disable_radio
rt73usb: Unknown symbol rt2x00usb_init_txentry
rt73usb: Unknown symbol rt2x00usb_vendor_request_buff
rt73usb: Unknown symbol rt2x00usb_kick_tx_queue
rt73usb: Unknown symbol rt2x00usb_write_tx_data
rt73usb: Unknown symbol rt2x00mac_config_interface
rt73usb: Unknown symbol rt2x00mac_remove_interface
rt73usb: Unknown symbol rt2x00usb_vendor_request
rt73usb: Unknown symbol rt2x00usb_probe
rt73usb: Unknown symbol rt2x00mac_config
rt73usb: Unknown symbol rt2x00usb_suspend
rt73usb: Unknown symbol rt2x00mac_conf_tx
rt73usb: Unknown symbol rt2x00mac_start
rt73usb: Unknown symbol rt2x00mac_stop
rt73usb: Unknown symbol rt2x00mac_configure_filter
rt73usb: Unknown symbol rt2x00usb_disconnect
rt73usb: Unknown symbol rt2x00mac_tx
rt73usb: Unknown symbol rt2x00usb_vendor_req_buff_lock
rt73usb: Unknown symbol rt2x00mac_get_tx_stats
rt73usb: Unknown symbol rt2x00usb_resume
rt73usb: Unknown symbol rt2x00usb_uninitialize
rt73usb: Unknown symbol rt2x00usb_initialize
rt73usb: Unknown symbol rt2x00mac_bss_info_changed
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver rndis_wlan
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
at76_usb: Unknown symbol ieee80211_free_hw
at76_usb: Unknown symbol ieee80211_alloc_hw
at76_usb: Unknown symbol ieee80211_register_hw
at76_usb: Unknown symbol ieee80211_tx_status_irqsafe
at76_usb: Unknown symbol ieee80211_wake_queues
at76_usb: Unknown symbol ieee80211_stop_queues
at76_usb: Unknown symbol ieee80211_scan_completed
at76_usb: Unknown symbol ieee80211_unregister_hw
at76_usb: Unknown symbol ieee80211_rx_irqsafe
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
ath5k: Unknown symbol ieee80211_free_hw
ath5k: Unknown symbol ieee80211_alloc_hw
ath5k: Unknown symbol ieee80211_register_hw
ath5k: Unknown symbol ieee80211_get_hdrlen_from_skb
ath5k: Unknown symbol ieee80211_generic_frame_duration
ath5k: Unknown symbol __ieee80211_get_tx_led_name
ath5k: Unknown symbol __ieee80211_get_rx_led_name
ath5k: Unknown symbol ieee80211_wake_queues
ath5k: Unknown symbol __ieee80211_rx
ath5k: Unknown symbol ieee80211_tx_status
ath5k: Unknown symbol ieee80211_stop_queue
ath5k: Unknown symbol ieee80211_stop_queues
ath5k: Unknown symbol ieee80211_unregister_hw
ath5k: Unknown symbol ieee80211_beacon_get
ath5k: Unknown symbol ieee80211_frequency_to_channel
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LK4E] -> GSI 19 (level,
high) -> IRQ 19
PCI: Setting latency timer of device 0000:03:00.0 to 64
ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
b43: Unknown symbol ieee80211_free_hw
b43: Unknown symbol ieee80211_alloc_hw
b43: Unknown symbol ieee80211_register_hw
b43: Unknown symbol ieee80211_generic_frame_duration
b43: Unknown symbol ieee80211_wake_queue
b43: Unknown symbol __ieee80211_get_tx_led_name
b43: Unknown symbol ieee80211_tx_status_irqsafe
b43: Unknown symbol __ieee80211_get_rx_led_name
b43: Unknown symbol ieee80211_ctstoself_get
b43: Unknown symbol ieee80211_stop_queue
b43: Unknown symbol __ieee80211_get_assoc_led_name
b43: Unknown symbol ieee80211_unregister_hw
b43: Unknown symbol ieee80211_hdrlen
b43: Unknown symbol ieee80211_rts_get
b43: Unknown symbol ieee80211_beacon_get
b43: Unknown symbol ieee80211_rx_irqsafe
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
b43legacy: Unknown symbol ieee80211_free_hw
b43legacy: Unknown symbol ieee80211_alloc_hw
b43legacy: Unknown symbol ieee80211_register_hw
b43legacy: Unknown symbol ieee80211_generic_frame_duration
b43legacy: Unknown symbol ieee80211_wake_queue
b43legacy: Unknown symbol __ieee80211_get_tx_led_name
b43legacy: Unknown symbol ieee80211_tx_status_irqsafe
b43legacy: Unknown symbol __ieee80211_get_rx_led_name
b43legacy: Unknown symbol ieee80211_ctstoself_get
b43legacy: Unknown symbol ieee80211_stop_queue
b43legacy: Unknown symbol ieee80211_stop_queues
b43legacy: Unknown symbol ieee80211_get_hdrlen
b43legacy: Unknown symbol __ieee80211_get_assoc_led_name
b43legacy: Unknown symbol ieee80211_unregister_hw
b43legacy: Unknown symbol ieee80211_hdrlen
b43legacy: Unknown symbol ieee80211_rts_get
b43legacy: Unknown symbol ieee80211_beacon_get
b43legacy: Unknown symbol ieee80211_rx_irqsafe
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
b43: Unknown symbol ieee80211_free_hw
b43: Unknown symbol ieee80211_alloc_hw
b43: Unknown symbol ieee80211_register_hw
b43: Unknown symbol ieee80211_generic_frame_duration
b43: Unknown symbol ieee80211_wake_queue
b43: Unknown symbol __ieee80211_get_tx_led_name
b43: Unknown symbol ieee80211_tx_status_irqsafe
b43: Unknown symbol __ieee80211_get_rx_led_name
b43: Unknown symbol ieee80211_ctstoself_get
b43: Unknown symbol ieee80211_stop_queue
b43: Unknown symbol __ieee80211_get_assoc_led_name
b43: Unknown symbol ieee80211_unregister_hw
b43: Unknown symbol ieee80211_hdrlen
b43: Unknown symbol ieee80211_rts_get
b43: Unknown symbol ieee80211_beacon_get
b43: Unknown symbol ieee80211_rx_irqsafe

[root@localhost compat-wireless-2008-08-06]# modprobe -v b43
insmod /lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko 
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
insmod /lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko 
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
insmod /lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43/b43.ko 
FATAL: Error inserting b43
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43/b43.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

Re: Question

[Luis R. Rodriguez]

On Wed, Aug 13, 2008 at 12:48 AM, Artjom <engine80@bk.ru> wrote:
> No possible to load compat-wireless modules in Fedora 8. What to do?
> What is the reason?
> The same with kernel 2.6.26.2-2.fc8.

You must do

make unload

first. Did you do that? And no need to do make load, just modprobe the
module of the wireless driver you need.

  Luis

Re: Question

[Chris Mason]

On Tue, 2008-08-12 at 13:32 -0700, Jeff Schroeder wrote:
> On Tue, Aug 12, 2008 at 1:06 PM, Morey Roof <moreyroof@gmail.com> wrote:
> > I was wondering if someone could give me a few hints.  I noticed that
> > all patches have [PATCH] in the subject.  Should this always be done?
> > Also, any other general rules to follow that could be passed on would
> > be nice.
> 
> Chris feel free to correct me on this, but...
> Since btrfs is Linux kernel code, the same rules apply for btrfs kernel code as
> they do for Linux kernel code. Take a look at Documentation/SubmittingPatches
> in a checkout of the kernel source. It is online here:
> http://users.sosdg.org/~qiyong/lxr/source/Documentation/SubmittingPatches
> 
> You can format your patch submission emails correctly with git-send-email(1).

Yes, in general the same rules apply to btrfs as the rest of the kernel.
But, one of my goals it to get new people involved and so I try fixup
imperfect patches as well.

-chris

Question

[Artjom]

No possible to load compat-wireless modules in Fedora 8. What to do?
What is the reason?
The same with kernel 2.6.26.2-2.fc8.
                                               Best regards.
                                                     Artjom.

[root@localhost compat-wireless-2008-08-06]# make load
Loading ipw2100...
Loading ipw2200...
Loading libertas_cs...
Loading usb8xxx...
Loading p54pci...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting p54common
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54common.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting p54pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading p54usb...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting p54common
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54common.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting p54usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading adm8211...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting adm8211
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/adm8211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading zd1211rw...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting zd1211rw
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/zd1211rw/zd1211rw.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8180...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8180
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8180.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8187...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8187
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8187.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading p54pci...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting p54common
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54common.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting p54pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading p54usb...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting p54common
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54common.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting p54usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/p54/p54usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading iwl3945...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting iwl3945
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/iwlwifi/iwl3945.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading iwl4965...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting iwlcore
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/iwlwifi/iwlcore.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting iwl4965
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/iwlwifi/iwl4965.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8180...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8180
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8180.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8187...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8187
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8187.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8180...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8180
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8180.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading rtl8187...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rtl8187
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rtl8187.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
Loading rt2400pci...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00lib
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rt2400pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2400pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rt2500pci...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00lib
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rt2500pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2500pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rt61pci...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00lib
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rt61pci
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt61pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rt2500usb...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00lib
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rt2500usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2500usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rt73usb...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00lib
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rt2x00usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt2x00usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting rt73usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/rt2x00/rt73usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Loading rndis_wlan...
Loading at76_usb...
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting at76_usb
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/at76_usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Module ath_pci not detected -- this is fine
Enabling ath5k ...      [OK]    Module renamed but another module file
is being preferred
Renamed
module:         /lib/modules/2.6.25.14-69.fc8/kernel/drivers/net/wireless/ath5k/ath5k.ko
Preferred
module:       /lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/ath5k/ath5k.ko
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting ath5k
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/ath5k/ath5k.ko): Unknown symbol in module, or unknown parameter (see dmesg)
ath5k loaded successfully
Module bcm43xx not detected -- this is fine
Enabling b43 ...        [OK]    Module renamed but another module file
is being preferred
Renamed
module:         /lib/modules/2.6.25.14-69.fc8/kernel/drivers/net/wireless/b43/b43.ko
Preferred
module:       /lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43/b43.ko
Enabling b43legacy ...  [OK]    Module renamed but another module file
is being preferred
Renamed
module:         /lib/modules/2.6.25.14-69.fc8/kernel/drivers/net/wireless/b43legacy/b43legacy.ko
Preferred
module:       /lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43legacy/b43legacy.ko
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting b43
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43/b43.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting b43legacy
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43legacy/b43legacy.ko): Unknown symbol in module, or unknown parameter (see dmesg)
b43 loaded successfully
b43legacy loaded successfully

[root@localhost compat-wireless-2008-08-06]# dmesg -c
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8180: Unknown symbol ieee80211_free_hw
rtl8180: Unknown symbol ieee80211_alloc_hw
rtl8180: Unknown symbol ieee80211_register_hw
rtl8180: Unknown symbol ieee80211_wake_queue
rtl8180: Unknown symbol ieee80211_tx_status_irqsafe
rtl8180: Unknown symbol ieee80211_stop_queue
rtl8180: Unknown symbol ieee80211_unregister_hw
rtl8180: Unknown symbol ieee80211_frequency_to_channel
rtl8180: Unknown symbol ieee80211_rx_irqsafe
rtl8180: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8187: Unknown symbol ieee80211_free_hw
rtl8187: Unknown symbol ieee80211_alloc_hw
rtl8187: Unknown symbol ieee80211_register_hw
rtl8187: Unknown symbol ieee80211_generic_frame_duration
rtl8187: Unknown symbol ieee80211_tx_status_irqsafe
rtl8187: Unknown symbol ieee80211_unregister_hw
rtl8187: Unknown symbol ieee80211_frequency_to_channel
rtl8187: Unknown symbol ieee80211_rx_irqsafe
rtl8187: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8180: Unknown symbol ieee80211_free_hw
rtl8180: Unknown symbol ieee80211_alloc_hw
rtl8180: Unknown symbol ieee80211_register_hw
rtl8180: Unknown symbol ieee80211_wake_queue
rtl8180: Unknown symbol ieee80211_tx_status_irqsafe
rtl8180: Unknown symbol ieee80211_stop_queue
rtl8180: Unknown symbol ieee80211_unregister_hw
rtl8180: Unknown symbol ieee80211_frequency_to_channel
rtl8180: Unknown symbol ieee80211_rx_irqsafe
rtl8180: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8187: Unknown symbol ieee80211_free_hw
rtl8187: Unknown symbol ieee80211_alloc_hw
rtl8187: Unknown symbol ieee80211_register_hw
rtl8187: Unknown symbol ieee80211_generic_frame_duration
rtl8187: Unknown symbol ieee80211_tx_status_irqsafe
rtl8187: Unknown symbol ieee80211_unregister_hw
rtl8187: Unknown symbol ieee80211_frequency_to_channel
rtl8187: Unknown symbol ieee80211_rx_irqsafe
rtl8187: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00pci: Unknown symbol rt2x00lib_suspend
rt2x00pci: Unknown symbol rt2x00lib_probe_dev
rt2x00pci: Unknown symbol ieee80211_free_hw
rt2x00pci: Unknown symbol ieee80211_alloc_hw
rt2x00pci: Unknown symbol rt2x00lib_rxdone
rt2x00pci: Unknown symbol rt2x00queue_get_entry
rt2x00pci: Unknown symbol rt2x00lib_remove_dev
rt2x00pci: Unknown symbol rt2x00lib_resume
rt2400pci: Unknown symbol rt2x00mac_add_interface
rt2400pci: Unknown symbol rt2x00queue_map_txskb
rt2400pci: Unknown symbol rt2x00mac_get_stats
rt2400pci: Unknown symbol rt2x00pci_initialize
rt2400pci: Unknown symbol rt2x00pci_uninitialize
rt2400pci: Unknown symbol rt2x00queue_get_entry
rt2400pci: Unknown symbol rt2x00pci_suspend
rt2400pci: Unknown symbol rt2x00mac_config_interface
rt2400pci: Unknown symbol rt2x00pci_remove
rt2400pci: Unknown symbol rt2x00mac_remove_interface
rt2400pci: Unknown symbol rt2x00lib_txdone
rt2400pci: Unknown symbol rt2x00mac_config
rt2400pci: Unknown symbol rt2x00queue_get_queue
rt2400pci: Unknown symbol rt2x00mac_conf_tx
rt2400pci: Unknown symbol rt2x00mac_start
rt2400pci: Unknown symbol rt2x00mac_stop
rt2400pci: Unknown symbol rt2x00mac_configure_filter
rt2400pci: Unknown symbol rt2x00mac_tx
rt2400pci: Unknown symbol rt2x00pci_resume
rt2400pci: Unknown symbol rt2x00pci_probe
rt2400pci: Unknown symbol rt2x00mac_get_tx_stats
rt2400pci: Unknown symbol rt2x00pci_rxdone
rt2400pci: Unknown symbol rt2x00lib_beacondone
rt2400pci: Unknown symbol rt2x00mac_bss_info_changed
rt2400pci: Unknown symbol rt2x00pci_write_tx_data
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00pci: Unknown symbol rt2x00lib_suspend
rt2x00pci: Unknown symbol rt2x00lib_probe_dev
rt2x00pci: Unknown symbol ieee80211_free_hw
rt2x00pci: Unknown symbol ieee80211_alloc_hw
rt2x00pci: Unknown symbol rt2x00lib_rxdone
rt2x00pci: Unknown symbol rt2x00queue_get_entry
rt2x00pci: Unknown symbol rt2x00lib_remove_dev
rt2x00pci: Unknown symbol rt2x00lib_resume
rt2500pci: Unknown symbol rt2x00mac_add_interface
rt2500pci: Unknown symbol rt2x00queue_map_txskb
rt2500pci: Unknown symbol rt2x00mac_get_stats
rt2500pci: Unknown symbol rt2x00pci_initialize
rt2500pci: Unknown symbol rt2x00pci_uninitialize
rt2500pci: Unknown symbol rt2x00queue_get_entry
rt2500pci: Unknown symbol rt2x00pci_suspend
rt2500pci: Unknown symbol rt2x00mac_config_interface
rt2500pci: Unknown symbol rt2x00pci_remove
rt2500pci: Unknown symbol rt2x00mac_remove_interface
rt2500pci: Unknown symbol rt2x00lib_txdone
rt2500pci: Unknown symbol rt2x00mac_config
rt2500pci: Unknown symbol rt2x00queue_get_queue
rt2500pci: Unknown symbol rt2x00mac_conf_tx
rt2500pci: Unknown symbol rt2x00mac_start
rt2500pci: Unknown symbol rt2x00mac_stop
rt2500pci: Unknown symbol rt2x00mac_configure_filter
rt2500pci: Unknown symbol rt2x00mac_tx
rt2500pci: Unknown symbol rt2x00pci_resume
rt2500pci: Unknown symbol rt2x00pci_probe
rt2500pci: Unknown symbol rt2x00mac_get_tx_stats
rt2500pci: Unknown symbol rt2x00pci_rxdone
rt2500pci: Unknown symbol rt2x00lib_beacondone
rt2500pci: Unknown symbol rt2x00mac_bss_info_changed
rt2500pci: Unknown symbol rt2x00pci_write_tx_data
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00pci: Unknown symbol rt2x00lib_suspend
rt2x00pci: Unknown symbol rt2x00lib_probe_dev
rt2x00pci: Unknown symbol ieee80211_free_hw
rt2x00pci: Unknown symbol ieee80211_alloc_hw
rt2x00pci: Unknown symbol rt2x00lib_rxdone
rt2x00pci: Unknown symbol rt2x00queue_get_entry
rt2x00pci: Unknown symbol rt2x00lib_remove_dev
rt2x00pci: Unknown symbol rt2x00lib_resume
rt61pci: Unknown symbol rt2x00mac_add_interface
rt61pci: Unknown symbol rt2x00mac_get_stats
rt61pci: Unknown symbol rt2x00pci_initialize
rt61pci: Unknown symbol rt2x00pci_uninitialize
rt61pci: Unknown symbol rt2x00queue_get_entry
rt61pci: Unknown symbol rt2x00pci_suspend
rt61pci: Unknown symbol rt2x00mac_config_interface
rt61pci: Unknown symbol rt2x00pci_remove
rt61pci: Unknown symbol rt2x00mac_remove_interface
rt61pci: Unknown symbol rt2x00lib_txdone
rt61pci: Unknown symbol rt2x00mac_config
rt61pci: Unknown symbol rt2x00queue_get_queue
rt61pci: Unknown symbol rt2x00mac_conf_tx
rt61pci: Unknown symbol rt2x00mac_start
rt61pci: Unknown symbol rt2x00mac_stop
rt61pci: Unknown symbol rt2x00mac_configure_filter
rt61pci: Unknown symbol rt2x00mac_tx
rt61pci: Unknown symbol rt2x00pci_resume
rt61pci: Unknown symbol rt2x00pci_probe
rt61pci: Unknown symbol rt2x00mac_get_tx_stats
rt61pci: Unknown symbol rt2x00pci_rxdone
rt61pci: Unknown symbol rt2x00mac_bss_info_changed
rt61pci: Unknown symbol rt2x00pci_write_tx_data
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00usb: Unknown symbol rt2x00lib_suspend
rt2x00usb: Unknown symbol rt2x00lib_probe_dev
rt2x00usb: Unknown symbol ieee80211_free_hw
rt2x00usb: Unknown symbol ieee80211_alloc_hw
rt2x00usb: Unknown symbol rt2x00lib_rxdone
rt2x00usb: Unknown symbol rt2x00lib_remove_dev
rt2x00usb: Unknown symbol rt2x00lib_txdone
rt2x00usb: Unknown symbol rt2x00queue_get_queue
rt2x00usb: Unknown symbol rt2x00lib_resume
rt2500usb: Unknown symbol rt2x00mac_add_interface
rt2500usb: Unknown symbol rt2x00mac_get_stats
rt2500usb: Unknown symbol rt2x00usb_init_rxentry
rt2500usb: Unknown symbol rt2x00usb_disable_radio
rt2500usb: Unknown symbol rt2x00usb_init_txentry
rt2500usb: Unknown symbol rt2x00usb_vendor_request_buff
rt2500usb: Unknown symbol rt2x00usb_kick_tx_queue
rt2500usb: Unknown symbol rt2x00usb_write_tx_data
rt2500usb: Unknown symbol rt2x00mac_config_interface
rt2500usb: Unknown symbol rt2x00mac_remove_interface
rt2500usb: Unknown symbol rt2x00usb_vendor_request
rt2500usb: Unknown symbol rt2x00usb_probe
rt2500usb: Unknown symbol rt2x00mac_config
rt2500usb: Unknown symbol rt2x00usb_suspend
rt2500usb: Unknown symbol rt2x00mac_conf_tx
rt2500usb: Unknown symbol rt2x00mac_start
rt2500usb: Unknown symbol rt2x00mac_stop
rt2500usb: Unknown symbol rt2x00mac_configure_filter
rt2500usb: Unknown symbol rt2x00usb_disconnect
rt2500usb: Unknown symbol rt2x00mac_tx
rt2500usb: Unknown symbol rt2x00usb_vendor_req_buff_lock
rt2500usb: Unknown symbol rt2x00mac_get_tx_stats
rt2500usb: Unknown symbol rt2x00usb_resume
rt2500usb: Unknown symbol rt2x00usb_uninitialize
rt2500usb: Unknown symbol rt2x00usb_initialize
rt2500usb: Unknown symbol rt2x00mac_bss_info_changed
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00usb: Unknown symbol rt2x00lib_suspend
rt2x00usb: Unknown symbol rt2x00lib_probe_dev
rt2x00usb: Unknown symbol ieee80211_free_hw
rt2x00usb: Unknown symbol ieee80211_alloc_hw
rt2x00usb: Unknown symbol rt2x00lib_rxdone
rt2x00usb: Unknown symbol rt2x00lib_remove_dev
rt2x00usb: Unknown symbol rt2x00lib_txdone
rt2x00usb: Unknown symbol rt2x00queue_get_queue
rt2x00usb: Unknown symbol rt2x00lib_resume
rt73usb: Unknown symbol rt2x00mac_add_interface
rt73usb: Unknown symbol rt2x00mac_get_stats
rt73usb: Unknown symbol rt2x00usb_init_rxentry
rt73usb: Unknown symbol rt2x00usb_disable_radio
rt73usb: Unknown symbol rt2x00usb_init_txentry
rt73usb: Unknown symbol rt2x00usb_vendor_request_buff
rt73usb: Unknown symbol rt2x00usb_kick_tx_queue
rt73usb: Unknown symbol rt2x00usb_write_tx_data
rt73usb: Unknown symbol rt2x00mac_config_interface
rt73usb: Unknown symbol rt2x00mac_remove_interface
rt73usb: Unknown symbol rt2x00usb_vendor_request
rt73usb: Unknown symbol rt2x00usb_probe
rt73usb: Unknown symbol rt2x00mac_config
rt73usb: Unknown symbol rt2x00usb_suspend
rt73usb: Unknown symbol rt2x00mac_conf_tx
rt73usb: Unknown symbol rt2x00mac_start
rt73usb: Unknown symbol rt2x00mac_stop
rt73usb: Unknown symbol rt2x00mac_configure_filter
rt73usb: Unknown symbol rt2x00usb_disconnect
rt73usb: Unknown symbol rt2x00mac_tx
rt73usb: Unknown symbol rt2x00usb_vendor_req_buff_lock
rt73usb: Unknown symbol rt2x00mac_get_tx_stats
rt73usb: Unknown symbol rt2x00usb_resume
rt73usb: Unknown symbol rt2x00usb_uninitialize
rt73usb: Unknown symbol rt2x00usb_initialize
rt73usb: Unknown symbol rt2x00mac_bss_info_changed
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver rndis_wlan
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
at76_usb: Unknown symbol ieee80211_free_hw
at76_usb: Unknown symbol ieee80211_alloc_hw
at76_usb: Unknown symbol ieee80211_register_hw
at76_usb: Unknown symbol ieee80211_tx_status_irqsafe
at76_usb: Unknown symbol ieee80211_wake_queues
at76_usb: Unknown symbol ieee80211_stop_queues
at76_usb: Unknown symbol ieee80211_scan_completed
at76_usb: Unknown symbol ieee80211_unregister_hw
at76_usb: Unknown symbol ieee80211_rx_irqsafe
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
ath5k: Unknown symbol ieee80211_free_hw
ath5k: Unknown symbol ieee80211_alloc_hw
ath5k: Unknown symbol ieee80211_register_hw
ath5k: Unknown symbol ieee80211_get_hdrlen_from_skb
ath5k: Unknown symbol ieee80211_generic_frame_duration
ath5k: Unknown symbol __ieee80211_get_tx_led_name
ath5k: Unknown symbol __ieee80211_get_rx_led_name
ath5k: Unknown symbol ieee80211_wake_queues
ath5k: Unknown symbol __ieee80211_rx
ath5k: Unknown symbol ieee80211_tx_status
ath5k: Unknown symbol ieee80211_stop_queue
ath5k: Unknown symbol ieee80211_stop_queues
ath5k: Unknown symbol ieee80211_unregister_hw
ath5k: Unknown symbol ieee80211_beacon_get
ath5k: Unknown symbol ieee80211_frequency_to_channel
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LK4E] -> GSI 19 (level,
high) -> IRQ 19
PCI: Setting latency timer of device 0000:03:00.0 to 64
ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
b43: Unknown symbol ieee80211_free_hw
b43: Unknown symbol ieee80211_alloc_hw
b43: Unknown symbol ieee80211_register_hw
b43: Unknown symbol ieee80211_generic_frame_duration
b43: Unknown symbol ieee80211_wake_queue
b43: Unknown symbol __ieee80211_get_tx_led_name
b43: Unknown symbol ieee80211_tx_status_irqsafe
b43: Unknown symbol __ieee80211_get_rx_led_name
b43: Unknown symbol ieee80211_ctstoself_get
b43: Unknown symbol ieee80211_stop_queue
b43: Unknown symbol __ieee80211_get_assoc_led_name
b43: Unknown symbol ieee80211_unregister_hw
b43: Unknown symbol ieee80211_hdrlen
b43: Unknown symbol ieee80211_rts_get
b43: Unknown symbol ieee80211_beacon_get
b43: Unknown symbol ieee80211_rx_irqsafe
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
b43legacy: Unknown symbol ieee80211_free_hw
b43legacy: Unknown symbol ieee80211_alloc_hw
b43legacy: Unknown symbol ieee80211_register_hw
b43legacy: Unknown symbol ieee80211_generic_frame_duration
b43legacy: Unknown symbol ieee80211_wake_queue
b43legacy: Unknown symbol __ieee80211_get_tx_led_name
b43legacy: Unknown symbol ieee80211_tx_status_irqsafe
b43legacy: Unknown symbol __ieee80211_get_rx_led_name
b43legacy: Unknown symbol ieee80211_ctstoself_get
b43legacy: Unknown symbol ieee80211_stop_queue
b43legacy: Unknown symbol ieee80211_stop_queues
b43legacy: Unknown symbol ieee80211_get_hdrlen
b43legacy: Unknown symbol __ieee80211_get_assoc_led_name
b43legacy: Unknown symbol ieee80211_unregister_hw
b43legacy: Unknown symbol ieee80211_hdrlen
b43legacy: Unknown symbol ieee80211_rts_get
b43legacy: Unknown symbol ieee80211_beacon_get
b43legacy: Unknown symbol ieee80211_rx_irqsafe
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
b43: Unknown symbol ieee80211_free_hw
b43: Unknown symbol ieee80211_alloc_hw
b43: Unknown symbol ieee80211_register_hw
b43: Unknown symbol ieee80211_generic_frame_duration
b43: Unknown symbol ieee80211_wake_queue
b43: Unknown symbol __ieee80211_get_tx_led_name
b43: Unknown symbol ieee80211_tx_status_irqsafe
b43: Unknown symbol __ieee80211_get_rx_led_name
b43: Unknown symbol ieee80211_ctstoself_get
b43: Unknown symbol ieee80211_stop_queue
b43: Unknown symbol __ieee80211_get_assoc_led_name
b43: Unknown symbol ieee80211_unregister_hw
b43: Unknown symbol ieee80211_hdrlen
b43: Unknown symbol ieee80211_rts_get
b43: Unknown symbol ieee80211_beacon_get
b43: Unknown symbol ieee80211_rx_irqsafe

[root@localhost compat-wireless-2008-08-06]# modprobe -v b43
insmod /lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko 
WARNING: Error inserting cfg80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/wireless/cfg80211.ko):
Invalid module format
insmod /lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko 
WARNING: Error inserting mac80211
(/lib/modules/2.6.25.14-69.fc8/updates/net/mac80211/mac80211.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
insmod /lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43/b43.ko 
FATAL: Error inserting b43
(/lib/modules/2.6.25.14-69.fc8/updates/drivers/net/wireless/b43/b43.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

Re: Question

[Jeff Schroeder]

On Tue, Aug 12, 2008 at 1:06 PM, Morey Roof <moreyroof@gmail.com> wrote:
> I was wondering if someone could give me a few hints.  I noticed that
> all patches have [PATCH] in the subject.  Should this always be done?
> Also, any other general rules to follow that could be passed on would
> be nice.

Chris feel free to correct me on this, but...
Since btrfs is Linux kernel code, the same rules apply for btrfs kernel code as
they do for Linux kernel code. Take a look at Documentation/SubmittingPatches
in a checkout of the kernel source. It is online here:
http://users.sosdg.org/~qiyong/lxr/source/Documentation/SubmittingPatches

You can format your patch submission emails correctly with git-send-email(1).

> Morey

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com

Question

[Morey Roof]

I was wondering if someone could give me a few hints.  I noticed that
all patches have [PATCH] in the subject.  Should this always be done?
Also, any other general rules to follow that could be passed on would
be nice.

Thanks,

Morey

Question

[mengualjeanphi]

Hi, can I write.

Re: Question

[Diego Lacerda]

Yeah,

It's possible, netfilter will change the packet as it passes through
the chains (in the NAT table).

Regards,
Diego Lacerda.

On Mon, Apr 28, 2008 at 7:11 AM, Jan Engelhardt <jengelh@computergmbh.de> wrote:
>
>
> On Monday 2008-04-28 11:01, Karim Reda Fakhir wrote:
>
> >How can i do SNAT and DNAT in same time with iptables , i try to
> >change Ip src and Ip dest .
>
> -t nat -A PREROUTING -j DNAT ...
> -t nat -A POSTROUTING -j SNAT ...
> no?
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: Question

[Jan Engelhardt]

On Monday 2008-04-28 11:01, Karim Reda Fakhir wrote:

>How can i do SNAT and DNAT in same time with iptables , i try to
>change Ip src and Ip dest .

-t nat -A PREROUTING -j DNAT ...
-t nat -A POSTROUTING -j SNAT ...
no?

Question

[Karim Reda Fakhir]

How can i do SNAT and DNAT in same time with iptables , i try to
change Ip src and Ip dest .


                  Best Regards.

Re: question

[Daniel Glöckner]

On Sat, Mar 01, 2008 at 02:49:42PM -0800, Michael Williamson wrote:
> With CX100 frame grabbers, it is possible to poll the
> even/odd video field bit through the ISA bus. 
> This is useful to have for cameras with electronic
> shutters to make long exposures. Is it possible to do
> with v4l2/bt848 PCI devices?

This information is available in the DSTATUS and INT_STAT register of the
bt848 but it is not exposed to userspace by the driver.

You can capture fields seperately to be informed of field changes.

  Daniel

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

question

[Michael Williamson]

Hi,

With CX100 frame grabbers, it is possible to poll the
even/odd video field bit through the ISA bus. 
This is useful to have for cameras with electronic
shutters to make long exposures. Is it possible to do
with v4l2/bt848 PCI devices?

Thanks,
-Mike



      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: question

[Stephen Smalley]

On Mon, 2007-02-05 at 19:33 +0200, Stefanos Harhalakis wrote:
> Hi there,
> 
>   Recently I started reading of selinux and I find it very useful. I'm planing 
> to use it for a multiuser server installation during the next 6 months. I've 
> read most of the documents I could find and a large portion of the 'SELinux 
> by Example' book.
> 
>   No matter where I looked I did not find an answer to the following question:
> 
>   When using the refpolicy, is it possible to adjust permissions without 
> changing the existing modules? As far as I understand, the proper way to 
> perform changes to existing modules is to change the appropriate .te file and 
> recompile it, but this presumes that there is only one kind of policy, one 
> policy tree and no future upgrades. Should I create my own supplementary 
> modules without defining any interfaces and load them?

You can perform certain forms of customization without disturbing the
existing policy by manipulating policy booleans (setsebool), context
mappings (semanage), or generating local policy modules (but those can
only allow further permissions, not take them away).  More significant
changes do require replacing portions of the existing policy, which is a
problem for continued updates from the original policy at present.
Common practice at present in e.g. Fedora is to have users generate
local policy modules for their needs, but encourage them to report
issues with the existing policy so that their changes can be fed back
into future updates of it.  I think you can expect improved support for
local customization and reconciling local customizations with updates in
the future.

-- 
Stephen Smalley
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

question

[Stefanos Harhalakis]

Hi there,

  Recently I started reading of selinux and I find it very useful. I'm planing 
to use it for a multiuser server installation during the next 6 months. I've 
read most of the documents I could find and a large portion of the 'SELinux 
by Example' book.

  No matter where I looked I did not find an answer to the following question:

  When using the refpolicy, is it possible to adjust permissions without 
changing the existing modules? As far as I understand, the proper way to 
perform changes to existing modules is to change the appropriate .te file and 
recompile it, but this presumes that there is only one kind of policy, one 
policy tree and no future upgrades. Should I create my own supplementary 
modules without defining any interfaces and load them?

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Question

[Chris Wright]

* Chuck Short (zulcss@gmail.com) wrote:
> I was wondering if the paravirt patches is actually usuable with Xen yet.

Yes, you can run a Xen domU based on the paravirt patches (although it
is still under development).

Question

[Chuck Short]

Hi,

I was wondering if the paravirt patches is actually usuable with Xen yet.

Thanks
chuck

question

[祝传雷]

[-- Attachment #1: Type: text/plain, Size: 411 bytes --]

nfs，您好！

	i do a nfs server  recently on suse linux 10 .
    /etc/export context:
	/var1/data      192.77.17.102(rw,no_root_squash) 192.77.17.101(rw,no_root_squash)

    i can mount directory in client ,but i write data from client to nfs server ,system report "Resource temporarily unavailable".
    i don't know what happened . i hope you can help me 
    thanks
    




　　　　　　　　 

[-- Attachment #2: Type: text/plain, Size: 373 bytes --]

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

RE: question

[Sietse van Zanen]

Usually you would test your firewall with the applications you need to use through it. That would be the only realistic test application wise.
 
For testing sustained tcp connections you can use a tool tike TTCP, which can open the connection and test throughput of your firewall.
http://www.pcausa.com/Utilities/pcattcp.htm
 
Foor DDOS simulations, you would need multiple pc's on your network and a simulation tool:
http://www.ssfnet.org/javadoc/SSF/App/DDoS/package-summary.html
 
-Sietse

________________________________

From: netfilter-bounces@lists.netfilter.org on behalf of Fabio S. Silva
Sent: Wed 21-Jun-06 14:14
To: netfilter@lists.netfilter.org
Subject: question



Hi all, i trying to find tools to test my firewall, i need to make
some test like "Sustained TCP Connections" but i dont know tools to do
it.. and... i need some tools to simulate an ddos to my firewall to
see if its droping packets, etc..
anybody can help me ??

best regards..

Fabio S. Silva

question

[Fabio S. Silva]

Hi all, i trying to find tools to test my firewall, i need to make
some test like "Sustained TCP Connections" but i dont know tools to do
it.. and... i need some tools to simulate an ddos to my firewall to
see if its droping packets, etc..
anybody can help me ??

best regards..

Fabio S. Silva

Re: Question

[Adam Wysocki via ArcaBit]

10.06.06 promod.promod@orangemail.sk wrote:

> How can I directly access port 0x378 (printer port ). I need to control LCD 
> display connected to printerport by setting some signals. From dosemu this 
> doesnt work. Can I set up dosemu to alow this port to dos program?

If you have working program in ANSI C and don't have to use dosemu, 
maybe ioperm(2) will help.

-- 
[ Adam Wysocki :: www.chmurka.net :: +48 514 710 213 ]
[ Software Development Department, ArcaBit Sp. z o.o ]
[ Ul. Fortuny 9 :: 01-339 Warszawa :: www.arcabit.pl ]

Question

[Palec Peter]

How can I directly access port 0x378 (printer port ). I need to control LCD 
display connected to printerport by setting some signals. From dosemu this 
doesnt work. Can I set up dosemu to alow this port to dos program?

Peter Palec 

Re: question

[Greg KH]

On Mon, Mar 06, 2006 at 11:49:31AM -0500, Doyle Bradford T (Brad) NPRI wrote:
> 
> I installed Red Hat Fedora Core 4 (FC4) operating system on a Dell
> Dimension XPSR450, but when it is booted it hangs on the line
> "Starting udev: Initializing hardware... storage network". I only have
> the following devices installed: a video card (STB nvidia TNT ver
> 1.10), a newer CPU, CD reader/writer, floppy drive, and a new Maxtor
> hard drive. (Conflicts with a network card, USB card, and sound card
> are not possible because these were removed before booting.)  Do you
> think this old Nvidia video card is conflicting with Udev?

As this is a FC4 issue, I suggest asking on one of their mailing lists
first.  If the issue is narrowed down to the core udev program, then we
will be glad to help you out here.

Good luck,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

question

[Doyle Bradford T (Brad) NPRI]

[-- Attachment #1.1: Type: text/plain, Size: 1077 bytes --]


	I installed Red Hat Fedora Core 4 (FC4) operating system on a Dell Dimension XPSR450, but when it is booted it hangs on the line "Starting udev: Initializing hardware... storage network". I only have the following devices installed: a video card (STB nvidia TNT ver 1.10), a newer CPU, CD reader/writer, floppy drive, and a new Maxtor hard drive. (Conflicts with a network card, USB card, and sound card are not possible because these were removed before booting.)  Do you think this old Nvidia video card is conflicting with Udev?

Bradford (Brad) T. Doyle
AN/SLQ-25A Lead Software Engineer 
NUWCDIVNPT Code 2512, on detail for Code 8242
Telephone# 401-832-3717

Nothing in the world can take the place of persistence. Talent will not; nothing is more common than unsuccessful men with talent. Genius will not; unrewarded genius is almost a proverb. Education will not, the world is full of educated derelicts. Persistence and determination alone are omnipotent. The slogan, 'Press on,' has solved and always will solve the problems of the human race. 
--Calvin Coolidge 



[-- Attachment #1.2: Type: text/html, Size: 1722 bytes --]

Question

[Robert-Panorama]

I am using ver 1.2.2 of dosemu on slackware 2.4.31. I Have read that 
there is some problems with database file (exactly indexes) and is 
better to mount database partition in sync mode. My question is if this 
mode is recognized by ncpmount, because my database files are on netware 
server which is mounted on local (linux) filesystem as ncp filesystem. 
Can I use sync option in my fstab to tell ncpmount about writing in 
synchro mode?
Thanks
Robert

--------------------
Masz k³opot ze znalezieniem czego¶ na mapie? My te¿!
Dlatego stawiamy na nawigacjê! To nowoczesny, najszybszy i najskuteczniejszy sposób!
Zajrzyj i przekonaj siê sam ...  http://www.gps.paragraf.pl/

Re: Question

[Bernd Petrovitsch]

On Wed, 2005-12-14 at 18:42 -0500, nramirez@site.uottawa.ca wrote:
[...]
> I want to implement a congestion control algorithm for an Ad-hoc wireless
> network. It means i will make some modifications to TCP and therefore in
> the transport layer.
> Do i need to modify the Kernel to do my implementation? or there are some

Yes.

> kernel modules i can modify as for the case of implementing a routing
> protocol in the network layer? If both are possible what could be the

No. You can compile the TCP/IP stack as module for easier
loading/unloading but that's all.

> advantage or disadvantage of each? Where can i get more information?

BTW almost rotuing protocols don't need changes in TCP/IP - they simple
use it as is and configure routes from the outside (of the kernel).

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services

Question

[nramirez]

Hi,

I want to implement a congestion control algorithm for an Ad-hoc wireless
network. It means i will make some modifications to TCP and therefore in
the transport layer.
Do i need to modify the Kernel to do my implementation? or there are some
kernel modules i can modify as for the case of implementing a routing
protocol in the network layer? If both are possible what could be the
advantage or disadvantage of each? Where can i get more information?

Thank you in advance,

Nadia Ramirez

Re: question

[Oskar Andreasson]

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

Shit happens, but now it works again. the admin of my site decided to
switch the dns records over to a temporary site while they are upgrading
the machine. my local dns server cached the old records while you seem
to have gotten to the new servers, and i didn't see it. 

To make a long story short, it's fixed. Same place as previously
mentioned... 3rd times the charm *crossing fingers* =)

On Thu, 2005-10-27 at 13:18 +0200, Marcin Giedz wrote:
> > Sorry about that, I got an urgent task on my desk and forgot to upload
> > the file:). It's uploaded now. Do note that this is just a very ugly
> > framework really, you need to do all the parsing etc on your own, and I
> > have a bad habit of not commenting work in progress projects... =)
> 	
> Hmm..  still have the same problem - sorry :( I tried http://www.frozentux.net 
> as well but it seems like some problems with PHP script :(
> 
> BR,
> Marcin

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: question

[Marcin Giedz]

> Sorry about that, I got an urgent task on my desk and forgot to upload
> the file:). It's uploaded now. Do note that this is just a very ugly
> framework really, you need to do all the parsing etc on your own, and I
> have a bad habit of not commenting work in progress projects... =)
	
Hmm..  still have the same problem - sorry :( I tried http://www.frozentux.net 
as well but it seems like some problems with PHP script :(

BR,
Marcin

Re: question

[Oskar Andreasson]

[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]

On Thu, 2005-10-27 at 12:25 +0200, Marcin Giedz wrote:
> Dnia czwartek, 27 października 2005 12:04, Oskar Andreasson napisał:
> > Hi Marcin,
> >
> > iptables and netfilter will not do the job, unless you are willing to
> > sacrifice stability and security. The problem is that the strings that
> > netfilter will see are broken down into smaller pieces. So the string
> > "iptables and netfilter" might actually be transmitted as "iptables and"
> > and then "netfilter" in a separate packet. On top of this, people might
> > try to intentionally break your filters by fragmenting the above string
> > into "i", "p", "t", ... etc packets.
> >
> > The good thing to do in this case, is to wait until the TCP stream has
> > reached the application layer and has been reassembled properly. Hence,
> > you will want to either write your own proxy, or to use someone elses
> > proxy.
> >
> > If you want to use it, I just uploaded a tunnel/proxy program to
> > http://www.frozentux.net/stunnel.tgz. This is an unfinished program I
> > started on a couple of years ago. It is written in C. It is horribly
> > coded and pretty much sucks, but it has no memory leaks and might serve
> > as a starting point.
> 
> Great!!! Really thanks but I just can't reach your program - above address 
> doesn't work :( Could you please do something or send the program on my 
> private mail.
> 

Sorry about that, I got an urgent task on my desk and forgot to upload
the file:). It's uploaded now. Do note that this is just a very ugly
framework really, you need to do all the parsing etc on your own, and I
have a bad habit of not commenting work in progress projects... =)

> Thanks once again,
> Marcin
> 
> >
> > Have a nice day;).
> >
> > On Thu, 2005-10-27 at 11:40 +0200, Marcin Giedz wrote:
> > > Dnia czwartek, 27 października 2005 11:09, Ruprecht Helms napisał:
> > > > Marcin Giedz wrote:
> > > > > I don't get it :(
> > > > > How with tcpdump as tcpdump is only dump traffic tool - as I know it
> > > > > can't change anything or I'm wrong?
> > > >
> > > > You are right. As I know it only dump.
> > > > What you need is a hexeditor or you are looking for a tool that do
> > > > hexediting in the fly.
> > >
> > > Absolutely!
> > >
> > > > But that is offtopic in this list.
> > >
> > > But I really don't know where to start? Perhaps some did it earlier.
> > >
> > > Marcin
> > >
> > > > Regards,
> > > > Ruprecht

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: question

[Marcin Giedz]

Dnia czwartek, 27 pa¼dziernika 2005 12:04, Oskar Andreasson napisa³:
> Hi Marcin,
>
> iptables and netfilter will not do the job, unless you are willing to
> sacrifice stability and security. The problem is that the strings that
> netfilter will see are broken down into smaller pieces. So the string
> "iptables and netfilter" might actually be transmitted as "iptables and"
> and then "netfilter" in a separate packet. On top of this, people might
> try to intentionally break your filters by fragmenting the above string
> into "i", "p", "t", ... etc packets.
>
> The good thing to do in this case, is to wait until the TCP stream has
> reached the application layer and has been reassembled properly. Hence,
> you will want to either write your own proxy, or to use someone elses
> proxy.
>
> If you want to use it, I just uploaded a tunnel/proxy program to
> http://www.frozentux.net/stunnel.tgz. This is an unfinished program I
> started on a couple of years ago. It is written in C. It is horribly
> coded and pretty much sucks, but it has no memory leaks and might serve
> as a starting point.

Great!!! Really thanks but I just can't reach your program - above address 
doesn't work :( Could you please do something or send the program on my 
private mail.

Thanks once again,
Marcin

>
> Have a nice day;).
>
> On Thu, 2005-10-27 at 11:40 +0200, Marcin Giedz wrote:
> > Dnia czwartek, 27 pa¼dziernika 2005 11:09, Ruprecht Helms napisa³:
> > > Marcin Giedz wrote:
> > > > I don't get it :(
> > > > How with tcpdump as tcpdump is only dump traffic tool - as I know it
> > > > can't change anything or I'm wrong?
> > >
> > > You are right. As I know it only dump.
> > > What you need is a hexeditor or you are looking for a tool that do
> > > hexediting in the fly.
> >
> > Absolutely!
> >
> > > But that is offtopic in this list.
> >
> > But I really don't know where to start? Perhaps some did it earlier.
> >
> > Marcin
> >
> > > Regards,
> > > Ruprecht

Re: question

[Oskar Andreasson]

[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]

Hi Marcin, 

iptables and netfilter will not do the job, unless you are willing to
sacrifice stability and security. The problem is that the strings that
netfilter will see are broken down into smaller pieces. So the string
"iptables and netfilter" might actually be transmitted as "iptables and"
and then "netfilter" in a separate packet. On top of this, people might
try to intentionally break your filters by fragmenting the above string
into "i", "p", "t", ... etc packets. 

The good thing to do in this case, is to wait until the TCP stream has
reached the application layer and has been reassembled properly. Hence,
you will want to either write your own proxy, or to use someone elses
proxy. 

If you want to use it, I just uploaded a tunnel/proxy program to
http://www.frozentux.net/stunnel.tgz. This is an unfinished program I
started on a couple of years ago. It is written in C. It is horribly
coded and pretty much sucks, but it has no memory leaks and might serve
as a starting point.

Have a nice day;).


On Thu, 2005-10-27 at 11:40 +0200, Marcin Giedz wrote:
> Dnia czwartek, 27 października 2005 11:09, Ruprecht Helms napisał:
> > Marcin Giedz wrote:
> > > I don't get it :(
> > > How with tcpdump as tcpdump is only dump traffic tool - as I know it
> > > can't change anything or I'm wrong?
> >
> > You are right. As I know it only dump.
> > What you need is a hexeditor or you are looking for a tool that do
> > hexediting in the fly.
> 
> Absolutely! 
> 
> >
> > But that is offtopic in this list.
> 
> But I really don't know where to start? Perhaps some did it earlier.
> 
> Marcin
> 
> >
> > Regards,
> > Ruprecht
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: question

[Marcin Giedz]

Dnia czwartek, 27 pa¼dziernika 2005 11:09, Ruprecht Helms napisa³:
> Marcin Giedz wrote:
> > I don't get it :(
> > How with tcpdump as tcpdump is only dump traffic tool - as I know it
> > can't change anything or I'm wrong?
>
> You are right. As I know it only dump.
> What you need is a hexeditor or you are looking for a tool that do
> hexediting in the fly.

Absolutely! 

>
> But that is offtopic in this list.

But I really don't know where to start? Perhaps some did it earlier.

Marcin

>
> Regards,
> Ruprecht

Re: question

[Sorin Panca]

Ruprecht Helms wrote:
> Marcin Giedz wrote:
> 
>>
>> I don't get it :(
>> How with tcpdump as tcpdump is only dump traffic tool - as I know it
>> can't change anything or I'm wrong?
> 
> 
> You are right. As I know it only dump.
> What you need is a hexeditor or you are looking for a tool that do
> hexediting in the fly.
> 
> But that is offtopic in this list.
I think he needs a packet mangling tool: he's not offtopic.

Re: question

[Ruprecht Helms]

Marcin Giedz wrote:

> 
> I don't get it :(
> How with tcpdump as tcpdump is only dump traffic tool - as I know it can't 
> change anything or I'm wrong?

You are right. As I know it only dump.
What you need is a hexeditor or you are looking for a tool that do 
hexediting in the fly.

But that is offtopic in this list.

Regards,
Ruprecht

Re: question

[Marcin Giedz]

Dnia czwartek, 27 pa¼dziernika 2005 10:18, Ruprecht Helms napisa³:
> Hi Marcin,
>
> > I'd like to ask if it possible to change "data" field (its content) in
> > TCP packet on fly? I don't need to change data's lenght but only change
> > few bytes in it.
> >
> > Example:
> > 0000  ff ff ff ff ff ff 00 11 25 31 ad e0 08 00 45 00   ........%1....E.
>
> much you can do with tcpdump.

I don't get it :(
How with tcpdump as tcpdump is only dump traffic tool - as I know it can't 
change anything or I'm wrong?

Marcin

>
> Regards,
> Ruprecht
>
> ---------------------------------------------------------------------------
>--------------- Ruprecht Helms IT-Service & Softwareentwicklung
>
> Tel./Fax  +49[0]7621 16 99 16
> Web:       htp://www.rheyn.de

Re: question

[Ruprecht Helms]

Hi Marcin,
> 
> I'd like to ask if it possible to change "data" field (its content) in TCP 
> packet on fly? I don't need to change data's lenght but only change few bytes 
> in it.
> 
> Example:
> 0000  ff ff ff ff ff ff 00 11 25 31 ad e0 08 00 45 00   ........%1....E.

much you can do with tcpdump.

Regards,
Ruprecht

------------------------------------------------------------------------------------------
Ruprecht Helms IT-Service & Softwareentwicklung

Tel./Fax  +49[0]7621 16 99 16
Web:       htp://www.rheyn.de

question

[Marcin Giedz]

Hi,


I'd like to ask if it possible to change "data" field (its content) in TCP 
packet on fly? I don't need to change data's lenght but only change few bytes 
in it.

Example:
0000  ff ff ff ff ff ff 00 11 25 31 ad e0 08 00 45 00   ........%1....E.
0010  00 c1 0a b1 00 00 80 11 82 0f ac 13 01 59 ff ff   .............Y..
0020  ff ff 04 2d 01 db 00 ad 60 78 ad a7 5b de 9f 26   ...-....`x..[..&
0030  ec 98 2d 26 ec 18 2d 26 ec 18 2d 26 ec 18 2d 26   ..-&..-&..-&..-&
0040  ec 18 2d 26 ec 18 2d 26 ec 18 2d 26 ec 18 2d 26   ..-&..-&..-&..-&

First line contains MAC address 00:11:25:31:ad:e0 - I need to change it to 
other value. 

Is it possible at all?

Marcin

Re: question.

[Clarence Dang]

On Wednesday 05 October 2005 04:59, Jan Willem Stumpel wrote:
> Promod, s.r.o. wrote:
> > I tryed to install dosemu on mandrale linux 9.1. "make" run OK and "make
> > install" too. Freedos is installed and I can run text DOS programs. But
> > I don't know how can I use program with graphics output
>
> you should use the
> command "xdosemu", not "dosemu", if you want graphics.

Something to be fixed on the dosemu end, perhaps, to avoid this kind of 
confusion?

Re: question.

[Jan Willem Stumpel]

Promod, s.r.o. wrote:
> I tryed to install dosemu on mandrale linux 9.1. "make" run OK and "make 
> install" too. Freedos is installed and I can run text DOS programs. But 
> I don't know how can I use program with graphics output - classic 
> borland C++ 3.1 program. 
> If I run program, program runs ( I can stop it with kwyboard, but I 
> don't see  graphics output - standard  640x480 VGA ).
> I try this on other competer and result is the same. But on this PC some 
> text programs don't run corectly (volkov commander), because text window 
> is in some strange mode ( something like 100x36 not 80x25).I tryed to 
> configure dosemu.conf file but no solution.
> Could you help

How did you start dosemu? From an xterm (in X) you should use the 
command "xdosemu", not "dosemu", if you want graphics.

Regards, Jan

question.

[Promod, s.r.o.]

I tryed to install dosemu on mandrale linux 9.1. "make" run OK and "make 
install" too. Freedos is installed and I can run text DOS programs. But 
I don't know how can I use program with graphics output - classic 
borland C++ 3.1 program. 
If I run program, program runs ( I can stop it with kwyboard, but I 
don't see  graphics output - standard  640x480 VGA ).
I try this on other competer and result is the same. But on this PC some 
text programs don't run corectly (volkov commander), because text window 
is in some strange mode ( something like 100x36 not 80x25).I tryed to 
configure dosemu.conf file but no solution.
Could you help me?

question

[Philip Pokorny]

I think the chips are even pin compatible which means that Tyan could 
concievably switch from vendor to vendor for each lot of boards.

Reading the lm85 docs, I see that there are a couple of documented 
"enchancements" in the ADT7463 over the LM85, so it's probably a better 
chip anyway.

:v)

Jean Delvare wrote:

>Hi Paul,
>
>  
>
>>One question I have is that I have two indentical systems from the
>>same  manufacturer, Tyan. One has a Celeron CPU and the other has a P4
>>with HT,  but the motherboards are the same. On one unit I must use a
>>lm85-* in  sensors.conf and the the other with a adt7463-* for the
>>chips section or the  values don't make sense.
>>
>>Could the different CPU's be causing lmsensors to get confused? I even
>>ran  the detect routines and came with the same results. What else
>>could I do to  check this?
>>    
>>
>
>There's nothing wrong with that. Both chips are mostly compatible, so
>Tyan may simply have switched at some point in time for some reason
>(price or availabilty for example). You can notice that both chips are
>supported by the same driver (lm85).
>
>You can share a section of sensors.conf among several chips by simply
>giving it more than just one chip name. If you take a look at the
>default configuration file, that's exactly what we do for the lm85
>driver:
>
>chip "lm85c-*" "adm1027-*" "adt7463-*" "lm85-*" "lm85b-*"
>
>   set temp1_max 50
>
>(...)
>
>Just do that for your own file and you will have a single file to
>maintain for both boards.
>
>  
>

question

[Paul Aviles]

Hello all,

Thanks to all for your answers and support. I was finally able to figure out 
my problems with the .spec file and I am now creating the rpms.

One question I have is that I have two indentical systems from the same 
manufacturer, Tyan. One has a Celeron CPU and the other has a P4 with HT, 
but the motherboards are the same. On one unit I must use a lm85-* in 
sensors.conf and the the other with a adt7463-* for the chips section or the 
values don't make sense.

Could the different CPU's be causing lmsensors to get confused? I even ran 
the detect routines and came with the same results. What else could I do to 
check this?

Thanks so much!!

Paul

Sample report.

lm85-i2c-0-2e
Adapter: SMBus I801 adapter at 1480
+2.6V:      +2.62 V  (min =  +2.47 V, max =  +2.73 V)
CPU Volt: +1.31 V  (min =  +1.25 V, max =  +1.40 V)
+3.3V:      +3.35 V  (min =  +3.13 V, max =  +3.47 V)
+5V:       +5.05 V  (min =  +4.74 V, max =  +5.26 V)
Fan2:      8424 RPM  (min = 4800 RPM)
Fan1:      6136 RPM  (min = 4800 RPM)
Fan3:      9294 RPM  (min = 2200 RPM)
CPU Temp:    +47?C  (low  =    +5?C, high =   +68?C)
Loc Temp:     +36?C  (low  =    +5?C, high =   +40?C)
Sys Temp:      +38?C  (low  =    +5?C, high =   +50?C)
vid:      +1.325 V  (VRM Version 9.1)

eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 1480
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-0-53
Adapter: SMBus I801 adapter at 1480
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512




-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

question

[Jean Delvare]

Hi Paul,

> One question I have is that I have two indentical systems from the
> same  manufacturer, Tyan. One has a Celeron CPU and the other has a P4
> with HT,  but the motherboards are the same. On one unit I must use a
> lm85-* in  sensors.conf and the the other with a adt7463-* for the
> chips section or the  values don't make sense.
> 
> Could the different CPU's be causing lmsensors to get confused? I even
> ran  the detect routines and came with the same results. What else
> could I do to  check this?

There's nothing wrong with that. Both chips are mostly compatible, so
Tyan may simply have switched at some point in time for some reason
(price or availabilty for example). You can notice that both chips are
supported by the same driver (lm85).

You can share a section of sensors.conf among several chips by simply
giving it more than just one chip name. If you take a look at the
default configuration file, that's exactly what we do for the lm85
driver:

chip "lm85c-*" "adm1027-*" "adt7463-*" "lm85-*" "lm85b-*"

   set temp1_max 50

(...)

Just do that for your own file and you will have a single file to
maintain for both boards.

-- 
Jean Delvare
http://khali.linux-fr.org/

Question

[phil]

Basicly, you insmod the driver, and you should see some files in
/proc/sys/dev/sensors/bt869*/ .  Then, you put your X-server in a NTSC
resolution, and then set the appropriate values in the files in the
directory noted above (e.g. "echo 0 > colorbars", and set ntsc/pal,
resolution, etc.).  Check the output.  If nessesary, you may need to
select the appropriate output port if you don't get anything.  Some
modifications to the driver were recently submitted to CVS (see our
download page for instruction on CVS), so you might try that.

Good luck!


Phil


On Thu, Feb 14, 2002 at 02:26:32PM -0500, Hoopez wrote:
> 
> Hi,                                                                                                                                                       
> I have a question about voodoo 3 cards and s-video tv-out in
> linux that i hope you can answer. I ran through the howto (i'm in america,
> ntsc) and i'm at the point just before you restart the X server. I'm out of sync (or whatever                                                                                  
> you call it), and then when i hit ctrl-alt-number_pad_+, i can see the                                                                                    
> colorbars for one second, until the x server restarts, then it goes back                                                                                  
> to the out-of-sync display. I was wondering if you had any advice on what                                                                                 
> to do or where I should look? I'm running Redhat 7.2 on an Athlon K7,                                                                                     
> Voodoo 3 3000, kernel 2.4.7-10 (i also tried it on 2.4.17)                                                                                                
>                                                                                                                                                           
> If you can help me, thanks, if not, thanks again!                                                                                                         
> Matt Hoopes         

-- 
Philip Edelbrock -- IS Manager -- Edge Design, Corvallis, OR
   phil@netroedge.com -- http://www.netroedge.com/~phil
 PGP F16: 01 D2 FD 01 B5 46 F4 F0  3A 8B 9D 7E 14 7F FB 7A

Re: Question

[comercial-newprint]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]

El correo al cual a enviado este eMail no existe, para contactar con nosotros por favor envie sus correos a alguna de las siguientes direcciones.

administración@in-out.es 	Administracion Grupo IN-out.

comercial@in-out.es		Dpto. Comercial Grupo IN-out.

pedidos@in-out.es		Pedidos Grupo IN-out.

grafismo@in-out.es		Dpto. diseño Grupo IN-out


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

Re: Question

[Juan Quintela]

>>>>> "peter" == Peter Hemström <peter@hemstrom.info> writes:

Hi

peter> I have lookt on internet for an awnser, but cant find one.

peter> Should i use the SMP kernal with an INTEL HT-Tech CPU?

Yes if you want to use hyperthreading.

peter> Thanks for an awnser.

You are wellcome.

Later, Juan.

-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

Question

[Peter Hemström]

Hello!

I have a question...

I have lookt on internet for an awnser, but cant find one.

Should i use the SMP kernal with an INTEL HT-Tech CPU?

Thanks for an awnser.

Peter Hemstrom

Re: Question

[Stephen Smalley]

On Mon, 2004-07-05 at 11:20, Christopher Soghoian wrote:
> What we'd like to be able to do, is to freeze the process right before
> the read/write request gets rejected.. and then call a script, which
> can gather some forensic information on the process.
> 
> It's important for us to be able to do this -before- the process's request
> is rejected.
> 
> I don't think theres anything in place right now to do this (or am I wrong?),
> but could someone please let me know how difficult it would be to add this,
> and where the code would have to go?
> 
> Ideally, we'd like to do a `kill -s SIGSTOP` on the process, and then run
> a script (passing in the misbehaving pid).

You would need to be selective in the set of permission checks that
triggered such behavior, as some permissions checks are called at points
where it would not be safe for you to block in this manner (e.g. kernel
locks may be held, or you may not even be in process context).  You
could introduce an additional access vector for this purpose, similar to
the existing vectors that control the auditing behavior.  You could then
modify avc_has_perm_noaudit() to (after releasing its own lock) call
force_sig_specific(SIGSTOP, current) if a) in process context, and b)
the requested permissions were denied, and c) the denied permissions
were present in the new vector, and to then call call_usermodehelper()
to run your script.  Or you could do likewise in specific hook
functions, e.g. selinux_inode_permission(), if you only wanted to apply
such behavior to specific hooks.

-- 
Stephen Smalley <sds@epoch.ncsc.mil>
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Question

[Christopher Soghoian]

Hi All,

I'm working on a summer project for IBM research, and we're interested
in gathering forensic information on misbehaving processes.

Consider the case when a process is trying to do something it shouldn't,
SELinux steps in, denies the read/write/whatever request, and then prints
out an error message.

What we'd like to be able to do, is to freeze the process right before
the read/write request gets rejected.. and then call a script, which
can gather some forensic information on the process.

It's important for us to be able to do this -before- the process's request
is rejected.

I don't think theres anything in place right now to do this (or am I wrong?),
but could someone please let me know how difficult it would be to add this,
and where the code would have to go?

Ideally, we'd like to do a `kill -s SIGSTOP` on the process, and then run
a script (passing in the misbehaving pid).

Thanks in advance,

Chris

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Question

[Jurzitza, Dieter]

Dear listmemebers,
could any friendly soul tell me what is the meaning of:

Jun 21 11:14:30 oekalux08 kernel: __alloc_pages: 2-order allocation failed
(gfp=0x20/0)

or 

Jun 21 11:14:35 oekalux08 kernel: __alloc_pages: 1-order allocation failed
(gfp=0x20/0)

when suddenly occuring in /var/log/messages?
Many thanks for your help,
take care



Dieter Jurzitza


-- 
________________________________________________

HARMAN BECKER AUTOMOTIVE SYSTEMS

Dr.-Ing. Dieter Jurzitza
Manager Hardware Systems
         ESI

Industriegebiet Ittersbach
Becker-Göring Str. 16
D-76307 Karlsbad / Germany

Phone: +49 (0)7248 71-1577
Fax:   +49 (0)7248 71-1216
eMail: DJurzitza@harmanbecker.com
Internet: http://www.becker.de
 


*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
 
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.
*******************************************

Question

[Jurzitza, Dieter]

Dear listmembers,
can anyone propably help me out: what does the message

oekalux08 kernel: __alloc_pages: 2-order allocation failed (gfp=0x20/0)
oekalux08 last message repeated 125 times

mean? I found it in /var/log/messages. Always my U60 SMP / Kernel 2.4.26.
Many thanks in advance
take care


Dieter Jurzitza


-- 
________________________________________________

HARMAN BECKER AUTOMOTIVE SYSTEMS

Dr.-Ing. Dieter Jurzitza
Manager Hardware Systems
         ESI

Industriegebiet Ittersbach
Becker-Göring Str. 16
D-76307 Karlsbad / Germany

Phone: +49 (0)7248 71-1577
Fax:   +49 (0)7248 71-1216
eMail: DJurzitza@harmanbecker.com
Internet: http://www.becker.de
 


*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
 
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.
*******************************************

question

[WemiAX]

[-- Attachment #1.1: Type: text/plain, Size: 197 bytes --]

77NvMSY8 e1138N3c4 00a41qf 36bq Pg7t52p FQdANMe 7u t52164mv8 1CA2 eqhXn80 p7SrUhj 6MJ qUR258
6uFE h2OH81 dO435
S0St465 4152bB4nY i3lhP4 07BY0 0r TsB1y Y2 k4V8m0Gx0 3cX3MGW5 61lwr8g MCP06 pCV874

[-- Attachment #1.2: Type: image/gif, Size: 3889 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq

Re: Question

[Tim Goetze]

[jacqueslen@sympatico.ca]

>Hullo, I can't seem to find how to create MIDI channel mode messages
>(like "reset all controllers" or "all notes off"), nor can I find out
>how to create many MIDI meta events (like "text event" or "copyright
>notice" or "sequence name"), I've been able to find out how to create
>some events at
>http://www.alsa-project.org/alsa-doc/alsa-lib/group___seq_middle.html
>, but not very many. Anyone have any ideas?

ad 1: standard MIDI controller specs can be found all over the 'net,
but the best thing is to consult the target device documentation.
if the device receiving the controller event interprets it as an
'omni' event, it will simply ignore the event channel, and so would
you.

to prepare controller event data, i use:

    snd_seq_event_t packet;

    packet.type = SND_SEQ_EVENT_CONTROLLER;
    packet.data.control.channel = channel;
    packet.data.control.param = controller;
    packet.data.control.value = value;

ad 2: afaik, you can't send meta events via the ALSA sequencer. they
only make sense within a MIDI file.

cheers,

tim


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

Question

[jacqueslen]

Hullo,
I can't seem to find how to create MIDI channel mode messages (like "reset all controllers" or "all notes off"), nor can I find out how to create many MIDI meta events (like "text event" or "copyright notice" or "sequence name"), I've been able to find out how to create some events at http://www.alsa-project.org/alsa-doc/alsa-lib/group___seq_middle.html , but not very many. Anyone have any ideas?
--Jacques


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

Re: question

[Henrik Nordstrom]

On Wed, 21 Jan 2004, Jeanmich wrote:

> I would like to protect myself against syn flooding.

What kind of SYN flooding of what?

> Obviously, i've looked on the web and i found 2 solutions :
> 
> -1- echo 1 in the file /proc/sys/net/ipv4/tcp_syncookies
> -2- iptables -A FORWARD -p tcp --syn -m limit --limit
> 1/second -J ACCEPT

The first makes Linux deal with SYN flooding on any services given by THIS 
Linux box. It does nothing on forwarded traffic.

THe second makes sure SYN "flooding" guantees a Denial of Service any new
sessions matching that rule in order to protect servers from becoming
overloaded by too many new sessions too fast, but without regard to the
actual load on the server.  This type of protection is highly overrated
and almost always causes more problems than it solves.  SYN flooding
SHOULD be addressed on the actual server using approach '1' or equivalent
(depending on the Server OS).

Neither protects from connection flooding if the server accepts long 
connections. And again connection flooding SHOULD be addressed on the 
server if possible as firewalling has much less knowledge of what is 
actually going on within the active sessions.

> When i've have a look in
> /usr/scr/linux/Documentation/networking/ip-sysctl.txt, i
> understand that it is a "facility" to use -1-, and that -1-
> is often hiding "misconfigured" servers.

This is not what the documentation says. What it says is that 
syncookies is not a substitute for a large SYN backlog unless there 
actually is a synflood in progress.

Both syncookies and SYN backlog is only relevant on connections to this
server. It is not related to forwarded traffic.

Regards
Henrik

question

[Jeanmich]

Hello.
I'm a french guy, so first of all, please, forgive my poor
english.
I'm insteresting by netfilter just as a user.
I've installed my Linux (RH9) at home as my first machine on
internet, trying to secure my little network. I think it is
working well.

I would like to protect myself against syn flooding.
Obviously, i've looked on the web and i found 2 solutions :

-1- echo 1 in the file /proc/sys/net/ipv4/tcp_syncookies
-2- iptables -A FORWARD -p tcp --syn -m limit --limit
1/second -J ACCEPT

This 2 solutions are accepted, and both seems to work.

My problem is : which one is the one ?

When i've have a look in
/usr/scr/linux/Documentation/networking/ip-sysctl.txt, i
understand that it is a "facility" to use -1-, and that -1-
is often hiding "misconfigured" servers.
But, http://cr.yp.to/syncookies.html seems to disagree.

When i looked on the web iptables scripts, approximately 80%
are using -1- and only 20% are using -2-.



Thanks for helping me to understand.
JMC

********** PROTEGEZ VOS E-MAILS !********** 
Avec Tiscali SuperMail, vos e-mails en toute sécurité ! 
Anti Spam personnalisable 
Anti Virus actualisé en permanence 
et de nombreux bonus... 
Pour en savoir plus, rendez-vous sur http://www.tiscali.fr/supermail/

RE: question

[Neil Holmes]

I haven't had much time to work on the Elks Distribution Edition of late.
But in the state it is in it should easily install and also co-exist with a
DOS environment. Feel free to drop me a line if I may be able to assist with
your setup.

Neil

-----Original Message-----
From: linux-8086-owner@vger.kernel.org
[mailto:linux-8086-owner@vger.kernel.org]On Behalf Of Jody
Sent: 14 January 2004 04:34
To: linux-8086@vger.kernel.org
Subject: Re: question


Assuming that you're referring to an ELKS-based environment, the best
advice at the moment that I can give is to download the "ELKS Distribution
Edition" from http://www.sourceforge.net/projects/elks and install as the
directions specify.  The documentation on ELKS is not the best as most of
it has not been updated in a LONG time, so you'll have a lot of
experimentation to do...

----- Original Message -----
From: "ShadowRage" <shadowrage@acidchat.net>
To: <linux-8086@vger.kernel.org>
Sent: Tuesday, January 13, 2004 10:04 PM
Subject: question


> can someone give me good instructions on how to set up a good 8086
environment?
>
> --
> AcidChat IRC Network
> www.acidchat.net
> free chatrooms!
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: question

[Jody]

Assuming that you're referring to an ELKS-based environment, the best
advice at the moment that I can give is to download the "ELKS Distribution
Edition" from http://www.sourceforge.net/projects/elks and install as the
directions specify.  The documentation on ELKS is not the best as most of
it has not been updated in a LONG time, so you'll have a lot of
experimentation to do...

----- Original Message -----
From: "ShadowRage" <shadowrage@acidchat.net>
To: <linux-8086@vger.kernel.org>
Sent: Tuesday, January 13, 2004 10:04 PM
Subject: question


> can someone give me good instructions on how to set up a good 8086
environment?
>
> --
> AcidChat IRC Network
> www.acidchat.net
> free chatrooms!
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

question

[ShadowRage]

can someone give me good instructions on how to set up a good 8086 environment?

-- 
AcidChat IRC Network
www.acidchat.net
free chatrooms!

question

[emiliano]

[-- Attachment #1: Type: text/plain, Size: 502 bytes --]

Hi, could you give me some help about the question below?

 

I have  a Total Control with a private pool of IPs. I’m using IPTables with
NAT and HT23 modules. My trouble is that while I get a perfect video stream,
I’m unable to transmitt/receive audio (through the instant Messenger from
Microsoft, MSN Messenger ). 

 

Some sugestión about? I really will be greateful with you if you can give me
some idea …

 

Thanks!! 

 

Best regards

 

Emiliano Barbat

Argentina


[-- Attachment #2: Type: text/html, Size: 2684 bytes --]

RE: question

[George Vieira]

Look in the archives yet? Done a google search?

Use the H323 patch from patch-o-matic.

Thanks,
____________________________________________
George Vieira
Systems Manager
georgev@citadelcomputer.com.au

Citadel Computer Systems Pty Ltd
http://www.citadelcomputer.com.au

-----Original Message-----
From: Sander Sneekes [mailto:sander@dmdsecure.com]
Sent: Friday, June 13, 2003 6:42 AM
To: Netfilter
Subject: question


Hi all,

Small qeustion anybody have any clue howto get 
microsoft netmeeting to work from behind an iptables
firewall?

I'm able to accept a conf. en send text but no video/audio



cheers
Sander

question

[Sander Sneekes]

Hi all,

Small qeustion anybody have any clue howto get 
microsoft netmeeting to work from behind an iptables
firewall?

I'm able to accept a conf. en send text but no video/audio



cheers
Sander

Re: Question

[Harald Welte]

[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]

On Sat, May 31, 2003 at 10:01:22PM -0300, mluengo@unlp.edu.ar wrote:
> I have a Kernel 2.4.20 patched with patch-o-matic . I have the modules loaded 
> (ip_conntrack_pptp, ip_nat_pptp, ip_nat_prot_gre, and so) but my server pptpd 
> is logging: 
> "pptpd[6249]: GRE: Discarding out of order packet" if two client is connected 
> (not if only one)

Are you aware that the linux pptpd doesn't even support multiple clients
from a single ip?  This is a severe bug in pptpd, not in the netfilter
nat helper module.

Try it for yourself... make two pptp connections  from one client to the
same server, and you will end up with the same error.

You need to use a pptp server that supports multiple connections from
one IP.

> Thank you in advance.
> Miguel
-- 
- Harald Welte <laforge@gnumonks.org>               http://www.gnumonks.org/
============================================================================
Programming is like sex: One mistake and you have to support it your lifetime

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: Question

[Guido Guenther]

On Wed, Feb 05, 2003 at 08:36:24PM -0500, benyates3@comcast.net wrote:
> I'm a student and is wondering if you could  tell me what version of Linux is suitable for a SGI Indigo 2 machine?  Thanks. 
There are basically two more or less complete distributions out there:
 ftp://ftp.linux-mips.org:/pub/linux/mips/redhat
and
 http://ports.debian.org/mips
However only XL graphics is supported on the I2, Express and Impact
aren't.
 -- Guido

Question

[benyates3]

[-- Attachment #1: Type: text/plain, Size: 148 bytes --]

I'm a student and is wondering if you could  tell me what version of Linux is suitable for a SGI Indigo 2 machine?  Thanks. 
Ben Yates
443-677-2693

[-- Attachment #2: Type: text/html, Size: 514 bytes --]

question

[franck Jolimay]

Hello,

I send you an email because I have the following message
during my reboot on a redhat7.2 server:


WARNING: unexpected IO-APIC, please mail
Dec 17 16:12:08 L1_CRUNCH03 kernel:           to linux-smp@vger.kernel.org


Can you tell me the meaning of this message and is there something to do ?


 Franck Jolimay
 Senior Unix Administrator
 Oracle dba administrator

 RealMedia
 Route de la Pierre
 1024 Ecublens-Lausanne

 Email : fjolimay@realmedia.com
 Tel   : 00 41 21.69.59.743
 Fax   : 00 41 21.69.59.701
 Web   : http://www.realmedia.com

24/7 Real Media, Inc. provides marketing solutions to the digital
advertising industry. Through a suite of online marketing and technologies
services, 24/7 Real Media connects media buyers and media sellers across
multiple digital platforms and works closely with individual clients to
develop a comprehensive, customized, value-enhancing solution. The Company's
business is organized into two principal lines of business: Technology
Solutions and Integrated Media Solutions. Technology Solutions includes Open
Adstream, the Company's proprietary advertising delivery and management
suite. 24/7 Real Media also partners with other companies to offer
complementary plug-ins and modules. 24/7 Real Media connects advertisers to
high-quality audiences through its Integrated Media Solutions, which include
four products: the 24/7 Network of marquee branded Websites and niche
Websites; permission-based e-mail databases; a comprehensive promotions
suite; and a search engine results listings service.

Re: question

[Robert Love]

On Wed, 2002-12-11 at 01:35, Sipos Ferenc wrote:

> Is the new atapi cd writing method included into the 2.4 backported ac
> ide code or is it separate, if it is, then will it be ported to 2.4?

No it is not in 2.4 nor 2.4-ac.

I doubt it will be back-ported but who knows.  Linus and Jens would know
best.  And Marcelo would have to take it.

	Robert Love

question

[Sipos Ferenc]

Hi!

Is the new atapi cd writing method included into the 2.4 backported ac
ide code or is it separate, if it is, then will it be ported to 2.4?

Thx.

Paco

Re: Question

[phrostie]

it's asking for what you want to use for your C:\ drive.
currently it is pointing at a image file that does not exist called 
/var/lib/dosemu/hdimage.first .

there is a second dosemu-freedos file that needs to be installed or you can 
change the line in your .dosemu.conf to point at a valid c:\ partition.

hope that helps

On Wednesday 04 September 2002 13:48, Daniel Chavarria wrote:
> i installed the dosemu version 1.0.1
>
> the install doesn't fail but when I try to execute
> sends me the next mesage.....
>
> Error in /var/lib/dosemu/global.conf: (line 720)
> Disk-device/file /var/lib/dosemu/hdimage.first    sn't
> exist.
> 1 error(s) detected while parsing the
> configuration-file
>
>
> i go to the archive and never find the 720 line .
> culod you help me?
>
> =====
> De antemano Gracias por su Atencion
>
> Daniel Rolando Chavarria Salinas
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Finance - Get real-time stock quotes
> http://finance.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Oh, I have slipped the surly bonds of DOS,
and danced the skies on Linux silvered wings.
http://pfrostie.freeservers.com/cad-tastrafy/
http://www.freelists.org/list/cad-linux

Question

[Daniel Chavarria]

i installed the dosemu version 1.0.1

the install doesn't fail but when I try to execute
sends me the next mesage.....

Error in /var/lib/dosemu/global.conf: (line 720)
Disk-device/file /var/lib/dosemu/hdimage.first    sn't
exist.
1 error(s) detected while parsing the
configuration-file


i go to the archive and never find the 720 line .
culod you help me?

=====
De antemano Gracias por su Atencion

Daniel Rolando Chavarria Salinas

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

Re: question

[jbradford]

It unsubscribed you automatically for some reason.  Just re-subscribe, and have at look at section 3.14 of the FAQ.

> Since Friday, I didn't get any mail from the mailing list. Could anybody
> tell me what has happened? Thx.

John.

question

[Sipos Ferenc]

Hi!

Since Friday, I didn't get any mail from the mailing list. Could anybody
tell me what has happened? Thx.

Paco

Re: Question

[Stephen Smalley]

On Tue, 25 Jun 2002, Boyne, Patrick J wrote:

> I have a question regarding importing and exporting data from a SELinux
> system via the floppy drive. If a user brings data into the system from a
> floppy disk with (as an example) a non-ext[2|3] filesystem, am I correct in
> thinking that the files will be labeled with the security context of the
> directory they are filed under? If the data was labeled on a disk with an
> ext2 filesystem are those labels preserved when it is copied or is the label
> altered? Or is this policy-dependent?

Ordinary users aren't authorized to mount filesystems or access unlabeled
data by the example policy configuration.

>From the perspective of the kernel, there is no such operation as a file
copy; it merely sees the creation of a new file, reading from the old
file, and writing to the new file.  The label of the new file is
determined at creation time.  The copying process can specify the label of
the new file using the extended system calls in order to preserve the
label of the original if desired, as is done by the SELinux-modified cp
program if you use the -p option to preserve attributes.  Otherwise, the
kernel will apply the standard logic to determine the new label, either
inheriting the type from the parent directory or using the type specified
in a type transition rule.

> I'm curious about the reverse cases too; that is, exporting data. I
> appreciate any help.

If you copy files to a filesystem on a floppy that does not support
labels, then you would naturally lose the labeling information.  Of
course, mounting and accessing such a filesystem is controlled by the
policy.  If you copy files to a labeled filesystem on a floppy, then the
same discussion above applies for determining the label of the new file.

--
Stephen D. Smalley, NAI Labs
ssmalley@nai.com




--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Question

[Boyne, Patrick J]

Hello,

I have a question regarding importing and exporting data from a SELinux
system via the floppy drive. If a user brings data into the system from a
floppy disk with (as an example) a non-ext[2|3] filesystem, am I correct in
thinking that the files will be labeled with the security context of the
directory they are filed under? If the data was labeled on a disk with an
ext2 filesystem are those labels preserved when it is copied or is the label
altered? Or is this policy-dependent?

I'm curious about the reverse cases too; that is, exporting data. I
appreciate any help. 

Thanks,

> Patrick J. Boyne
> M&DS Delaware Valley Technical Operations
> 

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Question

[Ramin Alidousti]

On Sat, Jun 22, 2002 at 11:25:48AM -0400, Stephen Frost wrote:

> > > I'm not aware of anything based on IPtables which makes an effective (OSI 
> > > layer 7) IDS - it's just not designed for it, being a packet filter.....
> > 
> > There is the psd module. Check it out.
> 
> There's also my recent module, just to throw it in there. :)

Which IMHO is much _more_ powerful :-)

Ramin

> 	Stephen

Re: Question

[Stephen Frost]

[-- Attachment #1: Type: text/plain, Size: 507 bytes --]

* Jack Bowling (jbinpg@shaw.ca) wrote:
> ** Reply to message from Antony Stone <Antony@Soft-Solutions.co.uk> on Sat, 22 Jun 2002 00:12:28 +0100
> > What sort of modules ?   I *hope* you don't mean the 'string' match ?
> > 
> > I'm not aware of anything based on IPtables which makes an effective (OSI 
> > layer 7) IDS - it's just not designed for it, being a packet filter.....
> 
> There is the psd module. Check it out.

There's also my recent module, just to throw it in there. :)

	Stephen

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: Question

[Jack Bowling]

** Reply to message from Antony Stone <Antony@Soft-Solutions.co.uk> on Sat, 22 Jun 2002 00:12:28 +0100


> On Friday 21 June 2002 7:31 pm, James Mello wrote:
> 
> > > Also I'm wondering say if I have a dmz and allow people to come into a
> > > server on port 80, will netfilter inspect the packet on all 7 layers
> > > of the OSI model and make sure that it is actually a http packet and
> > > following the rules and protocol specifications of http?
> >
> > No, but there are experimental modules that will allow you to enforce
> > your own rules. I've heard of some IDS or attack detection capabilities
> > being done through IP tables.
> 
> What sort of modules ?   I *hope* you don't mean the 'string' match ?
> 
> I'm not aware of anything based on IPtables which makes an effective (OSI 
> layer 7) IDS - it's just not designed for it, being a packet filter.....

There is the psd module. Check it out.

jb

-- 
Jack Bowling
mailto: jbinpg@shaw.ca

Re: Question

[Sascha Reissner]

From: Krish Ahya

> I was just wondering, is Netfilter as good as Cisco's PIX and Checkpoint's
Firewall-1, if not better?

its hard to compare apples with pears.. one is a firewalling system..
netfilter is more or less a packet filter....

> Also I'm wondering say if I have a dmz and allow people to come into a
server on port 80, will netfilter inspect the packet on all
> 7 layers of the OSI model and make sure that it is actually a http packet
and following the rules and protocol specifications of
> http? Sorta like checkpoints INSPECT module.

as netfilter is "only" a packet filter (with some additional modules to
provide more functions) you will stick with stuff like string match and all
modules you would like to provide the netfilter community (if you code them
yourself)

Re: Question

[Antony Stone]

On Saturday 22 June 2002 12:16 am, James Mello wrote:

> > > No, but there are experimental modules that will allow you to enforce
> > > your own rules. I've heard of some IDS or attack detection
> > > capabilities being done through IP tables.
> >
> > What sort of modules ?   I *hope* you don't mean the 'string' match ?
>
> Yeah, I actually do mean the 'string' match :) I've got some friends who
> used this to do some filtering on content on their own internet exposed
> boxes to prevent stupid Nimda worm and other attacks from being
> perpetrated.

Hmmm.   Okay, I'll agree you can do a certain amount of string matching, with 
a certain degree of reliability, wiht this module, but I think for an IDS I'd 
rather go for snort / hogwash.

 

Antony.

RE: Question

[James Mello]

> > No, but there are experimental modules that will allow you 
> to enforce 
> > your own rules. I've heard of some IDS or attack detection 
> > capabilities being done through IP tables.
> 
> What sort of modules ?   I *hope* you don't mean the 'string' match ?

Yeah, I actually do mean the 'string' match :) I've got some friends who
used this to do some filtering on content on their own internet exposed
boxes to prevent stupid Nimda worm and other attacks from being
perpetrated. They *did* say it was slow, but overall it's been a pretty
effective solution for them. Note I *never* did say that you can do all
sorts of Layer 7 evaluation (or validation) like the guy said. I just
suggested this as an option to do some layer 7 filtering and content
checking...

	-- Cheers
	-- James

Re: Question

[Antony Stone]

On Friday 21 June 2002 7:31 pm, James Mello wrote:

> > Also I'm wondering say if I have a dmz and allow people to come into a
> > server on port 80, will netfilter inspect the packet on all 7 layers
> > of the OSI model and make sure that it is actually a http packet and
> > following the rules and protocol specifications of http?
>
> No, but there are experimental modules that will allow you to enforce
> your own rules. I've heard of some IDS or attack detection capabilities
> being done through IP tables.

What sort of modules ?   I *hope* you don't mean the 'string' match ?

I'm not aware of anything based on IPtables which makes an effective (OSI 
layer 7) IDS - it's just not designed for it, being a packet filter.....

 

Antony.

RE: Question

[Rowan Reid]

>>At the least it's free to try... :)

Does anyone know where to find documentation for Firewall-1 I decided to
try it once but couldn't find any documentation to save my life.

Re: Question

[Nick Drage]

On Fri, Jun 21, 2002 at 12:33:15PM -0500, Krish Ahya wrote:
> Hi all,
> 
> I was just wondering, is Netfilter as good as Cisco's PIX and Checkpoint's
> Firewall-1, if not better?

Depends what you mean by "good", which is a little too general to rate
something as complex as a firewall.  In relation to Firewall-1 it is
cheaper, it is possibly as efficient and as secure ( with the right
configuration ), configuration is more difficult IMHO... and all that
depends on the situation you're using it and the skill of the
administrators.

At the least it's free to try... :)

-- 
FunkyJesus System Administration Team

RE: Question

[James Mello]

> > Also I'm wondering say if I have a dmz and allow people to 
> come into a 
> > server on port 80, will netfilter inspect the packet on all 
> 7 layers 
> > of the OSI model and make sure that it is actually a http 
> packet and 
> > following the rules and protocol specifications of http?

No, but there are experimental modules that will allow you to enforce
your own rules. I've heard of some IDS or attack detection capabilities
being done through IP tables.

	-- Cheers
	-- James

Re: Question

[Antony Stone]

On Friday 21 June 2002 6:33 pm, Krish Ahya wrote:

> Hi all,
>
> I was just wondering, is Netfilter as good as Cisco's PIX and Checkpoint's
> Firewall-1, if not better?

Yes.

> Also I'm wondering say if I have a dmz and allow people to come into a
> server on port 80, will netfilter inspect the packet on all 7 layers of the
> OSI model and make sure that it is actually a http packet and following the
> rules and protocol specifications of http?

No.


At least one of the above answers is merely my personal opinion.

 

Antony.

Question

[Krish Ahya]

[-- Attachment #1: Type: text/plain, Size: 589 bytes --]

Hi all,

I was just wondering, is Netfilter as good as Cisco's PIX and Checkpoint's Firewall-1, if not better?

Also I'm wondering say if I have a dmz and allow people to come into a server on port 80, will netfilter inspect the packet on all 7 layers of the OSI model and make sure that it is actually a http packet and following the rules and protocol specifications of http? Sorta like checkpoints INSPECT module.

Thanks.

- Krish
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
I have not failed 10,000 times, I have sucessfully found 10,000 ways that won't work." -- Thomas A. Edison

[-- Attachment #2: Type: text/html, Size: 1318 bytes --]

Re: Question

[Earle Nietzel]

This message merely hints that it is possible that the EBDA or XBDA 
(Extended Bios Data Area) can be written to which just so happens to be 
where the MP table is located during boot. Once your system is booted then 
the EBDA is no longer available and the MP table has been read by the OS.

So I assume if you boot fine then all is good!!! Also I am told that if you 
use a compressed kernel then this should never be a problem.


At 10:50 PM 6/17/2002, mmacdonald@symcor.com wrote:
>Not sure why it says to contact you but here goes.  Do you know what is
>causing this and how I can correct it?
>
> 
>
>  Jun 17 13:30:43 arccom01 kernel: WARNING: MP table in the EBDA can be 
> UNSAFE, contact
>  linux-smp@vger.kernel.org if you experience SMP 
> problems!
> 
>
> 
>
> 
>
>
>
>Any help would be appreciated.
>
>Mike Macdonald
>Mid-Range Systems
>Unix Administrator
>Phone: 416-591-9186
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-smp" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

Question

[mmacdonald]

Not sure why it says to contact you but here goes.  Do you know what is
causing this and how I can correct it?

                                                                                                    
 Jun 17 13:30:43 arccom01 kernel: WARNING: MP table in the EBDA can be UNSAFE, contact              
 linux-smp@vger.kernel.org if you experience SMP problems!                                          
                                                                                                    
                                                                                                    
                                                                                                    


Any help would be appreciated.

Mike Macdonald
Mid-Range Systems
Unix Administrator
Phone: 416-591-9186

question

[jimmy keffer]

i have a working ppp connection on redhat i did with rp3 i can bring
it up and down with ifup ppp0 and ifdown i have diald 1.01 installed
but i need ppp-on and off files also i have no /etc/diald dir they
talk about in the docs also i had no diald.conf i got one from the net
but im lost help please my modem is /dev/modem
thanks
jimmy

Re: Question

[Stephen Smalley]

On 19 Dec 2001, Justin Smith wrote:

> Is there a simple way to determine whether the system is in enforcing or
> permissive mode (other than issuing the avc_toggle command twice)?

Not currently.  We originally created the Development option and
avc_toggle with the intent of only using it for the development of
security policy configurations, expecting that one would build a kernel
without the option for operational use once the desired policy
configuration had been developed.  However, some people may choose to
always use a kernel with this option enabled and use avc_toggle in an rc
script to switch into enforcing mode during initialization so that they
can revert to permissive mode later from an authorized domain.  In that
situation, I can see that it would be useful to be able to determine
whether the kernel is currently permissive or enforcing.  Curiously, I
received this same question via private email from another person earlier
this week.

I suppose that we can add this to our TODO list.  It should be quite
trivial.

--
Stephen D. Smalley, NAI Labs
ssmalley@nai.com






--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Question

[Justin Smith]

Is there a simple way to determine whether the system is in enforcing or
permissive mode (other than issuing the avc_toggle command twice)?
-- 


--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Question

[C.Praveen]

Hello,

i have a very simple question.
please CC any reply to me, since im not subscribed to the list


On the same processor i have the following code (initially a = 0)

1. write a = 1
2. read b

if an interrupt occurred after line 1 and before line 2, and that ISR
reads the value of a, is there a chance it can see the value of a as 0?
Hope the question isnt too stupid, but the processor can buffer stores to
memory ? (Does it supply the correct value of a to the isr if it does). if
not, mb wont solve the problem i suppose? its meant for other cpus ?

Thanks,

Praveen C

Question

[Krishnan Ananthanarayanan]

Hi,
  I was wondering if there is any mechanism to notify a module of an event
such as arrival of data on a socket. I am trying to find out if a function
in a module can be invoked if such an event occurs. This solves the
problem of polling the socket for data.

Thanks a ton in advance.
Krishnan.

Question...

[Alberio Bathory-Frota]

I was wondering what the difference between wake_up_process and
wake_up_process_synchronous is?

Thanks for your input,
Alberio.

Re: Question

[David S. Miller]

   From: "S. Ashbrook" <ashbrook@crosswinds.net>
   Date:   Wed, 1 Sep 1999 15:36:19 +400

   is this still an active project?
   I recently installed the 1.1.9 version and like it.
   But i see its based on the RH5.2 and was wondering if a new release is planned
   and if it will be based on RH6.0.

RH6.0 supports UltraSparc

Later,
David S. Miller
davem@redhat.com

Re: Question

[Peter Jones]

On Wed, 1 Sep 1999, S. Ashbrook wrote:

> is this still an active project?
> I recently installed the 1.1.9 version and like it.
> But i see its based on the RH5.2 and was wondering if a new release is planned
> and if it will be based on RH6.0.
> Thanks,

UltraPenguin is no longer active, no.  Most of the changes between 5.2 and
UltraPenguin 1.1.9 got merged into the 6.0 release, and it was decided by
the UltraPenguin maintainers that it would be pointless to continue
seperate development efforts, so current development is against RH 6.0 .

 -- Peter

"This entire opus is respectfully dedicated to all those who have
loved unconditionally only to have their hearts unanaesthetically
ripped out: base not your joy upon the deeds of others, for what
is given may be taken away."
		-- Steele

Question

[S. Ashbrook]

is this still an active project?
I recently installed the 1.1.9 version and like it.
But i see its based on the RH5.2 and was wondering if a new release is planned
and if it will be based on RH6.0.
Thanks,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~     A live Dog is better than a Dead Lion     ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

question

[David S. Miller]

http://www-add.engr.sgi.com/nsd/htmls/prodmkt/HP_NET/100BT.html#100Base-TforIndy

Are any of these available for INDY yet?  If so, I'd like to write a
driver for one under Linux and see if we can get the _real_ world
record for over the wire tcp latency on _real_ hardware, an SGI
machine.

Oh btw, userland is coming along.  I'll post a progress report
sometime soon...

dm@engr.sgi.com

'Ooohh.. "FreeBSD is faster over loopback, when compared to
Linux over the wire". Film at 11.' -Linus

Re: question

[David S. Miller]

   From: "Christopher W. Carlson" <carlson@heaven.newport.sgi.com>
   Date: Mon, 3 Jun 1996 10:46:26 -0700

   For future reference, you might want to check out
   http://www.asd.sgi.com/bbon/, which is the SGI Big Book Of Names -
   definitions for all of our acronyms.

Thanks.

Later,
David S. Miller
dm@engr.sgi.com

Re: question

[Christopher W. Carlson]

On Jun 1,  8:46pm, David S. Miller wrote:
> Subject: question
>
> I understand what all the IP?? things are, but what is the IO4?
>
> Later,
> David S. Miller
> dm@sgi.com
>-- End of excerpt from David S. Miller


David,

For future reference, you might want to check out
http://www.asd.sgi.com/bbon/, which is the SGI Big Book Of Names -
definitions for all of our acronyms.

-- 

		Chris Carlson

	+------------------------------------------------------+
	| Also, carlson@sgi.com                                |
	|   Work:       (714) 756-5976     SGI vmail:  x5-8095 |
	|   FAX:        (714) 833-9503                         |
	+------------------------------------------------------+

Re: question

[William J. Earl]

David S. Miller writes:
 > 
 > I understand what all the IP?? things are, but what is the IO4?

      IO4 is part of the I/O system on Challenge L and XL ("Everest", "IP19")
systems.

question

[David S. Miller]

I understand what all the IP?? things are, but what is the IO4?

Later,
David S. Miller
dm@sgi.com