summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20110703/004890.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-discuss/20110703/004890.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-discuss/20110703/004890.html')
-rw-r--r--zarb-ml/mageia-discuss/20110703/004890.html126
1 files changed, 126 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20110703/004890.html b/zarb-ml/mageia-discuss/20110703/004890.html
new file mode 100644
index 000000000..dbe9caede
--- /dev/null
+++ b/zarb-ml/mageia-discuss/20110703/004890.html
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-discuss] mageiaupdate and the list of updates
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20mageiaupdate%20and%20the%20list%20of%20updates&In-Reply-To=%3C4E0FAC75.20005%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+
+ <LINK REL="Next" HREF="004891.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-discuss] mageiaupdate and the list of updates</H1>
+ <B>andre999</B>
+ <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20mageiaupdate%20and%20the%20list%20of%20updates&In-Reply-To=%3C4E0FAC75.20005%40laposte.net%3E"
+ TITLE="[Mageia-discuss] mageiaupdate and the list of updates">andr55 at laposte.net
+ </A><BR>
+ <I>Sun Jul 3 01:40:37 CEST 2011</I>
+ <P><UL>
+
+ <LI>Next message: <A HREF="004891.html">[Mageia-discuss] Contribute web page
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4890">[ date ]</a>
+ <a href="thread.html#4890">[ thread ]</a>
+ <a href="subject.html#4890">[ subject ]</a>
+ <a href="author.html#4890">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Anne nicolas a &#233;crit :
+&gt;<i> 2011/7/2 Romain d'Alverny&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">rdalverny at gmail.com</A>&gt;:
+</I>&gt;&gt;<i> Le 2 juil. 2011 &#224; 17:14, andre999&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">andr55 at laposte.net</A>&gt; a &#233;crit :
+</I>&gt;&gt;&gt;<i> Suppose during the update process you have a check box to put a particular update on
+</I>&gt;&gt;&gt;<i> the skip list, or another to uninstall the corresponding package.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> That would be an interesting option to investigate.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Note that if you can't uninstall a package because it is required, it is usually
+</I>&gt;&gt;&gt;<i> inadvisable skip updates, unless you really understand the issues.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> So the user is stuck: unadvisable to skip the updates, unless she understands the issues
+</I>&gt;&gt;<i> =&gt; just make the update automatic in a background task by default then; one doesn't care
+</I>&gt;&gt;<i> about the issues - or won't have a single clue about it either, unless being a specific
+</I>&gt;&gt;<i> type of user that would know how to disable this auto update setting anyway).
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Changing when the password is requested would reduce the security for the system, as
+</I>&gt;&gt;&gt;<i> unauthorised users could see what is installed.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Unauthorised users using an authorised session, to be more specific.
+</I>
+Such a situation is far from rare in multi-user environments.
+But also if someone doesn't know the root password, currently they can't see
+what is installed. By delaying it until something is actually updated, they can
+see everything. So a remote user with limited privileges could more easily
+compromise the system.
+
+&gt;&gt;<i> Security is important. But that's orthogonal to a pleasant/efficient experience.
+</I>&gt;&gt;<i> Which is important too. We are aiming at making things for people.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> This may not affect you personnally, but such an option would best not be the
+</I>&gt;&gt;&gt;<i> default, to protect other systems. So it could be more complicated than the
+</I>&gt;&gt;&gt;<i> changes suggested above, and would only save you a few seconds.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> &quot;a few seconds&quot; is already a lot for everyone (and even more if the notification
+</I>&gt;&gt;<i> breaks your focus). Multiply this by the times such a notification occurs for a
+</I>&gt;&gt;<i> typical desktop system, you have a lot of valuable time wasted here.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> That's not such a ludicrous idea; improving the person experience with the system
+</I>&gt;&gt;<i> so she can focus on her task and not on the tool is clearly one of our goals.
+</I>&gt;<i>
+</I>&gt;&gt;<i> But indeed, perhaps it only requires making this more obvious (that is, integrated
+</I>&gt;&gt;<i> in the user flow and interface), how to use the existing options.
+</I>&gt;<i>
+</I>&gt;<i> Imho those 2 things are bad ideas:
+</I>&gt;<i>
+</I>&gt;<i> - having updates in background: Interesting thing in Linux is to learn
+</I>&gt;<i> people about their system. If they do not want details, then fine we
+</I>&gt;<i> can just a way to switch from general mode to detailed one.
+</I>
+That's one thing I like about Linux. Being able to readily monitor updates in
+detail.
+
+&gt;<i> - giving the possibility of adding easily packages to skip.list is the
+</I>&gt;<i> best way to break updates of end users systems. They will skip some
+</I>&gt;<i> updates when it's too long for example, without really being aware of
+</I>&gt;<i> what they do.
+</I>
+That was part of my concerns.
+
+&gt;<i> Then if an incoming update depends on a specific version
+</I>&gt;<i> of skipped package it will just break. I would rather add this as an
+</I>&gt;<i> advanced option in rpmdrake
+</I>
+I agree.
+Maybe an advanced mode, like in diskdrake. (which I use judiciously)
+
+&gt;&gt;<i>
+</I>&gt;&gt;<i> Romain
+</I>
+--
+Andr&#233;
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+
+ <LI>Next message: <A HREF="004891.html">[Mageia-discuss] Contribute web page
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4890">[ date ]</a>
+ <a href="thread.html#4890">[ thread ]</a>
+ <a href="subject.html#4890">[ subject ]</a>
+ <a href="author.html#4890">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
+mailing list</a><br>
+</body></html>