Re: [leaf-user] Kernel compilation errors
Thomas At 23:01 24.09.2003 +0200, Thomas Wille wrote: Erich, I did all the things I normally do when compiling a new kernel: - untar the kernel (in this case into my home dirctory) - as root adjust the link /usr/src/linux so that it points to the kernel source to be compiled - exit from beeing root (in my home directory the user can do everything) - edit the config file by menuconfig (in this case I took Jaques' original config file) - make dep - make clean - make bzImage While doing this step the mentioned error messages occured. I see, I just did not grok your statement 'compiling grsecurity' but there is another error message in the middle of the compiling process: md5sum: kann hfc_pci. nicht öffnen (cannot open hfc_pci.) md5sum: kann hfc_pci nicht öffnen (cannot open hfc_pci) Looks like it cannot be found in the path. maybe these error message give a hint to the problem, even if hfc_pci belongs to the hisax-module. Which IIRC is enabled in the Bering config. Would it be better to download the original 2.4.20 kernel source and apply the patches myself? That's what I did. It's worth a try, even with an unpatched kernel source. That way you can easily verify your environment. The unpatched kernel source is a good reference point to start from. ... PS: error messages while making modules: make -C maps modules You wrote your own makefile, didn't you? make[3]: Entering directory /proline/lrp_nfs/Bering1.2/linux-bering-1.2/drivers/mtd/maps' gcc -D__KERNEL__ -I/proline/lrp_nfs/Bering1.2/linux-bering-1.2/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i486 -DMODULE -nostdinc -iwithprefix include -DKBUILD_BASENAME=dilnetpc -c -o dilnetpc.o dilnetpc.c Are you trying to cross compile for that hardware? There are probably a few quirks to the make environment to be done. dilnetpc.c:374: ONFIG_MTD_DILNETPC_BOOTSIZE' undeclared here (not in a function) Weird, it looks like there is an empty or undefined $C variable. It eats the uppercase C in the declaration? HTH Erich THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] openssh 3.7.1p1
At 18:48 24.09.2003 -0300, Brian Fisher wrote: Hi All, I have updated my bering with the new ssh suite. Here's a bug that I want to pass along. I use putty to ssh into my bering box and all is good except when I want to 'break' or end a command. for example, if I start to ping an ip and then want to stop the ping I would just use 'ctrl-c' but that command now closes the ssh window ! Has anyone ran into this problem ? Yep, no solution yet... sorry I attributed it to my old environment (RC3) but apparently that is not the case. I had difficulties to run ssh on the system itself to get one hop further. The host key of the remote machine was not recognised valid anymore. Erich THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] openssh 3.7.1p1
On Wed, 2003-09-24 at 14:48, Brian Fisher wrote: Hi All, I have updated my bering with the new ssh suite. Here's a bug that I want to pass along. I use putty to ssh into my bering box and all is good except when I want to 'break' or end a command. for example, if I start to ping an ip and then want to stop the ping I would just use 'ctrl-c' but that command now closes the ssh window ! Has anyone ran into this problem ? I recently reported this problem when Superfreeswan was activated in Bering 1.2. I suspect changing stty settings will fix the unintentionally aborted ssh shell. Where are stty settings located in Bering? Thanks, Stephen --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] openssh 3.7.1p1
Le Jeudi 25 Septembre 2003 09:07, Stephen Lee a écrit : On Wed, 2003-09-24 at 14:48, Brian Fisher wrote: Hi All, I have updated my bering with the new ssh suite. Here's a bug that I want to pass along. I use putty to ssh into my bering box and all is good except when I want to 'break' or end a command. for example, if I start to ping an ip and then want to stop the ping I would just use 'ctrl-c' but that command now closes the ssh window ! Has anyone ran into this problem ? I recently reported this problem when Superfreeswan was activated in Bering 1.2. I suspect changing stty settings will fix the unintentionally aborted ssh shell. Where are stty settings located in Bering? 1/ stty setting are set in /etc/profile (or /root/.profile) 2/ This problem occured the first time with openssh 3.6.1 See my mail on this: http://sourceforge.net/mailarchive/message.php?msg_id=4480281 That is why at that time I went back to 3.5p1 If someone can provide a fix let us know. I do not have much time currently. Otherwise I will apply the latest security patch to 3.5p1 until a solution is found. Jacques --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[leaf-user] Dachstein, 2 internal nets routing
All, It shouldn't be this hard. All I'm trying to do is route between my two internal networks of 192.168.1.0 and 192.168.2.0. Here is what I have: INTERN_NET=192.168.1.0/24 192.168.2.0/24 eth1_ROUTES=192.168.2.0/24_via_192.168.2.254 eth2_ROUTES=192.168.1.0/24_via_192.168.1.254 eth1 is the 192.168.1.0 network, eth2 is the other one. I can ping 192.168.1.254 from the 192.168.2.0 network and also 192.168.2.254 from the 192.168.1.0 network, but no other addresses on the opposite internal networks. Connections to the outside world, through eth0, work fine. I must be missing something, it's got me stumped. Thanks for the help, Mark --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] Dachstein, 2 internal nets routing
On Thu, 2003-09-25 at 21:37, Mark Bynum wrote: All, It shouldn't be this hard. All I'm trying to do is route between my two internal networks of 192.168.1.0 and 192.168.2.0. Here is what I have: INTERN_NET=192.168.1.0/24 192.168.2.0/24 eth1_ROUTES=192.168.2.0/24_via_192.168.2.254 eth2_ROUTES=192.168.1.0/24_via_192.168.1.254 eth1 is the 192.168.1.0 network, eth2 is the other one. I can ping 192.168.1.254 from the 192.168.2.0 network and also 192.168.2.254 from the 192.168.1.0 network, but no other addresses on the opposite internal networks. Connections to the outside world, through eth0, work fine. Don't use Dachstein, but the eth1 route can't go through 192.168.2.254 since 192.168.2.254 isn't on the 192.168.1.0 network. You need something like eth1_ROUTES=192.168.2.0/24_via_192.168.1.254 eth2_ROUTES=192.168.1.0/24_via_192.168.2.254 don't you? I must be missing something, it's got me stumped. Thanks for the help, Mark -Richard --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
