[ LUGOS ] linux bridge
Borut Rozman
jedo na zipp.nu
Pet Nov 3 17:29:57 CET 2000
Pozdravljeni!
Trenutno se ukvarjam z LinuxBridgem na Mašini Slack 7.0 z kernelom 2.2.17
Iz neta sem potegnil tudi patch za kernel (bridge) vendar pa ne morem
popatchati Sourca?
napaka ki jo javi če dam -f opcijo
pyro:/usr/src/linux# patch < /bridge-0.0.7-against-2.2.17.diff -f
patching file CREDITS
Hunk #1 succeeded at 342 with fuzz 2 (offset 35 lines).
can't find file to patch at input line 21
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/Documentation/Configure.help
linux-2.2.17br0.0.7/Documentation/Configure.help
|--- linux-2.2.17/Documentation/Configure.help Mon Sep 4 19:39:15 2000
|+++ linux-2.2.17br0.0.7/Documentation/Configure.help Tue Sep 26 19:25:11
2000
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file bridge.txt,
which already exists! Applying it anyway.
patching file bridge.txt
Patch attempted to create file bridge.txt, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file bridge.txt.rej
patching file MAINTAINERS
Hunk #1 succeeded at 351 with fuzz 1 (offset 14 lines).
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
The next patch would create the file if_bridge.h,
which already exists! Applying it anyway.
patching file if_bridge.h
Patch attempted to create file if_bridge.h, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file if_bridge.h.rej
can't find file to patch at input line 219
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/include/linux/netdevice.h
linux-2.2.17br0.0.7/include/linux/netdevice.h
|--- linux-2.2.17/include/linux/netdevice.h Tue Jan 4 19:12:25 2000
|+++ linux-2.2.17br0.0.7/include/linux/netdevice.h Tue Sep 26 19:25:11
2000
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 242
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/include/linux/skbuff.h
linux-2.2.17br0.0.7/include/linux/skbuff.h
|--- linux-2.2.17/include/linux/skbuff.h Thu May 13 19:33:17 1999
|+++ linux-2.2.17br0.0.7/include/linux/skbuff.h Tue Sep 26 19:25:11 2000
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file br.h,
which does not exist! Applying it anyway.
can't find file to patch at input line 253
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/include/net/br.h
linux-2.2.17br0.0.7/include/net/br.h
|--- linux-2.2.17/include/net/br.h Thu May 4 02:16:52 2000
|+++ linux-2.2.17br0.0.7/include/net/br.h Thu Jan 1 01:00:00 1970
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 588
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/Changes linux-2.2.17br0.0.7/net/Changes
|--- linux-2.2.17/net/Changes Sun Jun 7 19:37:42 1998
|+++ linux-2.2.17br0.0.7/net/Changes Tue Sep 26 19:25:11 2000
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 599
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/Config.in linux-2.2.17br0.0.7/net/Config.in
|--- linux-2.2.17/net/Config.in Tue Jan 4 19:12:26 2000
|+++ linux-2.2.17br0.0.7/net/Config.in Tue Sep 26 21:32:40 2000
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
patching file Makefile
Hunk #1 FAILED at 59.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
patching file README
Hunk #1 FAILED at 7.
1 out of 1 hunk FAILED -- saving rejects to file README.rej
patching file Makefile
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 7.
2 out of 2 hunks FAILED -- saving rejects to file Makefile.rej
can't find file to patch at input line 677
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/bridge/br.c linux-2.2.17br0.0.7/net/bridge/br.c
|--- linux-2.2.17/net/bridge/br.c Mon Sep 4 19:39:29 2000
|+++ linux-2.2.17br0.0.7/net/bridge/br.c Tue Sep 26 19:34:31 2000
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file br_device.c,
which already exists! Applying it anyway.
patching file br_device.c
Patch attempted to create file br_device.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_device.c.rej
The next patch would create the file br_fdb.c,
which already exists! Applying it anyway.
patching file br_fdb.c
Patch attempted to create file br_fdb.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_fdb.c.rej
The next patch would create the file br_forward.c,
which already exists! Applying it anyway.
patching file br_forward.c
Patch attempted to create file br_forward.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_forward.c.rej
The next patch would create the file br_if.c,
which already exists! Applying it anyway.
patching file br_if.c
Patch attempted to create file br_if.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_if.c.rej
The next patch would create the file br_input.c,
which already exists! Applying it anyway.
patching file br_input.c
Patch attempted to create file br_input.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_input.c.rej
The next patch would create the file br_ioctl.c,
which already exists! Applying it anyway.
patching file br_ioctl.c
Patch attempted to create file br_ioctl.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_ioctl.c.rej
The next patch would create the file br_notify.c,
which already exists! Applying it anyway.
patching file br_notify.c
Patch attempted to create file br_notify.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_notify.c.rej
The next patch would create the file br_private.h,
which already exists! Applying it anyway.
patching file br_private.h
Patch attempted to create file br_private.h, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_private.h.rej
The next patch would create the file br_private_stp.h,
which already exists! Applying it anyway.
patching file br_private_stp.h
Patch attempted to create file br_private_stp.h, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_private_stp.h.rej
The next patch would create the file br_stp.c,
which already exists! Applying it anyway.
patching file br_stp.c
Patch attempted to create file br_stp.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_stp.c.rej
The next patch would create the file br_stp_bpdu.c,
which already exists! Applying it anyway.
patching file br_stp_bpdu.c
Patch attempted to create file br_stp_bpdu.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_stp_bpdu.c.rej
The next patch would create the file br_stp_if.c,
which already exists! Applying it anyway.
patching file br_stp_if.c
Patch attempted to create file br_stp_if.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_stp_if.c.rej
The next patch would create the file br_stp_timer.c,
which already exists! Applying it anyway.
patching file br_stp_timer.c
Patch attempted to create file br_stp_timer.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file br_stp_timer.c.rej
The next patch would delete the file br_tree.c,
which does not exist! Applying it anyway.
can't find file to patch at input line 6186
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/bridge/br_tree.c
linux-2.2.17br0.0.7/net/bridge/br_tree.c
|--- linux-2.2.17/net/bridge/br_tree.c Tue Jan 4 19:12:26 2000
|+++ linux-2.2.17br0.0.7/net/bridge/br_tree.c Thu Jan 1 01:00:00 1970
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file sysctl_net_bridge.c,
which does not exist! Applying it anyway.
can't find file to patch at input line 6691
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/bridge/sysctl_net_bridge.c
linux-2.2.17br0.0.7/net/bridge/sysctl_net_bridge.c
|--- linux-2.2.17/net/bridge/sysctl_net_bridge.c Mon Jun 3 11:42:41
1996
|+++ linux-2.2.17br0.0.7/net/bridge/sysctl_net_bridge.c Thu Jan 1 01:00:00
1970
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 6708
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/core/dev.c linux-2.2.17br0.0.7/net/core/dev.c
|--- linux-2.2.17/net/core/dev.c Mon Sep 4 19:39:29 2000
|+++ linux-2.2.17br0.0.7/net/core/dev.c Tue Sep 26 19:25:11 2000
--------------------------
No file to patch. Skipping patch.
7 out of 7 hunks ignored
can't find file to patch at input line 6889
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/core/skbuff.c
linux-2.2.17br0.0.7/net/core/skbuff.c
|--- linux-2.2.17/net/core/skbuff.c Sun Mar 7 19:12:18 1999
|+++ linux-2.2.17br0.0.7/net/core/skbuff.c Tue Sep 26 19:25:11 2000
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 6900
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/ipv4/af_inet.c
linux-2.2.17br0.0.7/net/ipv4/af_inet.c
|--- linux-2.2.17/net/ipv4/af_inet.c Mon Sep 4 19:39:29 2000
|+++ linux-2.2.17br0.0.7/net/ipv4/af_inet.c Tue Sep 26 19:25:11 2000
--------------------------
No file to patch. Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 6942
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/netsyms.c linux-2.2.17br0.0.7/net/netsyms.c
|--- linux-2.2.17/net/netsyms.c Wed Jun 7 23:26:44 2000
|+++ linux-2.2.17br0.0.7/net/netsyms.c Tue Sep 26 21:04:00 2000
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 6970
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/packet/af_packet.c
linux-2.2.17br0.0.7/net/packet/af_packet.c
|--- linux-2.2.17/net/packet/af_packet.c Thu May 4 02:16:54 2000
|+++ linux-2.2.17br0.0.7/net/packet/af_packet.c Tue Sep 26 19:25:11 2000
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 7009
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.2.17/net/sysctl_net.c
linux-2.2.17br0.0.7/net/sysctl_net.c
|--- linux-2.2.17/net/sysctl_net.c Sun Nov 30 23:00:40 1997
|+++ linux-2.2.17br0.0.7/net/sysctl_net.c Tue Sep 26 19:25:11 2000
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
kot da bi bil kernel napačen, oziroma ne patcham pravilno kernela ?
any ideas?
lp Borut
Dodatne informacije o seznamu Starilist