similar to: Adding options to grub

On Thu, Aug 27, 2020 at 11:08 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Thu, Aug 27, 2020 at 10:50:12AM +0300, Sam Eiderman wrote: > > Hi, > > > > I'm using libguestfs 1.42, > > > > When I run the following python3 commands on a rhel7.8: > > > > print(g.ls('/sys')) > > [] > > This lists the files in /sys in

Hi, I'm using libguestfs 1.42, When I run the following python3 commands on a rhel7.8: print(g.ls('/sys')) print(g.sh('ls /sys')) I get: [] block bus class dev devices firmware fs hypervisor kernel module power It seems that g.ls('/sys') is chrooted correctly. But g.sh('ls /sys') isn't. I came across this behavior when I used

On Thu, Aug 27, 2020 at 10:50:12AM +0300, Sam Eiderman wrote: > Hi, > > I'm using libguestfs 1.42, > > When I run the following python3 commands on a rhel7.8: > > print(g.ls('/sys')) > [] This lists the files in /sys in the filesystem, which in most disk images is likely to be an empty directory. > print(g.sh('ls /sys')) > block > bus >

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

> Il 06/04/20 11:54, Georgios ha scritto: >> Hi there! >> I had a similar problem recently with grub. No idea why it doesnt work. >> Try using grubby instead of grub2-mkconfig if you want the system to >> keep your kernel parameters between boots. >> >> Something like: >> >> sudo grubby --args="i915.modeset=0 rd.driver.blacklist=i915"

Il 06/04/20 20:51, Jonathan Billings ha scritto: > On Mon, Apr 06, 2020 at 04:03:53PM +0200, Alessandro Baggi wrote: >> I'm on 8.1. I'm searching help to see if this is a bug or error by me but >> can't find nothing. >> Currently I used grubby but it does not write any file that I know like >> /boot/efi/EFI/centos/grub.cfg (I tried to remove and add arg but

Il 06/04/20 15:21, Simon Matter via CentOS ha scritto: >> Il 06/04/20 11:54, Georgios ha scritto: >>> Hi there! >>> I had a similar problem recently with grub. No idea why it doesnt work. >>> Try using grubby instead of grub2-mkconfig if you want the system to >>> keep your kernel parameters between boots. >>> >>> Something like:

On Apr 8, 2020, at 04:01, Alessandro Baggi <alessandro.baggi at gmail.com> wrote: > > Il 08/04/20 01:46, Jonathan Billings ha scritto: >> >> grubby only alters the existing configuration. It never regenerates the grub.cfg in EFI. >> >> You can?t use ?grub2-mkconfig? to create individual boot spec entries. >> >> -- >> Jonathan Billings

Il 08/04/20 01:46, Jonathan Billings ha scritto: > On Apr 7, 2020, at 04:14, Alessandro Baggi <alessandro.baggi at gmail.com> wrote: >> thank you for your explanation. So in el8 grubby should be used to update kernel opts and grub2-mkconfig is used to generate an initial config. >> >> If I'm not wrong, grubby updates every single (sperated) entries on

Hello everyone. I'm trying to install CentOS 8 with root and swap partitions on software raid. The plan is: - create md0 raid level 1 with 2 hard drives: /dev/sda and /dev/sdb, using Linux Rscue CD, - install CentOS 8 with Virtual Box on my laptop, - rsync CentOS 8 root partition on /dev/md0p1, - chroot in CentOS 8 root partition, - configure /etc/mdadm.conf, grub.cfg, initramfs, install

On Apr 7, 2020, at 04:14, Alessandro Baggi <alessandro.baggi at gmail.com> wrote: > thank you for your explanation. So in el8 grubby should be used to update kernel opts and grub2-mkconfig is used to generate an initial config. > > If I'm not wrong, grubby updates every single (sperated) entries on /boot/loader/entries and then generate the /boot/efi/EFI/centos/grub.cfg? >

Il 06/04/20 11:54, Georgios ha scritto: > Hi there! > I had a similar problem recently with grub. No idea why it doesnt work. > Try using grubby instead of grub2-mkconfig if you want the system to > keep your kernel parameters between boots. > > Something like: > > sudo grubby --args="i915.modeset=0 rd.driver.blacklist=i915" --update- > kernel=ALL > >

Hi there! I had a similar problem recently with grub. No idea why it doesnt work. Try using grubby instead of grub2-mkconfig if you want the system to keep your kernel parameters between boots. Something like: sudo grubby --args="i915.modeset=0 rd.driver.blacklist=i915" --update- kernel=ALL Hope it helps! Have a nice day! On Mon, 2020-04-06 at 11:42 +0200, Alessandro Baggi wrote:

On Mon, Apr 06, 2020 at 04:03:53PM +0200, Alessandro Baggi wrote: > I'm on 8.1. I'm searching help to see if this is a bug or error by me but > can't find nothing. > Currently I used grubby but it does not write any file that I know like > /boot/efi/EFI/centos/grub.cfg (I tried to remove and add arg but nothing > changed on files), so I don't know where it make

So I installed centos8. And I was looking for the grub config file: [root at testbox ~]# ls -l /etc/grub2.cfg lrwxrwxrwx. 1 root root 22 Oct 2 13:01 /etc/grub2.cfg -> ../boot/grub2/grub.cfg [root at testbox ~]# But [root at testbox ~]# ls /boot/grub2/ grubenv [root at testbox ~]# Why is it not there? FYI, I did try 'yum reinstall grub2' and no /boot/grub2/grub.cfg for me.

On Fri, Dec 27, 2019 at 7:04 AM Eddie O'Connor <eoconnor25 at gmail.com> wrote: > > Wouldn't a "find grub / find grub*"....or "locate grub / locate grub*" > work?... > locate would require to install that package and run updatedb first. But, it would save time looking for files that have been already added to its db, specially compared to running

Hi list, I reinstalled on my workstation CentOS 8.1. I explain: I'm a KDE user but packages shipped from EPEL currently are buggy so I prefer a stable and functioning system to work with. So I tried to remove KDE workgroup and installed group "Workstation" but the system bricked so I reinstalled with GNOME. I've an nvidia gtx 1050ti GPU so I installed kmod-driver from

hello! While trying to compile the new and final icecast2, I got this compile error on the make: make[3]: *** [xslt.o] Error 1 make[3]: Leaving directory `/home/boink/icecast-2.0.0/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/boink/icecast-2.0.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/boink/icecast-2.0.0' make: ***

you also need the dev's aswell <p>> >hello! > >While trying to compile the new and final icecast2, I got this compile >error on the make: > >make[3]: *** [xslt.o] Error 1 >make[3]: Leaving directory `/home/boink/icecast-2.0.0/src' >make[2]: *** [all-recursive] Error 1 >make[2]: Leaving directory `/home/boink/icecast-2.0.0/src' >make[1]: ***

Full_Name: Jeff Hallman Version: 1.2.2 OS: Solaris Submission from: (NULL) (132.200.32.33) "boink<-" <- function(x, a = 1, b = 2, value){ print(match.call()) x } > z <- 1 > boink(z, b = 4) <- 22 boink<-(x = *tmp*, a = 4, value = 22) > Shouldn't it have matched the 4 to b, not a?