Pages

Search

Unknown video mode 0x31a - Forums Linux

Unknown video mode 0x31a - Forums Linux

Unknown video mode 0x31a

Posted: 20 Jul 2009 08:40 AM PDT

Allen Kistler wrote:
 

I resolved it quite easily! But needed long time ;-)

I recognised late night yesterday that I had still a memory card of my
digitl camera in the device slot (I have a flopy disk with memory card
readers for different formats). The card was in when I booted and then I
got that error message.

I unplugged the card - error gone! Strange though - Dos anybody have an idea
what happened?

Regards,

NoKo

--
"Careful with that VAX, Eugene!"

initrd + "no space left on device"

Posted: 17 Jul 2009 07:27 PM PDT

On Sun, 19 Jul 2009 10:29:40 -0400, Doug Laidlaw <org> wrote:
 
 

The term initrd stands for "initial ramdrive".

The initrd file stored in in /boot, contains an image that is copied
to the initial ramdrive (in ram) during bootup.

In addition to the contents from the file, there will be some free
space, that is used to create the temporary /dev and /tmp files,
that are needed before the real root filesystem has been checked,
mounted read-only, and then switched to read/write.

I've never used mondo. A regular boot cd and dd works fine for me.

My guess from the above, is that when mondo creates a bootable backup,
it needs more free space in the initial ramdrive for it's /tmp files
then is available (for the op). Note that this is the in ram drive,
not the on disk image of the drive.

zgrep "RAM_SIZE" /proc/config.gz
CONFIG_BLK_DEV_RAM_SIZE=32000

This shows the kernel's default size in kbytes. It can be overridden
with the ramdisk_size boot parameter. If it isn't specified in
the .config file, or in a boot parameter, it defaults to 4096kb
or 4 MB.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

Monitoring and securing outbound connections

Posted: 10 Jul 2009 08:25 PM PDT

On Wed, 15 Jul 2009 12:08:22 +0200, Aragorn wrote:
 

communism maybe, socialism nope. There is a big different.
Like commune and cult.

--

Great advances in Debian Linux; post a bug report and get spam in three
days.

yum is needed by package yum

Posted: 09 Jul 2009 08:57 AM PDT

On Jul 9, 11:57am, Guillaume Dargaud <fr> wrote: 

Rip yum-rhn-plugin and yum-updatesd ithe hell out if if you are using
local yum repositories, rather than calling back to the mothership.
Registering with the RHEL mothership is useful: it gets you notices of
security updates, and sitewide update management with yum-updatesd.
But yum-rhn-plugin is *NOT* a normal yum utility: it is "up2date"
dressed in grandmother's clothing, waiting to ignore yum directives
and replace your locally modified packages with RedHat's officially
provided ones, and it is *nasty* if you work with RPMforge or EPEL
packages or modify your kernels to support NTFS.

I approve of registration, so people pay their license fees and reward
RedHat for their hard work. But if you have a broad kickstart
deployment policy, or install Beowulf clusters or virtual machines and
don't want to individualize the machines even if you have enough
licenses, set up one machine with a license and use the 'reposync'
tool to download all the packages to a local HTTP repository, run
'createrepo' on it, and point your local machines to that much more
manageable yum repository.