1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] mageia sound tasks
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3C20101218145426.GA18333%40sisay.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001786.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] mageia sound tasks</H1>
<B>Michael scherer</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3C20101218145426.GA18333%40sisay.ephaone.org%3E"
TITLE="[Mageia-dev] mageia sound tasks">misc at zarb.org
</A><BR>
<I>Sat Dec 18 15:54:26 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001786.html">[Mageia-dev] mageia sound tasks
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1790">[ date ]</a>
<a href="thread.html#1790">[ thread ]</a>
<a href="subject.html#1790">[ subject ]</a>
<a href="author.html#1790">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Fri, Dec 17, 2010 at 01:33:24PM -0500, Frank Griffin wrote:
><i> SaschaS wrote:
</I>><i> > After having a looong chat with the guys from linux4audio and reading
</I>><i> > tons of posts in ccrma forum, I must say .....
</I>><i> >
</I>><i> > Idea with an rt-kernel for netbooks ....... DISMISSED .... it simply
</I>><i> > makes no sense.
</I>><i> > Those guys mostly use gentoo and build their own kernel for years now
</I>><i> > and they gave me the following hints, that also can be found in
</I>><i> > discussions of other distributions:
</I>><i> Pre-built kernels are appropriate for standard and newbie systems, but
</I>><i> what you might consider is packaging a kernel .config file with the
</I>><i> options for your custom kernel, having the package prereq kernel-source,
</I>><i> and having the spec file compile the kernel with that .config file and
</I>><i> install it under a name derived from the package-name.
</I>><i>
</I>><i> Of course, we'll get performance complaints about urpmi running for 3 or
</I>><i> 4 hours, but hey, it's a lot less of a bandwidth/space hog.
</I>
We could have something that run the compilation in the background. That's how
gitorious do for lenghty operation, something based on stomp.
You install the specfile, it check if the server is up, if not, it start it, it
send a message "compile this", and then urpmi finish.
The next issue would be how to communicate with the user that the kernel is ready.
Maybe using s2u, or dbus, i do not know.
Using this method would also ease the distribution of custom patched kernel, if we start to
distribute the various patchs as rpm, we would no longer have 28 compiled kernels in
contrib.
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001786.html">[Mageia-dev] mageia sound tasks
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1790">[ date ]</a>
<a href="thread.html#1790">[ thread ]</a>
<a href="subject.html#1790">[ subject ]</a>
<a href="author.html#1790">[ 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>
|
