diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-July/017640.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-July/017640.html | 153 |
1 files changed, 153 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-July/017640.html b/zarb-ml/mageia-dev/2012-July/017640.html new file mode 100644 index 000000000..1093b9c61 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-July/017640.html @@ -0,0 +1,153 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Systemd improvement + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Systemd%20improvement&In-Reply-To=%3C20120724094735.GR3708%40virgo.home.nanardon.zarb.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="017635.html"> + <LINK REL="Next" HREF="017642.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Systemd improvement</H1> + <B>Olivier Thauvin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Systemd%20improvement&In-Reply-To=%3C20120724094735.GR3708%40virgo.home.nanardon.zarb.org%3E" + TITLE="[Mageia-dev] Systemd improvement">nanardon at nanardon.zarb.org + </A><BR> + <I>Tue Jul 24 11:47:36 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="017635.html">[Mageia-dev] Systemd improvement +</A></li> + <LI>Next message: <A HREF="017642.html">[Mageia-dev] Systemd improvement +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17640">[ date ]</a> + <a href="thread.html#17640">[ thread ]</a> + <a href="subject.html#17640">[ subject ]</a> + <a href="author.html#17640">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>* Colin Guthrie (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>) wrote: +><i> 'Twas brillig, and Olivier Thauvin at 24/07/12 10:02 did gyre and gimble: +</I>><i> > I have some minor issues with systemd so I report it in case some +</I>><i> > improvment could be done: +</I>><i> > +</I>><i> > 1) The timeout is very long when the system failed to ask the passphrase +</I>><i> > for encrypted partition, os it is very long to reach any console (this +</I>><i> > happend only when there is a problem) +</I>><i> > +</I>><i> > 2) When everything work fine, the timeout occur if the passphrase for +</I>><i> > encrypted partition is not enter early enough: I power up my laptop, do +</I>><i> > something else, come back and it report the boot has failed, surprising! +</I>><i> +</I>><i> So it's both too long and too short :) +</I>><i> +</I>><i> I'm not sure how to deal with this, but I would suggest that we need to +</I>><i> do something a bit more creative to deal with your particular use case. +</I>><i> +</I>><i> For yourself, it's not a "critical" filesystem - e.g. it's not /usr or +</I>><i> similar, but /home. +</I> +No you misunderstood, if the system succeed to launch +'/usr/bin/ask-the-passphrase' or whatever its name is, it must wait an +answer for ever and not continue booting and finally claim "hey +surprising, I failed to boot w/o the passphrase". +The firest time it happend I really thought my system was broken. + +However, if it cannot launch '/usr/bin/ask-the-passphrase' it is sure +booting will failed as it cannot get the passphrase, no need to wait an +impossible user input. +Again, the case I just talk about happend only in case of bug and must +not happend on stable distro. + +><i> > 3) the boot process hang/stop/wait if my wireless card is down (using +</I>><i> > the hardware switch on the side of my laptop). This step need just one +</I>><i> > second when the card is on, even it does not connect to any network. +</I>><i> +</I>><i> If you have any NFS (or other network mounts) mounts that are NOT marked +</I>><i> with nofail, then we consider them to be "critical" filesystems. If +</I>><i> these filesystems are NOT needed for boot, then just mark them as +</I>><i> "nofail" and they will still be mounted but your DM/logins will not be +</I>><i> delayed while waiting for the network. +</I> + +I don't have nfs in my fstab but maybe this is triggered by another +service. +But I don't see the point of waiting the card to be on, especially when +the card is on it don't connect to any network and don't wait this +happend. + +-- + +Olivier Thauvin +CNRS - LATMOS +♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖ +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: not available +Type: application/pgp-signature +Size: 197 bytes +Desc: not available +URL: </pipermail/mageia-dev/attachments/20120724/a26bf990/attachment.asc> +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="017635.html">[Mageia-dev] Systemd improvement +</A></li> + <LI>Next message: <A HREF="017642.html">[Mageia-dev] Systemd improvement +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17640">[ date ]</a> + <a href="thread.html#17640">[ thread ]</a> + <a href="subject.html#17640">[ subject ]</a> + <a href="author.html#17640">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |