search for: config_dummi

Displaying 20 results from an estimated 74 matches for "config_dummi".

Did you mean: config_dummy
2005 May 02
1
[PATCH] config_xen0_tun.patch
QEMU needs CONFIG_TUN to enable networking. Signed-off-by: Edwin Zhai <edwin.zhai@intel.com> Signed-off-by: Arun Sharma <arun.sharma@intel.com> --- 1.56/linux-2.6.11-xen-sparse/arch/xen/configs/xen0_defconfig_x86_32 2005-04-13 15:38:59 -07:00 +++ edited/xen0_defconfig_x86_32 2005-05-02 13:18:14 -07:00 @@ -598,7 +598,7 @@ # CONFIG_DUMMY is not set # CONFIG_BONDING is not set #
2002 Nov 21
2
TINC (vpn daemon) has stopped working after compiling kernel
Hi folks, after recompiling of kernel (need quota support), tinc daemon has stopped working. Messages from log file are: ... Nov 21 14:45:02 m61 tinc.sunnet[326]: tincd 1.0pre7 starting Nov 21 14:45:02 m61 tinc.sunnet[326]: /dev/net/tun is a Linux ethertap device Nov 21 14:45:02 m61 tinc.sunnet[326]: Process 327 (tinc-up) exited with non-zero status 255 Nov 21 14:45:02 m61 tinc.sunnet[326]:
2000 Feb 21
0
Kernel Error due to long filenames??
We're running a PIII550, 128 MB, 3com 3c905b-TX with SuSE Linux 6.3; Kernel 2.2.14 (see file kernelconfig) and Samba 2.0.6 as PDC & Fileserver in a hospital. Now we got the following error: Feb 18 14:39:54 file kernel: Unable to handle kernel paging request at virtual address 00110004 Feb 18 14:39:54 file kernel: current->tss.cr3 = 040ab000, %cr3 = 040ab000 Feb 18 14:39:54 file kernel:
2001 Oct 27
3
Strange memory stats with 2.4.13 and ext3
Hi, My gateway/firewall/mailserver machine has been running 2.4.13 for a day or so now. Its basically a stock Linus kernel + ext3-0.9.13 patch (for -pre6, with the rej fixed). I'm getting this in /proc/meminfo: total: used: free: shared: buffers: cached: Mem: 130179072 117489664 12689408 0 46854144 69632 Swap: 1073987584 10907648 1063079936 MemTotal: 127128
2005 Dec 06
0
Compile time errors on xen 2.6.12.5
Here are the relevant details. all help is greatly appreciated. xenbox linux # uname -a Linux xenbox.localhost 2.6.14-gentoo-r2 #2 Mon Dec 5 16:17:58 Local time zone must be set--see zic manua x86_64 Intel(R) Xeon(TM) CPU 3.00GHzGenuineIntel GNU/Linux xenbox linux # lspci 0000:00:00.0 Host bridge: Intel Corporation E7520 Memory Controller Hub (rev 0c) 0000:00:00.1 Class ff00: Intel Corporation
2004 Jul 26
5
IP ROUTE
Hello, my linux show me that: server2 root # ip route add default scope global nexthop via 192.168.5.1 dev eth2 weight 1 nexthop via 192.168.160.1 dev eth0 weight 1 RTNETLINK answers: Invalid argument What can I do???? Thanks Matias --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.726 / Virus Database: 481 - Release Date:
2001 Aug 18
2
ext3 0.9.6 for kernel 2.4.9
This is just a rediff and retest - no ext3 changes in this release. http://www.uow.edu.au/~andrewm/linux/ext3/ The latest diff is against linux-2.4.9. The version of ext3 in -ac kernels is current. -ac's ext3 has the "buffer tracing" debug code removed from the non-ext3 files, so the 2.4.9 diff is more useful for bug hunting. I should generate a diff against -ac to enable
2005 Apr 12
0
Syslinux on USB initrd problem
Hi! Im currently trying to encrypt my harddrive and plan to boot it of a USB memory stick. Im using loop-aes to do the real work but Im having the hardest time getting syslinux to mount my initrd. Im not sure what information you need but Ill give a bit of it. VFS unable to mount root-fs on unknow-block(1,0) is the error I get. I think there was a Kernel Panic attached somewhere on there as
2002 Apr 22
3
[PATCH] open files in kjounald
Hello everybody! As I wrote in my mail the previous week ("BUG: 2.4.19pre1 & journal_thread & open filehandles") I followed the problem a little bit further. Here's my patch; I beg the ext3-maintainers (Stephen, Andreas, Andrew) to have a look at it and submit it to Marcelo and Linux for inclusion. (2.4 is for now for me more important than 2.5). Patch ----- On every
2005 Apr 13
0
Sv: Syslinux on USB initrd problem
Is there noone who has any ideas? Ive searched google like crazy but cant find any good information... Any tips on where else I could find information? ----Ursprungligt meddelande---- Fr?n: gabriel.j at telia.com Datum: Apr 12, 2005 2:36:24 PM Till: syslinux at zytor.com ?rende: [syslinux] Syslinux on USB initrd problem Hi! Im currently trying to encrypt my harddrive and plan to boot it of a
2010 Jan 27
9
[Bridge] [PATCH 0/3 v3] macvtap driver
This is the third version of the macvtap device driver, following another major restructuring and a lot of bug fixes: * Change macvtap to be based around a struct sock * macvtap: fix initialization * return 0 to netlink * don't use rcu for q->file and q->vlan pointers * macvtap: checkpatch.pl fixes * macvtap: fix tun IFF flags * Use a struct socket to make tx flow control work * disable
2010 Jan 27
9
[Bridge] [PATCH 0/3 v3] macvtap driver
This is the third version of the macvtap device driver, following another major restructuring and a lot of bug fixes: * Change macvtap to be based around a struct sock * macvtap: fix initialization * return 0 to netlink * don't use rcu for q->file and q->vlan pointers * macvtap: checkpatch.pl fixes * macvtap: fix tun IFF flags * Use a struct socket to make tx flow control work * disable
2010 Jan 27
9
[Bridge] [PATCH 0/3 v3] macvtap driver
This is the third version of the macvtap device driver, following another major restructuring and a lot of bug fixes: * Change macvtap to be based around a struct sock * macvtap: fix initialization * return 0 to netlink * don't use rcu for q->file and q->vlan pointers * macvtap: checkpatch.pl fixes * macvtap: fix tun IFF flags * Use a struct socket to make tx flow control work * disable
2005 Apr 13
1
Sv: Re: Sv: Re: Sv: Syslinux on USB initrd problem
Ive done a new initrd but got the exact same error. Should rootfs really be minix? initrd is ext2. ----Ursprungligt meddelande---- Fr?n: jbebel at ncsu.edu Datum: Apr 13, 2005 11:58:26 PM Till: gabriel <gabriel.j at telia.com> ?rende: Re: Sv: Re: Sv: [syslinux] Syslinux on USB initrd problem I've got some really old instructions on creating an initrd up at
2005 Dec 15
3
VIA sata + Xen 3.0 boot lockup problems
Hello! I`m trying to boot a via sata machine with xen 3.0 with no sucess. It just freezes at this point: ********* ACPI: PCI Interrupt 0000:00:0f.0[B] -> Link [LNKB] -> GSI 10 (level,low) -> IRQ 10 sata_via (0000:00:0f.0): routed to hard irq line 10 ata1: SATA max UDMA/133 cmd 0xEFE0 ctl 0xEFAE bmdma 0xEF90 irq 10 ata2: SATA max UDMA/133 cmd 0xEFA0 ctl 0xEFAA bmdma 0xEF98 irq 10 ata1:
2002 Jul 18
0
Fwd: oops with 2.4.18 and preempt patch, on SMP + ext3 machine
I sent this report sometime ago to l-k and to the preempt-patch maintainer, but omitted to send a copy here, where some people could have clues about the problem - so here it is: ----- Forwarded message ----- To: linux-kernel@vger.kernel.org, Robert Love <rml@tech9.net> Subject: oops with 2.4.18 and preempt patch, on SMP + ext3 machine Coming back home tonight, I found my machine in a bad
2004 Mar 27
0
Oops with md/ext3 on 2.4.25 on alpha architecture
HI list! We regularly experience kernel Ooops on our alpha SX164 with ext3 on md on ide controller: No modules loaded, lsmod empty, self compiled kernel ksymoops 2.4.5 on alpha 2.4.25. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.25/ (default) -m /boot/System.map-2.4.25 (default) Warning: You did not tell me where
2009 Dec 03
3
[RFC 0/2] macvtap, second try
I did not get this ready for the merge window, but people asked what the status of this is so I'm posting it now to solicit feedback. The first patch just adds some hooks into macvlan.c and is less invasive than the previous version. That part should be fine and I'd like this to get merged into macvlan for 2.6.33 if people agree that the approach is right. The second patch adds the
2009 Dec 03
3
[RFC 0/2] macvtap, second try
I did not get this ready for the merge window, but people asked what the status of this is so I'm posting it now to solicit feedback. The first patch just adds some hooks into macvlan.c and is less invasive than the previous version. That part should be fine and I'd like this to get merged into macvlan for 2.6.33 if people agree that the approach is right. The second patch adds the
2009 Dec 03
3
[RFC 0/2] macvtap, second try
I did not get this ready for the merge window, but people asked what the status of this is so I'm posting it now to solicit feedback. The first patch just adds some hooks into macvlan.c and is less invasive than the previous version. That part should be fine and I'd like this to get merged into macvlan for 2.6.33 if people agree that the approach is right. The second patch adds the