On 7/25/07, John Summerfield <[EMAIL PROTECTED]> wrote:
It's some time since I used RHEL rescue mode, but I would expect it to
be able to mount the filesystem.
RHEL documentation explains how to mount the filesystem -- this is
required to do a grub-install. (grub-install isn't on the rescue
di
John Hearns wrote:
Michael H. Semcheski wrote:
If I can't mount /dev/sda2, this means that I can't run grub-install.
(As I understand things.)
(And / Or, maybe I'm thick headed.)
In rescue mode, when you get the prompt, I normally do
modprobe 3w-9xxx (or 3w-xxx depending on controller)
Tho
On Wed, 25 Jul 2007, Michael H. Semcheski wrote:
So I didn't do an lsmod while I was booted in to 'linux rescue',
however I did "dmesg|grep 3w" and saw the 3w-9xxx driver, and I could
see /dev/sda, sda1, and sda2. When I ran lvm, it could see the
LogVol00 and LogVol01. I did vgchange -a y, I t
On 7/25/07, Connie Sieh <[EMAIL PROTECTED]> wrote:
How does AppArmor solve this security issue?
I am not sure. I am not an AppArmour expert in any way. A lot of the
issues that John brings up about path based control etc are ones that
are why AppArmor hasnt been brought into the core kernel
On 7/25/07, John Hearns <[EMAIL PROTECTED]> wrote:
Michael H. Semcheski wrote:
>
>
> If I can't mount /dev/sda2, this means that I can't run grub-install.
> (As I understand things.)
>
> (And / Or, maybe I'm thick headed.)
In rescue mode, when you get the prompt, I normally do
modprobe 3w-9xxx
Michael H. Semcheski wrote:
If I can't mount /dev/sda2, this means that I can't run grub-install.
(As I understand things.)
(And / Or, maybe I'm thick headed.)
In rescue mode, when you get the prompt, I normally do
modprobe 3w-9xxx (or 3w-xxx depending on controller)
Though as you can see /
On 7/25/07, Michael H. Semcheski <[EMAIL PROTECTED]> wrote:
If I can't mount /dev/sda2, this means that I can't run grub-install.
(As I understand things.)
I think I may be able to work through this:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/s1-rescuemode-boot.
On 7/25/07, Connie Sieh <[EMAIL PROTECTED]> wrote:
> Anaconda does fine. No errors. After the disk is formated and the
> packages are copied over from the CD's, it asks me to reboot. I
> reboot, and after the BIOS and RAID are initialized, instead of seeing
> grub, I just see a blank text scre
Michael H. Semcheski wrote:
Hello,
I'm setting up Scientific Linux (version 4.5) on a brand new machine.
This machine has a 3ware RAID card. The RAID5 configuration is 4x750.
(So I'm installing onto a
roughly 2TB disk, using the default partitioning.)
Anaconda does fine. No errors. After the
On Wed, 25 Jul 2007, Michael H. Semcheski wrote:
Hello,
I'm setting up Scientific Linux (version 4.5) on a brand new machine.
This machine has a 3ware RAID card. The RAID5 configuration is 4x750.
(So I'm installing onto a
roughly 2TB disk, using the default partitioning.)
Anaconda does fine.
Hello,
I'm setting up Scientific Linux (version 4.5) on a brand new machine.
This machine has a 3ware RAID card. The RAID5 configuration is 4x750.
(So I'm installing onto a
roughly 2TB disk, using the default partitioning.)
Anaconda does fine. No errors. After the disk is formated and the
pac
On Tue, 24 Jul 2007, Stephen John Smoogen wrote:
On 7/24/07, John Logsdon <[EMAIL PROTECTED]> wrote:
A number of people - not on this list - have objections to SEL, even including
the suggestion that it is really a business model to sell support rather than
offer security!
Mine has always been
12 matches
Mail list logo
