IP ID == 0 ?!
Hi, I've been having weird problems with 2.4 kernels ip networking. I can't connect to several sites ( hotmail.com,intel.com... ). After some investigation with tcpdump I figured that the IDentification field of every outgoing ip packet is set to zero and then it doesn't get through some few firewalls. I'm surprised I haven't found anything about it in the list archives, so I'm trying to get help here. Did I forget to configure something? Ivan Vadovic - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: PID of init != 1 when initrd with pivot_root
> > But the problem still remains. How do I make my /sbin/init run with PID 1 > > using initial ramdisk under the new root change mechanism? I don't want to > > use the old change_root mechanism... > > I had the same problem when doing some development for mkCDrec. > This project uses busybox, whose init does not run if its PID != 1. > I asked the busybox folks same question you did and never got a response. > > As a kludge, and after looking at the busybox source code, I renamed init > to linuxrc. In this case the program is functionally equivalent to init, > except that it does not do the PID == 1 check. > > An excerpt from my real linuxrc: > > echo Pivot_root: my PID is $$ > # exec /usr/sbin/chroot . /sbin/init < dev/console > dev/console 2>&1 > # Okay, try this: > exec /usr/sbin/chroot . /sbin/linuxrc < /dev/console > /dev/console 2>&1 > > /sbin/linuxrc is actually init, renamed. > I fugured it out. The Documentation/initrd.txt says to use root=/dev/rd/0 with devfs. Well, that's wrong. You should use root=/dev/ram0 even with devfs no matter what the documentation says. And my linuxrc finaly runs with PID == 1. Ivan Vadovic - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
any good diff merging utility?
Hi, I like to build kernels with a bunch of patches on top to test new stuff. The problem is that it takes a lot of effort to fix all the failed hunks during patching that really wouldn't have to be failed if only patch was a little more inteligent and could merge several patches into one ( if possible) or if could take into account already applied patches. Well, are there any utilities to merge diffs? I couldn't find any on freshmeat. So what are you using to stack many patches onto the kernel tree? Just manualy modify the diff? I'll try to write something more automatic if nothing comes up. Ivan Vadovic - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: any good diff merging utility?
> > I like to build kernels with a bunch of patches on top to test > > new stuff. The problem is that it takes a lot of effort to fix > > all the failed hunks during patching that really wouldn't have > > to be failed if only patch was a little more inteligent and > > could merge several patches into one ( if possible) or if could > > take into account already applied patches. > > The basic problem here is that the "failed hunks" are usually there > because of conflicts between the two patches in question, and as a > result, they are not as easy to merge automagically as one might at > first assume. Very often the case is that they indeed can be merged automagically. For example two patches inserting few lines right after the #include lines. patch1: @@ 10,1 10,2 @@ #include +#include <1.h> patch2: @@ 10,1 10,2 @@ #include +#include <2.h> The patch will fail to patch :-). But there is no real conflict between the patches. > > Well, are there any utilities to merge diffs? I couldn't find > > any on freshmeat. So what are you using to stack many patches > > onto the kernel tree? Just manualy modify the diff? I'll try to > > write something more automatic if nothing comes up. > > I once came across a utility called "diff3" that was designed to take > a patch for one version of a package and create an equivalent patch > for another version of the same package, but I haven't been able to > find it again since my hard drive crashed. diff3 comes from gnu diffutils <ftp://ftp.gnu.org/gnu/diffutils/diffutils-2.7.tar.gz>. But all it does is comparing three FILES for differencies. Ivan Vadovic - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/