Hi,
I've got a bit of an issue after I switched to a new laptop for my
CentOS 6.9 installation: I'm using a Logitech cordless keyboard and
mouse that communicate with the system via a so-called "unifying
receiver". If this unit (a small USB thingummy) is connected when I try
to boot the syste
Hi,
After moving my CentOS 6 installation over to a new PC, the GRUB
start-up screen looks a bit strange. On the old machine, the menu area
and splash image would cover the entire screen, but now they occupy only
a small rectangle in its centre. I think what happens is that the max
resolution
Hi all,
I have used http://cefs.steve-meier.de/ plus https://github.com/vmfarms/generate_updateinfo to insert
some security-information into my os-updates - mirror.
This seems to work, but only partially.
On my 7.4 test server,
> yum --security -v check-update
gives me dnsmasq, nss, nss-sysi
First off - let me say I am not an administrator. I need to know if there is
an easy way to increase my /boot partition. When I installed CentOS 6 after
running 5, it was my oversight not to increase the /boot size. it's too small
and I can't do yum updates.
if it's not easy to actually incr
If there are many old kernels in there, you can probably remove the oldest
one(s) to make room for newer ones.
I've run into problems where the yum update didn't work because there wasn't
enough room in /boot; my notes for updating now include removing old kernels
first before running updates.
> On Oct 10, 2017, at 5:39 AM, Toralf Lund wrote:
>
> If this unit (a small USB thingummy) is connected when I try to boot the
> system, it locks up completely.
I’ve seen USB power draw be an issue similar to this previously. Does the same
problem occur if connected through a powered USB hub?
On Tue, 2017-10-10 at 13:55 +, KM wrote:
> First off - let me say I am not an administrator. I need to know if
> there is an easy way to increase my /boot partition. When I
> installed CentOS 6 after running 5, it was my oversight not to
> increase the /boot size. it's too small and I can't
Thanks for the idea. I've already restricted it to one kernel. so this
will not help me.
On Tuesday, October 10, 2017 10:04:56 AM, Vanhorn, Mike
wrote:
If there are many old kernels in there, you can probably remove the oldest
one(s) to make room for newer ones.
On Tue, 10 Oct 2017, KM wrote:
Thanks for the idea. I've already restricted it to one kernel. so this
will not help me.
And did you also delete the rescue kernel/image from /boot?
jh
___
CentOS mailing list
CentOS@centos.org
https://lists.ce
Here is my current info, should have increased it to like 500M or so at least.
Filesystem Size Used Avail Use% Mounted on/dev/sda1 96M 33M
59M 36% /boot
ls /boot
config-2.6.32-358.el6.x86_64
efi
grub
initramfs-2.6.32-358.el6.x86_64.img
initrd-2.6.32-358.el6.x86_64kdump.img
lo
On Tue, 10 Oct 2017, Pete Biggs wrote:
No, you can't do that. /boot is special and needs to be a separate
partition.
Needs is a bit strong, as grub2 does support LVM. It's not a supported
configuration for Redhat.
I'm not a sure there's a lot to it beyond having the lvm module loaded in
grub
On 10 October 2017 at 09:55, KM wrote:
> First off - let me say I am not an administrator. I need to know if there
> is an easy way to increase my /boot partition. When I installed CentOS 6
> after running 5, it was my oversight not to increase the /boot size. it's
> too small and I can't d
On Tue, Oct 10, 2017 at 10:36:16AM -0400, Stephen John Smoogen wrote:
> On 10 October 2017 at 09:55, KM wrote:
> > First off - let me say I am not an administrator. I need to know if there
> > is an easy way to increase my /boot partition. When I installed CentOS 6
> > after running 5, it was
Thanks for all of the input, not really sure what if anything I will do. i
was hoping it would be easy and i could just create a /boot in root, and copy
the actual boot contents to it and use it. wishful thinking i guess. just to
give a complete picture here is the current partitioning on t
Hiya everyone,
Is there a way to disable a thread that has degenerated into flaming? The
recent "discussion" on /var/run descended into some quite nasty places and
perhaps a lid should have been put on it. This seems to happen every few
weeks and is somewhat embarrassing when I'm trying to persuad
On 10/10/2017 16:03, Andrew Holway wrote:
Hiya everyone,
Is there a way to disable a thread that has degenerated into flaming? The
recent "discussion" on /var/run descended into some quite nasty places and
perhaps a lid should have been put on it. This seems to happen every few
weeks and is some
On 10/10/2017 11:03 AM, Andrew Holway wrote:
Hiya everyone,
Is there a way to disable a thread that has degenerated into flaming? The
recent "discussion" on /var/run descended into some quite nasty places and
perhaps a lid should have been put on it. This seems to happen every few
weeks and is s
Am 10.10.2017 um 17:03 schrieb Andrew Holway :
> Is there a way to disable a thread that has degenerated into flaming? The
> recent "discussion" on /var/run descended into some quite nasty places and
> perhaps a lid should have been put on it. This seems to happen every few
> weeks and is somewhat
On Tue, October 10, 2017 10:22 am, Mark Haney wrote:
> On 10/10/2017 11:03 AM, Andrew Holway wrote:
>> Hiya everyone,
>>
>> Is there a way to disable a thread that has degenerated into flaming?
>> The
>> recent "discussion" on /var/run descended into some quite nasty places
>> and
>> perhaps a lid
KM wrote:
> if it's not easy to actually increase it,
It's possible to resize partitions. I use System Rescue CD,
http://www.system-rescue-cd.org/
--
Yves Bellefeuille
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/lis
On 10/10/17 15:27, John Hodrien wrote:
On Tue, 10 Oct 2017, Pete Biggs wrote:
No, you can't do that. /boot is special and needs to be a separate
partition.
Needs is a bit strong, as grub2 does support LVM. It's not a supported
configuration for Redhat.
I'm not a sure there's a lot to it bey
On 10/10/2017 07:04 AM, Vanhorn, Mike wrote:
If there are many old kernels in there, you can probably remove the oldest
one(s) to make room for newer ones.
This is what I do. When /boot hits about 80% I go through and remove old
kernels I will never boot into anyway.
Usually that's at four
Do i need to do something special or is it as easy as:
- save the contents of the current /boot - umount /boot and change the
/etc/fstab so it doesn't mount again- create a boot directory that is in the
root filesystem- copy the contents back
I realize the physical/current /boot will be a wast
I have no idea how that script works (not maintained by CentOS Project)
.. BUT ..
If it does not also look at the CR announce list, it will miss those.
We do not double annonuce:
https://lists.centos.org/pipermail/centos-cr-announce/
(August 2017 and September 2017 were for the updates released
KM wrote:
> Do i need to do something special or is it as easy as:
> - save the contents of the current /boot - umount /boot and change
> the /etc/fstab so it doesn't mount again- create a boot directory
> that is in the root filesystem- copy the contents back
You'll also have to reinstall Grub
KM wrote:
> Thanks for all of the input, not really sure what if anything I will do.
> i was hoping it would be easy and i could just create a /boot in root,
> and copy the actual boot contents to it and use it. wishful thinking i
> guess. just to give a complete picture here is the current pa
On 10/10/2017 09:53 AM, KM wrote:
Thanks for all of the input, not really sure what if anything I will do. i
was hoping it would be easy and i could just create a /boot in root, and copy
the actual boot contents to it and use it. wishful thinking i guess. just to
give a complete picture
On 10/10/2017 6:20 PM, Robert Nichols wrote:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_bldsrv-lv_root
50G 26G 22G 55% /
tmpfs 9.0G 156K 9.0G 1% /dev/shm
/dev/sda1 96M 33M 59M 36% /boot
/dev/mapper/vg_bldsrv-lv_hom
On 10/10/2017 6:50 PM, John R Pierce wrote:
Your root filesystem is in an LVM volume. CentOS 6 is still using
GRUB legacy, which does not support /boot in LVM.
says up there, /boot is /dev/sda1, this is almost exactly the config
of my C6 servers.
never mind, I realized after I sent this,
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of KM
> Sent: den 10 oktober 2017 15:55
> To: CentOS Mailing List
> Subject: [CentOS] /boot partition too small
>
> First off - let me say I am not an administrator. I need to know if there
> is an
> easy w
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of KM
> Sent: den 10 oktober 2017 21:06
> To: centos@centos.org; Phil Perry
> Subject: Re: [CentOS] /boot partition too small
>
> Do i need to do something special or is it as easy as:
> - save the contents o
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Sorin Srbu
> Sent: den 11 oktober 2017 07:57
> To: CentOS mailing list
> Subject: Re: [CentOS] /boot partition too small
>
> > -Original Message-
> > From: CentOS [mailto:centos-boun...@centos.org]
32 matches
Mail list logo
