similar to: C7, systemd, say what?!

Matthew Miller wrote: > On Wed, Jun 07, 2017 at 10:10:14AM -0400, m.roth at 5-cent.us wrote: >> I just updated a system - as in minutes ago, and log back in after it >> reboots, and this is in dmesg: >> [ 88.202272] systemd-readahead[484]: >> open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many >> levels of symbolic links >> [

On Wed, Jun 07, 2017 at 10:10:14AM -0400, m.roth at 5-cent.us wrote: > I just updated a system - as in minutes ago, and log back in after it > reboots, and this is in dmesg: > [ 88.202272] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many > levels of symbolic links > [ 88.202515] systemd-readahead[484]: >

On 7 June 2017 at 16:13, <m.roth at 5-cent.us> wrote: > Matthew Miller wrote: >> On Wed, Jun 07, 2017 at 10:10:14AM -0400, m.roth at 5-cent.us wrote: >>> I just updated a system - as in minutes ago, and log back in after it >>> reboots, and this is in dmesg: >>> [ 88.202272] systemd-readahead[484]: >>>

On 06/07/2017 09:10 AM, m.roth at 5-cent.us wrote: > I just updated a system - as in minutes ago, and log back in after it > reboots, and this is in dmesg: > [ 88.202272] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many > levels of symbolic links > [ 88.202515] systemd-readahead[484]: >

2012/6/5 Kok, Auke-jan H <auke-jan.h.kok@intel.com> wrote on systemd-devel list: > It seems your system is taking well into 15+ seconds before btrfs is > actually *ready* on your system, which seems to be the main hiccup > (note, speculation here). I''ve personally become a bit displeased with > btrfs performance recently myself, so, I''m wondering if you should

On Mon, 8 Aug 2016 18:38:55 +0200 Pino Toscano <ptoscano@redhat.com> wrote: > Use the canonical way to regenerate the initrd images for all the > installed kernels, i.e. reconfigure the initramfs-tools which will > trigger the kernel postinst scripts. > --- > v2v/convert_linux.ml | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git

> -----Original Messages----- > From: "Steven Tardy" <sjt5atra at gmail.com> > Sent Time: 2018-02-26 10:48:48 (Monday) > To: "CentOS mailing list" <centos at centos.org> > Cc: > Subject: Re: [CentOS] How to update modules in iniramfs fastly > > On Sun, Feb 25, 2018 at 8:29 PM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> > wrote:

On 06/07/2017 11:24 AM, James Hogarth wrote: > > Mark stop with the flame baiting please. > > This is nothing systemd specific - and keep in mind /var/tmp is a > persistent temp area unlike /tmp which as it's tmpfs by default is of > course emptie don boot. I would wholeheartedly disagree. This IS something systemd specific. I have never seen init.d blow itself up over

On 4/5/2017 5:56 ??, Marcelo Roccasalva wrote: > dracut -f /boot/initramfs-<kernel_version>.img <kernel_version> I did: # dracut -f /boot/initramfs-3.10.0-514.10.2.el7.x86_64.img 3.10.0-514.10.2.el7.x86_64 and it ended without reporting any error. However, when I rebooted, nothing changed ("no such device: <UUID>. Entering rescue mode..."). Am I missing

I know dracut can update modules in initramfs, but I think it is too slow. So I'm wondering what is the fastest way to update modules in initramfs of CentOS 7? Thanks!

Hi, folks, Well, still more fun (for values of fun approaching zero): 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. Even though I installed the 9 repo, all that I get is 8. I've used their webform, and an waiting on a reply. 2. I remove all nvidia packages. 3. It appears that the kmod-nvidia is what I need; that's what nvidia-detect

Using update-initramfs is the native way of updating initrd on Debian based systems. To add some modules to the image we can list them in file /etc/initramfs-tools/modules. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/convert_linux.ml | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml index

> > But, what happens if you let the kernel post install scripts do the work > or setting up the initrd things? Initially, I just rebooted from LiveCD and left Grub,kernel and dracut do their job with the defaults, but unfortunately, boot process stops at initrd (dracut) stage with the following error: [ 197.768159] localhost.localdomain dracut-initqueue[252]: Warning: Could > not

On Wed, 2017-06-07 at 11:23 -0500, Johnny Hughes wrote: > If you want to create a CentOS-7 variant that does not use systemd, > then start a Special Interest Group and create modified packages > to use something else instead ......., much like the this group did > with Debian: > > https://devuan.org/ > > In the case of CentOS-7 .. you don't need to create a whole new

Just did an in-place update from 6.1 to 6.2 on my eeepc 901 (Atom CPU). during boot, (if I hit ESC to see the boot messages) it says "starging udev" then nothing else for a few seconds, then a huge register dump scrolls by. it's too big to see the beginning of it. If I boot from the prior kernel and look in /var/log/messages, I don't see any evidence of the failed boot.

Using update-initramfs is the native way of updating initrd on Debian based systems. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/convert_linux.ml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml index 08f4b2a..b09d03e 100644 --- a/v2v/convert_linux.ml +++ b/v2v/convert_linux.ml @@ -478,6 +478,15 @@

Hello I have error virt-v2v: error: unable to rebuild initrd (/boot/initramfs-4.2.3-300.fc23.x86_64.img) because mkinitrd or dracut was not found in the guest My physical machine run on fedora23 Boot on usb made from virt-p2v-livecd-1.32.0.fc23.iso <http://oirase.annexia.org/virt-p2v/virt-p2v-livecd-1.32.0.fc23.iso> Log joined to this mail Do you have this problem ?

I renamed my volume with vgrename however I didn't complete the other steps. Mainly update fstab and intiramfs. Once I booted, I was dropped on the Dracut shell. From here I can see the newly rename VG and I can lvm lvscan as well as activate it, lvm vgchange -ay. However I can't figure out what to do next, I'm assuming I need to regenerate the initramfs and then boot to change

Hi, I have a customized CentOS 5.5 kernel. I want it to upgrade it to CentOS 7. The approach I have decided was to take the CentOS 7 and then install the customized packages that are there in the CentOS 5.5. While trying to install the customized packages, I could install most of the packages, but I couldn't install the below in the latest CentOS 7. 1. rhpl 2. mod_perl 3.

> Yannis Milios wrote: >>> But, what happens if you let the kernel post install scripts do the >>> work or setting up the initrd things? >> >> Initially, I just rebooted from LiveCD and left Grub,kernel and dracut >> do >> their job with the defaults, but unfortunately, boot process stops at >> initrd (dracut) stage with the following error: