> This is not a problem. As long as your /boot
> partition (or / if /boot
> isn't it's own partition) is near the begining of
I don't think this is a problem any longer with the
new lilo 'lba32' support.
__
Do You Yahoo!?
Yahoo! Photos - 35mm Qu
> X, I get an error stating that it can't load the
> default font "fixed" and
> reports that it can't use "unix:/-1". In the xfs
> config file, it's set
> for "unix:/7300".
Can't you just rename 'unix:/7330' to 'unix:/-1' and
try that? Otherwise comment it out and it should still
run successfull
> Anyway, here's my question. I've got RH 6.2 (mostly
> stock... no major upgrades or anything) and I'm
That's a bad thing. If you're worried about security
(and obviously you are if you're using ssh) then make
sure to upgrade many packages which were found to be
vulnerable in RH62.
> Any ideas
> You should be using cc or gcc to compile anything on
> a redhat system... including the kernel.
Well, apparently this kgcc is specifically designed to
compile the kernel, due to it being a new version, I
think?
So you're able to compile the kernel using:
cpp-2.96-54
kernel-2.2.16-22
glibc-2.1
Hi. I've just installed 7.0 on a blank disk and now
understand there is a 'kgcc' that must be used to
compile the kernel. I removed gcc and linked kgcc to
gcc and cc in /usr/bin. Now, I'm receiving the
following assembly errors:
cc -D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes -