Socket question? Network unreachable
I have a simple socket program. I've compiled it with gcc on Debian 1.1 (kernel 2.0.29) and Red Had (Biltmore 2.0.30) and I keep getting Network is unreachable. Running gdb reveals the connect call is not working. After stepping over the connect, errno = 101. Network is unreachable is displayed by perror and the program exits. This is a small program that runs fine under SunOS 4.1.3. The only thing I had to do to the program was change the include paths from sys/ to linux/. My Linux box IP 140.117.43.69 Netmask 255.255.224.0 Network 140.117.32.0 Broadcast 140.117.63.225 Can anyone give me a clue as to what the problem might be. I don't know what to look for at the moment. The only thing I can think of is the above IPs are not correct. I can ping and telnet to the target which has the server this socket program is to connect to. I look in the arp table and it has a complete entry. Would arp be able to figure out everything if the above IPs we not right? Thanks in advance for any advice. Brian -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: porting machines
I just received a Atari Falcon 030. Will the debian 68k distribution work on this machine? Anyone else out there using an Atari? Thanks, Brian -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Help! Messed up my MBR (PROBLEM SOLVED!!!)
Thanks goes out to all who responded to my plea for help. After reading everyones mail and falling back to a phrase we use in the Military when all else fails, read the instructions! I have my P90 back up and going again! I checked out my boot directory and found the following files: boot.0300 boot.0301 boot.0341 The date on boot.0300 was time stamped with the time I had a brain cramp and executed lilo on the wrong machine. I felt pretty confident that issueing /sbin/lilo -u /dev/hda would take care of the boot sector. I ran the above command and all went well! Now came the time to repair the damage done to /dev/hda1. The time on boot.0301 looked like the time I tried to make the most of my mistake and get lilo to boot my linux partition on /dev/hdb1, except I fat fingered my lilo.conf and set boot=/dev/hda1 which messed up some partition information I guess. Next I ran /sbin/lilo -u /dev/hda1 I got a message saying that the time stamp of the file didn't match the time stamp written to /dev/hda1 and told me to use the -U option if I knew what I was doing! By now I have nothing to loose. The time stamp looked good on boot.0301 so I took a bet that this contained the status of /dev/hda1 before I started mucking around with everything trying to get lilo to boot linux on /dev/hdb1. I went for it and ran /sbin/lilo -U /dev/hda1. Several messages displayed saying that the records were restored ... said a little prayer and hit CTRL_ALT_DEL. I never thought I'd be so glad to see the words Starting MSDOS! My hat goes off to the people who are in charge of the lilo program. I did not use dd to back up the contents and I am glad that lilo saves the FIRST change of a device to a file for you! Now I understand the importance of doing this with dd and I have learned a great deal in this experience! I would not have cared if this machine was not my machine at work. We have some software on here that our IT dept. is in charge of and they would have had to come in and wipe my disk clean and reinstall their standard client software and charge our group bucks to do so. Not to mention that I (a Software Engineer) would have to explain how I did such a foolish thing. Thanks again to all who responded. If any of you come through Lynchburg Virginia send me e-mail and I owe you lunch! Now I just have to figure out why the kernel I built (which got me into this mess) can't find the root file system ... Thanks again, Brian p.s. sorry for talking so long. I'm just very thankful that everything turned out well. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Help! Messed up my MBR, don't have backup!
I built a new kernel (2.0.29) and copied it from arch/i386/boot to /boot. I then made a sym link zImage-/boot/zImage. Next I ran lilo which is were I had a total brain failure. I built the kernel above on my P90 for a 386. I forgot what machine I was on when I ran lilo! I was doing all of this from a xterm on my Sun logged into my P90. Now my P90 is screwed up. Here is how my P90 is setup: /dev/hda1 Ide dos drive 500+M /dev/hdb1 Ide linux drive 130M I use a boot floppy to boot Debian Linux 1.2 on my P90. I made the boot floppy by cp /usr/src/linux/arch/i386/boot/zImage /dev/fd0. I tried using lilo to forget about my linux drive and just boot dos but I think I ended up messing things up. I tried: /etc/lilo.conf: boot=/dev/hda other=/dev/hda1 table=/dev/hda label=dos When I boot the machine I get LILO then unexpected EOF loading dos. Is there any way I can rebuild my MBR so my dos partition works again? Next time I will remember what machine I am on before I do something this stupid again. I hope I can recover from this or else I'm in trouble since my P90 is my machine at work! :( Thanks, Brian -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Help! Messed up my MBR part 2
Here is some more information on my sad state! I thought no problem, I'll just make a dos boot floppy. wrong. When I do a C: I can get to the drive but when I try to do a dir or anything I get: Invalid media type reading drive C The machine I built the kernel for (the 386) is giving me problems too. I copied the zImage to a dos formated floppy and on reboot I get: Kernel panic:VFS: Unable to mount root fs on 03:01 The 386 has a simple setup. One ide drive @120M only 1 partition /dev/hda1 /hda5 is swap. After the kernel built I copied zImage to /boot in / I made a sym link ln-s /boot/zImage . I use the following /etc/lilo.conf: /boot=/dev/hda1 /root=/dev/hda1 compact install=/boot/boot.b map=/boot/map vga=normal delay=5 image=zImage label=Linux read-only What am I doing wron on this machine? I'm not having a very productive day! :( Thanks in advance for helping me out of this one too. Brian -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: [Fwd: Virus Alert]
I called the number listed in this message it this is a joke! The statement about the tight loop that could damage your processor should be a dead give-away! Check these things out in the future before spreading them! Thanks, Brian ,---. | ERICSSON /// | | | | Brian T. Hutchinson | | Software Engineer | | Private Radio Systems | | | | Ericsson Inc. Telephone: (804)948-6442 | | Mountain View Road, Room 2630FAX: (804)948-6340 | | Lynchburg, VA 24502[EMAIL PROTECTED] | | | `---'
Can't find boot/root disks for 1.1
Hi all, I follow the links from the Debian org homepage to: ftp://ftp.debian.org/debian/Debian-1.1/disks-i386/current here I try to download root.bin, boot1440.bin etc. and I get a error from my browser saying the links are bad and it can't find the files! Could someone point me the the base disks I need to get Debian 1.1 up and running? Thanks for the help! Brian
