meino.cra...@gmx.de wrote:
Hi,
this is no security issue in sense of attacks...it is related
to the consistency of the system.
Simple question (and may be complicate to answer... ;) )
How can I check, that my Gentoo system is uptodate, consistent
and sane?
Best regards,
mcc
I think
On 04/04/2010 08:18 AM, meino.cra...@gmx.de wrote:
Hi,
this is no security issue in sense of attacks...it is related
to the consistency of the system.
Simple question (and may be complicate to answer... ;) )
How can I check, that my Gentoo system is uptodate
emerge --sync emerge -uDN
Nikos Chantziaras wrote:
On 04/04/2010 08:18 AM, meino.cra...@gmx.de wrote:
Hi,
this is no security issue in sense of attacks...it is related
to the consistency of the system.
Simple question (and may be complicate to answer... ;) )
How can I check, that my Gentoo system is uptodate
Nikos Chantziaras rea...@arcor.de [10-04-04 08:28]:
On 04/04/2010 08:18 AM, meino.cra...@gmx.de wrote:
Hi,
this is no security issue in sense of attacks...it is related
to the consistency of the system.
Simple question (and may be complicate to answer... ;) )
How can I check, that my
Dale rdalek1...@gmail.com [10-04-04 08:20]:
meino.cra...@gmx.de wrote:
Hi,
this is no security issue in sense of attacks...it is related
to the consistency of the system.
Simple question (and may be complicate to answer... ;) )
How can I check, that my Gentoo system is uptodate,
Dale rdalek1...@gmail.com [10-04-04 08:36]:
Nikos Chantziaras wrote:
On 04/04/2010 08:18 AM, meino.cra...@gmx.de wrote:
Hi,
this is no security issue in sense of attacks...it is related
to the consistency of the system.
Simple question (and may be complicate to answer... ;) )
How
On 04/04/2010 10:07 AM, meino.cra...@gmx.de wrote:
Nikos Chantziarasrea...@arcor.de [10-04-04 08:28]:
On 04/04/2010 08:18 AM, meino.cra...@gmx.de wrote:
Hi,
this is no security issue in sense of attacks...it is related
to the consistency of the system.
Simple question (and may be
meino.cra...@gmx.de wrote:
Dalerdalek1...@gmail.com [10-04-04 08:36]:
Nikos Chantziaras wrote:
On 04/04/2010 08:18 AM, meino.cra...@gmx.de wrote:
Hi,
this is no security issue in sense of attacks...it is related
to the consistency of the system.
Simple question (and may
On Sunday 04 April 2010 01:52:17 Adam wrote:
Probably neither. Can you Ctrl+F12 to see what the logs are
saying? I've been getting kernel Oops! on shutdown on one
machine of mine with the 2.6.31-gentoo-r10 kernel. Might be
similar
Ok, i found this, which is mentioning fglrx, and the
Am 04.04.2010 07:18, schrieb meino.cra...@gmx.de:
Hi,
this is no security issue in sense of attacks...it is related
to the consistency of the system.
Simple question (and may be complicate to answer... ;) )
How can I check, that my Gentoo system is uptodate, consistent
and sane?
Best
Try appending md=3,/dev/sdb3,/dev/sdc3 to the kernel command line
parameters.
On 04/04/2010 01:45 AM, Albert Hopkins wrote:
On Sat, 2010-04-03 at 16:07 -0700, Mark Knecht wrote:
The install is complete but it won't boot. grub finds the kernel
and starts booting but then I get the typical VFS
On Sat, Apr 3, 2010 at 7:38 PM, Kerin Millar kerfra...@gmail.com wrote:
On 04/04/2010 02:01, Mark Knecht wrote:
Tried changing root=/dev/md0. No change.
The actual failure message is the fairly standard
VFS - Unable to mount root fs on unknown-block(9,0)
[snip]
CONFIG_MD_RAID1=y
On Sun, Apr 4, 2010 at 2:57 AM, Xavier Parizet x...@gentooist.com wrote:
Try appending md=3,/dev/sdb3,/dev/sdc3 to the kernel command line
parameters.
Thanks. Tried that one last night but no luck, although it does change
the message to Unknown-block(9,3) from Unknown-block(9,0).
Cheers,
Mark
Hello Everyone!
I am trying to install gentoo on my eee1201h and used this howto:
http://www.gentoo.org/doc/en/liveusb.xml
to setup a bootable SD card.
The system boots but depscan fail with
line 128: /bin/chmod: Input/Output Error
line 139: Bus Error
and a lot more.
Almost every command i
On 04/04/2010 15:20, Mark Knecht wrote:
On Sat, Apr 3, 2010 at 7:38 PM, Kerin Millarkerfra...@gmail.com wrote:
On 04/04/2010 02:01, Mark Knecht wrote:
Tried changing root=/dev/md0. No change.
The actual failure message is the fairly standard
VFS - Unable to mount root fs on
On Sun, Apr 4, 2010 at 10:32 AM, Kerin Millar kerfra...@gmail.com wrote:
On 04/04/2010 15:20, Mark Knecht wrote:
On Sat, Apr 3, 2010 at 7:38 PM, Kerin Millarkerfra...@gmail.com wrote:
On 04/04/2010 02:01, Mark Knecht wrote:
Tried changing root=/dev/md0. No change.
The actual failure
On 04/04/2010 18:50, Mark Knecht wrote:
[snip]
No problem supplying it. I did the rebuild this morning but forced
metadata to Type 1.0. No change as you suggested there wouldn't be.
OK, here's:
1) lspci to read lspci -k to see drivers both from the non-RAID kernel
2) The RAID kernel config
Hi,
I am running a vanilla kernel (linux-2.6.32.11), This kernel uses
alsa-1.0.21.
When doing the eix-sync-thingy, emerge always suggests to update
to alsa-1.0.22.
Is there a way that emerge/eix or whatever relizes the version of
alsa which the kernel is runnig and only suggests updates which
Von: nor...@smash-net.org
Datum: 04.04.2010 11:37
An: gentoo-user@lists.gentoo.org
Betreff: Re: [gentoo-user]
Checking sanity of system...
Am 04.04.2010 07:18, schrieb meino.cra...@gmx.de:
Hi,
this is no security
issue in sense of attacks...it is related
to the consistency of the system.
Hi,
I have to move my whole system from one disk to another
bigger one.
I think of doing as follows:
Boot a system via CD/DVD (knoppix for example).
Mount small disk read-only
Mount bigger disk read-write
cd into mountpoint of the first one
cp -a . ../mountpoint_of_bigger_disk
Seems to me
On 04/04/2010 19:43, Mark Knecht wrote:
[snip]
Aside from all of that, notable options that are going to be required to
boot in your case are:
CONFIG_MD_RAID1
CONFIG_SATA_AHCI
CONFIG_BLK_DEV_SD
CONFIG_BLK_DEV_SR
CONFIG_MSDOS_PARTITION (normally implicit but worth mentioning)
That, and the
On 04/04/2010 20:05, meino.cra...@gmx.de wrote:
Hi,
I have to move my whole system from one disk to another
bigger one.
I think of doing as follows:
Boot a system via CD/DVD (knoppix for example).
Mount small disk read-only
Mount bigger disk read-write
cd into mountpoint of the first one
cp
On Sun, Apr 4, 2010 at 12:29 PM, Kerin Millar kerfra...@gmail.com wrote:
SNIP
Ah, that looks better. Not that I've pored over every line, but at first
glance everything seems to be in order. There are no obvious gotchas that I
can see, so I'm somewhat puzzled.
As am I!
Here are a few
meino.cra...@gmx.de wrote:
Hi,
I have to move my whole system from one disk to another
bigger one.
I think of doing as follows:
Boot a system via CD/DVD (knoppix for example).
Mount small disk read-only
Mount bigger disk read-write
cd into mountpoint of the first one
cp -a .
On Sun, 04 Apr 2010 20:35:11 +0100, Kerin Millar wrote:
Whichever way you go about it, ensure that no pseudo-filesystem or bind
mounts are present within /mnt/oldrootfs at the time.
Use the -x option with rsync to stop it descending into other filesystems.
--
Neil Bothwick
Did you hear
On 04/04/2010 20:52, Mark Knecht wrote:
So this suggests that because I did the install from a running Gentoo
chroot that the mknod commands didn't stick? Somehow they were part
of, or because part of, the host Gentoo non-RAID install? Interesting.
I don't know what the handbook says these
On Sun, 4 Apr 2010 20:42:48 +0200, meino.cra...@gmx.de wrote:
I am running a vanilla kernel (linux-2.6.32.11), This kernel uses
alsa-1.0.21.
When doing the eix-sync-thingy, emerge always suggests to update
to alsa-1.0.22.
The 1.0.22 userspace tools work fine with the drivers in 2.6.32.
I'm running with full system FEATURES=test on, and I have a couple of
programs that depended on dev-libs/boost. The boost testsuite always
fails in my computer due to insufficient disk space, I usually simply
skip the test for boost and just go on with the merge. But today, I
decided to let the
On Sun, Apr 4, 2010 at 1:06 PM, Kerin Millar kerfra...@gmail.com wrote:
On 04/04/2010 20:52, Mark Knecht wrote:
So this suggests that because I did the install from a running Gentoo
chroot that the mknod commands didn't stick? Somehow they were part
of, or because part of, the host Gentoo
On 04/04/2010 23:16, Mark Knecht wrote:
First, thanks for sticking with me on this. I really appreciate it.
Second, I apologize for the length of the reply but it's still not
working and I wanted to try and clearly show the steps I've taken.
Maybe you or someone else will see the step I'm
On Sun, Apr 4, 2010 at 3:47 PM, Kerin Millar kerfra...@gmail.com wrote:
On 04/04/2010 23:16, Mark Knecht wrote:
First, thanks for sticking with me on this. I really appreciate it.
Second, I apologize for the length of the reply but it's still not
working and I wanted to try and clearly
On 05/04/2010 00:12, Mark Knecht wrote:
1) If you don't specify metadata then you get the newest - I think
that's currently ver. 1.2 or something.
Interesting. I suppose that might be a change in mdadm-3.0 (a version
which I have yet to use to create any new arrays). However, that would
Dnia 2010-04-04, o godz. 21:04:03
Neil Bothwick n...@digimed.co.uk napisał(a):
On Sun, 04 Apr 2010 20:35:11 +0100, Kerin Millar wrote:
Whichever way you go about it, ensure that no pseudo-filesystem or
bind mounts are present within /mnt/oldrootfs at the time.
Use the -x option with
On Sun, Apr 4, 2010 at 4:51 PM, Kerin Millar kerfra...@gmail.com wrote:
On 05/04/2010 00:12, Mark Knecht wrote:
1) If you don't specify metadata then you get the newest - I think
that's currently ver. 1.2 or something.
Interesting. I suppose that might be a change in mdadm-3.0 (a version
On 05/04/2010 00:51, Kacper Kopczyński wrote:
Dnia 2010-04-04, o godz. 21:04:03
Neil Bothwickn...@digimed.co.uk napisał(a):
On Sun, 04 Apr 2010 20:35:11 +0100, Kerin Millar wrote:
Whichever way you go about it, ensure that no pseudo-filesystem or
bind mounts are present within
On 05/04/2010 00:58, Mark Knecht wrote:
One thing about this that still confuses me is where /dev/md3, or
whatever, comes from when I boot if the the mknod command is never
executed within the chrrot. (As per the install guide.) Not a big deal
to proceed and see what happens. Maybe the kernel
On Sun, Apr 4, 2010 at 4:58 PM, Mark Knecht markkne...@gmail.com wrote:
On Sun, Apr 4, 2010 at 4:51 PM, Kerin Millar kerfra...@gmail.com wrote:
On 05/04/2010 00:12, Mark Knecht wrote:
1) If you don't specify metadata then you get the newest - I think
that's currently ver. 1.2 or something.
On 04/04/2010 07:20 AM, Mark Knecht wrote:
keeper ~ # diff /usr/src/linux/.config /mnt/gentoo/usr/src/linux/.config
4c4
# Mon Mar 29 01:02:31 2010
---
# Sun Apr 4 06:28:53 2010
893,912c893,906
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
Hi Mark,
Interesting thread, and I'm learning a lot
On Sun, Apr 4, 2010 at 5:47 PM, walt w41...@gmail.com wrote:
On 04/04/2010 07:20 AM, Mark Knecht wrote:
keeper ~ # diff /usr/src/linux/.config /mnt/gentoo/usr/src/linux/.config
4c4
# Mon Mar 29 01:02:31 2010
---
# Sun Apr 4 06:28:53 2010
893,912c893,906
CONFIG_MD_LINEAR=m
On 04/04/2010 11:42 AM, meino.cra...@gmx.de wrote:
Hi,
I am running a vanilla kernel (linux-2.6.32.11), This kernel uses
alsa-1.0.21.
When doing the eix-sync-thingy, emerge always suggests to update
to alsa-1.0.22.
Do you have media-sound/alsa-driver installed? If so, that is the
cause of
On 04/04/2010 01:04 PM, Neil Bothwick wrote:
On Sun, 04 Apr 2010 20:35:11 +0100, Kerin Millar wrote:
Whichever way you go about it, ensure that no pseudo-filesystem or bind
mounts are present within /mnt/oldrootfs at the time.
Use the -x option with rsync to stop it descending into other
On 05/04/2010 02:34, walt wrote:
On 04/04/2010 01:04 PM, Neil Bothwick wrote:
On Sun, 04 Apr 2010 20:35:11 +0100, Kerin Millar wrote:
Whichever way you go about it, ensure that no pseudo-filesystem or bind
mounts are present within /mnt/oldrootfs at the time.
Use the -x option with rsync to
http://sites.google.com/site/gni8hy9ojm/icfa5w
Neil Bothwick n...@digimed.co.uk [10-04-05 01:32]:
On Sun, 4 Apr 2010 20:42:48 +0200, meino.cra...@gmx.de wrote:
I am running a vanilla kernel (linux-2.6.32.11), This kernel uses
alsa-1.0.21.
When doing the eix-sync-thingy, emerge always suggests to update
to alsa-1.0.22.
The
walt w41...@gmail.com [10-04-05 05:02]:
On 04/04/2010 11:42 AM, meino.cra...@gmx.de wrote:
Hi,
I am running a vanilla kernel (linux-2.6.32.11), This kernel uses
alsa-1.0.21.
When doing the eix-sync-thingy, emerge always suggests to update
to alsa-1.0.22.
Do you have
Hi,
adding Gentoo/emerge related stuff to the completion system of the zsh
is nice...but getting a dark blue color for parts of the prompt with
that is not.
Where can I tuirn what to modifiy the color or get back my previous
prompt?
Best regards,
mcc
--
Please don't send me any Word- or
46 matches
Mail list logo
