Nice, so you're up and running? There are later hardened tarballs
available, pre-2007.0... I can confirm that they work well. :)
ncftp ...al/x86/hardened/stages > ls *.tar.bz2
stage1-x86-hardened-2007.0_pre20070209.tar.bz2
stage2-x86-hardened-2007.0_pre20070209.tar.bz2
stage3-x86-hardened-2007
...and 'make modules'. 2.6 will make the modules when you do 'make', but
2.4 won't...
Public GPG/PGP key for Brant Williams: 0x88E1AA9E.
Available at your friendly local public keyserver.
On Sun, 17 Jun 2007, René Rhéaume wrote:
> I did an experiment by building the libata drivers as modu
What steps are you taking when running the kernel
configuration/compilation? You might have forgotten to do 'make dep'...
Public GPG/PGP key for Brant Williams: 0x88E1AA9E.
Available at your friendly local public keyserver.
On Sun, 17 Jun 2007, René Rhéaume wrote:
> I did an experiment by
On 6/20/07, Brant Williams <[EMAIL PROTECTED]> wrote:
What error(s) do you see?
e2fsck was doing a fatal error and I was forced to reboot. It is now
solved after I updated e2fsprogs.
Long answer : I restarted a hardened+uclibc installation using a very
old stage3 tarball (dating back from 2005)
What error(s) do you see?
Public GPG/PGP key for Brant Williams: 0x88E1AA9E.
Available at your friendly local public keyserver.
On Mon, 18 Jun 2007, René Rhéaume wrote:
> No, the problem was SCSI and SCSI disk support were built as modules,
> not in-kernel. Now, init runs, but e2fsck does no
No, the problem was SCSI and SCSI disk support were built as modules,
not in-kernel. Now, init runs, but e2fsck does not grok my root
partition (formatted with a 2.6 kernel).
--
[EMAIL PROTECTED] mailing list
René Rhéaume kirjoitti:
> I did an experiment by building the libata drivers as modules. During
> make modules_install, I got "Unresolved symbols" errors for every
> driver. What kernel configuration option am I missing ?
>
Did you boot into the new kernel? For me this has usually meant that the
On 17 Jun 2007 at 19:45, René Rhéaume wrote:
> I did an experiment by building the libata drivers as modules. During
> make modules_install, I got "Unresolved symbols" errors for every
> driver. What kernel configuration option am I missing ?
something related to libata-core?
--
[EMAIL PROTECTED
I did an experiment by building the libata drivers as modules. During
make modules_install, I got "Unresolved symbols" errors for every
driver. What kernel configuration option am I missing ?
depmod: *** Unresolved symbols in
/lib/modules/2.4.33.4-hardened-grsec/kernel/drivers/scsi/sata_nv.o
depm
