Re: FC4 Base installed -- no dhcp
- From: Stefan Patric <tootek2@xxxxxxxxx>
- Date: Thu, 16 Aug 2007 02:17:16 GMT
On Wed, 15 Aug 2007 10:17:21 -0700, ernobe wrote:
On Aug 15, 1:14 am, Stefan Patric <toot...@xxxxxxxxx> wrote:
Anyway, the install took care of setting up the LAN and Internet, andI don't think YRC.
the yum repository configs. I just answered a few simple questions,
and I was up and running. Took, maybe, 20 minutes. Maybe you should
just re- install from the standard FC4 Install CDs, instead what you're
doing now.
Also, FC4 uses the 2.4 kernel, IIRC. So, if you develop your compiler
under it, it won't run on current 2.6 kernel systems. And, your code
for the compiler, which compiles just fine with the 2.4 headers,
probably won't under the 2.6 ones. There were LOTS of changes between
2.4 and 2.6 in the kernel itself as well as header files. I don't even
know if FC4 will run under the 2.6 kernel, even if you upgrade to it.
You're correct. I checked. FC4 comes with the 2.6 kernel by default.
So does FC3 for that matter. So, if you have any problems compiling and
running your compiler on other 2.6 Linux systems, it shouldn't be becasue
of the kernel.
My system didn't seem to be a core one when first installed because in
the yum repositories there were no files named core, nor any file with a
[core] heading in it. There was fedora.repo, and the first line of it
was [base], so I thought that the rinse program, which did the
installation, worked similar to the debootstrap program, which
automatically downloads and installs all the base packages for a Debian
system on a mounted partition. All you have to do then is add an
/etc/fstab file, edit the hostname and networking files according to
your setup, add /etc/lilo.conf, do a chroot into it and run lilo, and
boot into it. Fedora came with a 2.6 kernel,
vmlinuz-2.6.17-1.2142_FC4, but when booting it was unable to recognize
the initrd image that came with it, so I had to manually create the
console, null and zero devices in /dev, and boot without it. Then it
could boot, though at some point it started going into a loop when
trying to connect to the net, so now it can only boot in interactive
mode, with the network service disabled. Anyway, I very much appreciate
your input, since it had not occurred to me that there is a real
possibility that work on XBasic is being hampered by the use of a 2.4
kernel. The latest release of XBasic is 5 years old, and I haven't been
able to get it to work on Debian Stable or Unstable. There is a
possibility that the assembly files it produces will only compile
correctly with a 2.4 kernel.
Sounds almost like you installed a Rescue CD or something. Or maybe just
the stuff off the first FC4 Install CD. You need the first two for a
more or less usable install. Try reinstalling FC4 from the full FC4 CD
set.
If you're using 5 year old code from XBasic written under the 2.4 headers
could be the problem. C header files and libraries for compiling under
the 2.4 kernel are different enough from the 2.6 headers to cause a
compile to fail. I have the code supplied by the manufacturer for the
Linux driver for a PCMCIA wireless card, a USRobotics. Compiles without
errors or warnings under 2.4; fails to compile with all kinds of errors
and warnings under 2.6. I know roughly what and where the problem is,
but it was easier just to buy a new madwifi compatible wireless card than
to rewrite the code.
Stef
.
- References:
- FC4 Base installed -- no dhcp
- From: ernobe
- Re: FC4 Base installed -- no dhcp
- From: Stefan Patric
- Re: FC4 Base installed -- no dhcp
- From: ernobe
- Re: FC4 Base installed -- no dhcp
- From: Stefan Patric
- Re: FC4 Base installed -- no dhcp
- From: ernobe
- FC4 Base installed -- no dhcp
- Prev by Date: Re: How do I change a readonly environment variable??
- Next by Date: Re: FC4 Base installed -- no dhcp
- Previous by thread: Re: FC4 Base installed -- no dhcp
- Next by thread: Re: FC4 Base installed -- no dhcp
- Index(es):
Relevant Pages
|
