Instead of using the ‘~’ in the file path, try using the ‘${HOME}’ variable
instead. If you must use the ‘~’, you will likely need to escape it in many
places. Another thing to note, if you use single quotes ( ‘ ) instead of double
quotes ( “ ) , most places in bash scripts won’t try to expand
I am trying to track down what happened with the “kernel-azure” packages that
were created by the Virt SIG? I see the last release was August 2020. I also
can’t seem to find the sources in the Virt repo
(http://mirror.centos.org/centos/7/virt/x86_64/azure/Packages/k/), nor in the
CentOS git
The way we did in place upgrades from CentOS 6 to 7 for our network appliance
VMs:
1. Take a backup of our appliance (database, settings, uploads, etc.). Store
the backup on a separate partition/volume.
2. Copy the CentOS 7 Minimal .iso, with our added packages, to the backup
partition/volume
Try "yum clean all", but I suspect you need to delete and rebuild the RPM
database. I don't remember the commands for that offhand, but Google might help
locate them.
Gregory
-Original Message-
From: CentOS On Behalf Of Jerry Geis
Sent: Wednesday, January 8, 2020 4:40 PM
To: CentOS
As long as you include the Grub modules (an issue I ran into with UEFI boot
last week on an .iso), you can use the "read" module to prompt for a hidden
command. Load the read module at the top, then at the end, put in your prompt
and secret boot option. In the case, you type "secret" at the
Nope, that editable FAT partition is actually the EFI boot partition. IIRC, the
grub config in that partition isn't actually used, only the EFI bootstrap
files. Once it can access the config on the main .iso partition it loads
everything from there.
Gregory Young
-Original Message-
You will want to follow the instructions for creating a custom .iso
https://access.redhat.com/solutions/60959
^^^ Requires a Red Hat account, or Red Hat Developer Account.
The keys are to modify both:
- /isolinux/isolinux.cfg - for legacy BIOS boot
- /EFI/BOOT/grub.cfg - for UEFI boot
Make
Heads up, Hyper-V Gen 2, CentOS 8 Server with GUI install results in a black
screen as updates are needed for X to properly detect and load the video. If
you can ssh into the box, do a yum update and it should grab the needed
updates, then reboot.
Gregory Young
-Original Message-
Ignore me, it looks like our Dev network DHCP server went down.
Gregory Young
-Original Message-
From: CentOS On Behalf Of Young, Gregory
Sent: September 24, 2019 2:33 PM
To: CentOS mailing list
Subject: Re: [CentOS] CentOS 8 Boot.iso image DHCP4 not working?
OK, looks like I'm
OK, looks like I'm seeing this with the DVD image as well.
Gregory Young
-Original Message-
From: CentOS On Behalf Of Young, Gregory
Sent: September 24, 2019 2:05 PM
To: centos@centos.org
Subject: [CentOS] CentOS 8 Boot.iso image DHCP4 not working?
I'm just wondering if anyone else
I'm just wondering if anyone else is not getting a DHCPv4 address in Anaconda,
using the CentOS 8 Boot.iso image? I get an IPv6 Autoconfig address, but it
doesn't want to pick up a DHCPv4. This is in a Hyper-V Gen2 VM, connected to
the same network all my other dev VMs are on, and picking up
Smith
Sent: August 8, 2019 7:48 PM
To: centos@centos.org
Subject: Re: [CentOS] another bizarre thing...
On Thu, Aug 08, 2019 at 05:06:06PM +0000, Young, Gregory wrote:
> Is this on both EL6 and EL7? If only EL7, it could be control groups causing
> the issue. The idea of cgroups is t
Is this on both EL6 and EL7? If only EL7, it could be control groups causing
the issue. The idea of cgroups is to prevent zombie processes, but if you need
your program to spawn another process then restart itself while the other
process continues to run, you need to launch it in a different
Hi Keith,
Is this a VM running on top of Hyper-V by chance? There seems to be an issue
with the combination of:
- Windows 10 1708 or newer.
- Hyper-V config version 8.2 - 9.0.
- Microsoft's Fix for Spectre and Meltdown.
- Newer Intel Hardware (Sandy Lake/Kaby Lake, etc.)
The workaround seems to
At least for debugging, try adding "inst.graphical" to the "append initrd="
line in your isolinux.cfg on the .iso image (grub.cfg and the "linuxefi" line
if you are booting UEFI). Remove "inst.cmdline" and "inst.text", as well as any
entries of " inst.noninteractive", " inst.noshell" and "
*** This response is my personal opinion and may not reflect that of my
employer. ***
I have never used the .automount file I have the .mount file configured for
various SAMBA shares, and I simply issued "systemctl enable share-x-y-z.mount"
to get them to mount on boot.
Greg
*** This response is my personal opinion and may not reflect that of my
employer. ***
>> people are tired of screaming and yelling about systemd, because we've
>> had years now of the response being "tough, it's the Wave of the
>> Future"
>
>We covered that back when RHEL 7 was still in beta:
*** This response is my personal opinion and may not reflect that of my
employer. ***
It seems recent updates to Anaconda and in particular Blivet in the CentOS 7
.iso are restricting things rather than expanding the options. We have a
scenario where we are doing a CentOS 6 to CentOS 7 upgrade
This response is my personal opinion and may not reflect that of my employer.
I see from your signature you are using WordPress. 100% I would recommend using
WooCommerce. The number of integrations and add-ons makes it the best
multi-purpose e-commerce solution. Depending on what you are doing,
19 matches
Mail list logo
