Stefan G. Weichinger wrote:
> On 29.05.2015 01:57, cov...@ccs.covici.com wrote:
>
> > OK, thanks much.
>
> so, does it boot now?
>
Sure, once I found the typo and fixed it, it booted, I was just trying
to save time in the future and I did learn a few things in the process.
--
Your life is l
On 29.05.2015 01:57, cov...@ccs.covici.com wrote:
> OK, thanks much.
so, does it boot now?
Canek Peláez Valdés wrote:
> On Thu, May 28, 2015 at 2:11 PM, wrote:
> >
> > > Also, as Rich said, if you wait it's possible that systemd (and/or
> dracut)
> > > will drop you into a rescue shell anyway. Unfortunately, thanks to very
> > > slow hardware in the wild, the timeout has been increase
On Thu, May 28, 2015 at 5:23 PM, Rich Freeman wrote:
>
> On Thu, May 28, 2015 at 5:32 PM, Canek Peláez Valdés
wrote:
> >
> > As I said, I did the following tests:
> >
> > 1. Adding "emergency" to the kernel command line, with a valid root=.
> > 2. Adding "rescue" to the kernel command line, with
On Thu, May 28, 2015 at 4:55 PM, wrote:
> Canek Peláez Valdés wrote:
[...]
> > As I said, I did the following tests:
> >
> > 1. Adding "emergency" to the kernel command line, with a valid root=.
> > 2. Adding "rescue" to the kernel command line, with a valid root=.
> > 2. Leaving root= invalid wi
On Thu, May 28, 2015 at 5:55 PM, wrote:
> How do you pivot route manually?
>
With dracut I'm pretty sure that as long as you mount root under
/sysroot you can just type exit and it will take care of the rest. I
suspect it will even remount it for you if you don't use the same
options as it find
On Thu, May 28, 2015 at 5:32 PM, Canek Peláez Valdés wrote:
>
> As I said, I did the following tests:
>
> 1. Adding "emergency" to the kernel command line, with a valid root=.
> 2. Adding "rescue" to the kernel command line, with a valid root=.
> 2. Leaving root= invalid without adding neither "em
Canek Peláez Valdés wrote:
> On Thu, May 28, 2015 at 1:36 PM, Rich Freeman wrote:
> >
> > On Thu, May 28, 2015 at 2:11 PM, Canek Peláez Valdés
> wrote:
> > >
> > > Actually, it does work (see attached screenshot). I set my root= kernel
> > > command line parameter wrong on purpose, and systemd
On Thu, May 28, 2015 at 2:11 PM, wrote:
>
> > Also, as Rich said, if you wait it's possible that systemd (and/or
dracut)
> > will drop you into a rescue shell anyway. Unfortunately, thanks to very
> > slow hardware in the wild, the timeout has been increased to three
minutes,
> > and I believe tho
On Thu, May 28, 2015 at 1:36 PM, Rich Freeman wrote:
>
> On Thu, May 28, 2015 at 2:11 PM, Canek Peláez Valdés
wrote:
> >
> > Actually, it does work (see attached screenshot). I set my root= kernel
> > command line parameter wrong on purpose, and systemd (inside dracut)
dropped
> > me inside a res
Canek Peláez Valdés wrote:
> On Thu, May 28, 2015 at 3:30 AM, wrote:
> >
> > Stefan G. Weichinger wrote:
> >
> > > On 28.05.2015 09:39, cov...@ccs.covici.com wrote:
> > >
> > > > No, the journal is gone, it was only in /run which is on a tmpfs file
> > > > system. I can boot from a cd all day
On Thu, May 28, 2015 at 2:11 PM, Canek Peláez Valdés wrote:
>
> Actually, it does work (see attached screenshot). I set my root= kernel
> command line parameter wrong on purpose, and systemd (inside dracut) dropped
> me inside a rescue shell.
Interesting. Perhaps it just enables shell access.
T
On Thu, May 28, 2015 at 11:57 AM, Canek Peláez Valdés wrote:
> Others have already answered, but I will add that if you put "emergency"
> anywhere in the kernel command line, then systemd will boot to the rescue
> target; that's why I suggested to do it in my first answer.
I'm pretty sure that wo
On Thu, May 28, 2015 at 3:30 AM, wrote:
>
> Stefan G. Weichinger wrote:
>
> > On 28.05.2015 09:39, cov...@ccs.covici.com wrote:
> >
> > > No, the journal is gone, it was only in /run which is on a tmpfs file
> > > system. I can boot from a cd all day long, but it would not help one
> > > bit.
>
Rich Freeman wrote:
> On Thu, May 28, 2015 at 2:15 AM, wrote:
> >
> > Thanks for your quick reply, but I do have rd.shell=1, but it did not
> > drop to a shell,it just hung, so I could not do journalctl or anything
> > -- the nearest break point was pre-initqueue which was maybe too early
> > a
Stefan G. Weichinger wrote:
> On 28.05.2015 10:30, cov...@ccs.covici.com wrote:
>
> > I still have openrc, but Dracut won't work with it, at least maybe
> > because I have systemd use flag enabled. Also, in retrospect, that
> > would not have solved my specific problems, because it was related
On Thu, May 28, 2015 at 2:15 AM, wrote:
>
> Thanks for your quick reply, but I do have rd.shell=1, but it did not
> drop to a shell,it just hung, so I could not do journalctl or anything
> -- the nearest break point was pre-initqueue which was maybe too early
> and the next one is pre-mount which
On 28.05.2015 10:30, cov...@ccs.covici.com wrote:
> I still have openrc, but Dracut won't work with it, at least maybe
> because I have systemd use flag enabled. Also, in retrospect, that
> would not have solved my specific problems, because it was related to an
> rd.lv command which is specific
Stefan G. Weichinger wrote:
> On 28.05.2015 09:39, cov...@ccs.covici.com wrote:
>
> > No, the journal is gone, it was only in /run which is on a tmpfs file
> > system. I can boot from a cd all day long, but it would not help one
> > bit.
>
> Hm, I think it could help for sure as you could chro
On 28.05.2015 09:39, cov...@ccs.covici.com wrote:
> No, the journal is gone, it was only in /run which is on a tmpfs file
> system. I can boot from a cd all day long, but it would not help one
> bit.
Hm, I think it could help for sure as you could chroot in and do
something. For example build a
Stefan G. Weichinger wrote:
> Am 2015-05-28 um 08:15 schrieb cov...@ccs.covici.com:
>
> > Thanks for your quick reply, but I do have rd.shell=1, but it did not
> > drop to a shell,it just hung, so I could not do journalctl or anything
> > -- the nearest break point was pre-initqueue which was ma
Am 2015-05-28 um 08:15 schrieb cov...@ccs.covici.com:
> Thanks for your quick reply, but I do have rd.shell=1, but it did not
> drop to a shell,it just hung, so I could not do journalctl or anything
> -- the nearest break point was pre-initqueue which was maybe too early
> and the next one is pre-
Canek Peláez Valdés wrote:
> On Thu, May 28, 2015 at 12:09 AM, wrote:
> >
> > Hi folks. I spent a very frustrating time last night trying to figure
> > out why my systemd would not boot using systemd. I am using dracut and
> > its version is 041r2. Now what was happening is that the system w
On Thu, May 28, 2015 at 12:09 AM, wrote:
>
> Hi folks. I spent a very frustrating time last night trying to figure
> out why my systemd would not boot using systemd. I am using dracut and
> its version is 041r2. Now what was happening is that the system would
> get to the pre-init-queue -- and
24 matches
Mail list logo
