Re: What happened to the Ubuntu SoC 2006 projects that we're so excited about?
Hi. 2007/8/1, Joel Bryan Juliano <[EMAIL PROTECTED]>: > > What happened to those SoC 2006's "Ubuntu Welcome Center?" and "Panel > Switcher?".. > the last time I checked them out through svn around 5 months ago, is still > the same files I have now. > > It's really disappointing that those people actually have resources to > make those, and not make use of it.. > I'm so pissed off I actually made my own versions of those software in > just 2 days time (during midnight in a borrowed computer from a friend.). Care to post some patches? Regards Erik Andrén Where is the final product? > > -- > "object-oriented programming is really just a common sense extension of > structured programming" - Roger Sessions > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Apprenticeship periods at university, working on Ubuntu!
Hello, 2007/9/5, Vincenzo Ciancia <[EMAIL PROTECTED]>: > > Hi all, > > [...] 3) Ethernet needs (in my opinion) support in network manager for those > networks that do not have dhcp (say "create new ethernet connection with > name...") and for 802.1x ethernet support out-of-the-box (see LP bug > #82113). Sounds more like an upstream network manager issue than an ubuntu specific one. You should probably direct further inqueries to them directly. Take care, Erik Someone willing to mentor, or suggestions? > > Thanks and bye > > Vincenzo > > > > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: regular fsck runs are too disturbing
2007/9/27, Waldemar Kornewald <[EMAIL PROTECTED]>: > > ... > -- > Are there any alternatives? Here are two examples: > > Use SMART (AFAIK, Vista does that). SMART is hardware- and not filesystem dependent. Besides, the implementation of SMART differs wildly from each hard-drive manufacturer. Take care, Erik Run fsck read-only (even on mounted partitions) as a low-priority > process in the background when the system is *idle* and report to the > user only when an error is found, then requiring a reboot and full > system check on boot-up. > > Regards, > Waldemar Kornewald > > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: regular fsck runs are too disturbing
I'm going to add an anecdote to this thread why running fsck (at least in textmode) at startup is bad. Some good friends of mine use ubuntu on their HTPC. The connected HDTV can't display the text mode under which the fsck runs, this results in a blue screen during the whole operation. As these folks aren't any computer whizzes they belive the computer has hanged itself as no plausible explanation is given from the computer. Efter a brief explanation from me this, of course, is no problem, but I'm sure these people aren't the only one with a similar experience. Regards, Erik Andrén 2007/10/17, Phillip Susi <[EMAIL PROTECTED]>: > > Onno Benschop wrote: > > I am subscribed to the list, there is no need to send this to me > directly. > > Fair enough. I will remove you for now, but if you wish to not get such > replies regularly, you should set your Reply-To: header to point to the > mailing list. > > > I have personal experience where "a modern journalling file system" > > (ext3) does *not* maintain integrity. I have now had three cases where > > the journal corrupted for no particular reason, causing the kernel to > > remount my drive read-only. A read-only and non-destructive read-write > > test failed to uncover any problems. > > > > My point was, and it still stands, "theoretically a file-system > > maintains its integrity, in practice it cannot". > > > > fsck is the tool that catches the difference between theory and > practice. > > It sounds like in your case it was the running kernel that noticed the > problem ( which in all likelihood was simply an IO error that happened > while the kernel tried to update the journal ), not the auto fsck at 30 > mounts. In any case, such errors occur only for the VAST minority of > users, so why should everyone be penalized? > > > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
[PATCH] Make x11-input-synaptics poll less frequently
Hi,
In an effort to make my laptop conserve more power I've used the
following patch, which decreases the polling frequency of the touchpad
by an order of one magnitude. This greatly lessens the amount of wakeups
on my machine. I haven't detected any misbehaviour when using it.
Original author is Florian Schäfer. [1]
Please consider including this to optimise the battery life of laptops
using a touchpad.
With kind regards,
Erik Andrén
[1] http://www.bughost.org/pipermail/power/2007-June/000602.html
diff --git a/syndaemon.c b/syndaemon.c
index 4730460..66cc8bf 100644
--- a/syndaemon.c
+++ b/syndaemon.c
@@ -161,7 +161,7 @@ get_time()
static void
main_loop(Display *display, double idle_time)
{
-const int poll_delay = 2; /* 20 ms */
+const int poll_delay = 20; /* 200 ms */
double last_activity = 0.0;
double current_time;
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
[PATCH] Make the Xorg smart scheduler smarter
Hi,
In an effort to reduce power consumption on my laptop, I'm trying out
different patches to reduce the amount of wakeups on my machine and
tracing the process using the powertop utility.
One of the biggest offenders for my laptop is the do_setitimer function
in Xorg. Arjan van de Ven has developed a patch which optimises the
smart scheduler and works around this problem. [1]
I have been using this patch now for a couple of days without noticing
any problems and it has reduced the amount of ticks per second immensly.
Please review and consider for inclusion in Ubuntu Hardy.
With kind regards,
Erik Andrén
[1] http://www.bughost.org/pipermail/power/2007-October/001107.html
>From 48e4d08e99de41047c6b6fde5ba9d12787881c23 Mon Sep 17 00:00:00 2001
From: root <[EMAIL PROTECTED]>
Date: Sun, 28 Oct 2007 09:37:52 +0100
Subject: [PATCH] The smart scheduler itimer currently always fires after each request
(which in turn causes the CPU to wake out of idle, burning precious power).
Rather than doing this, just stop the timer before going into the select()
portion of the WaitFor loop. It's a cheap system call, and it will only get
called if there's no more commands batched up from the active fd.
This change also allows some of the functions to be simplified; setitimer()
will only fail if it's passed invalid data, and we don't do that... so make
it void and remove all the conditional code that deals with failure.
The change also allows us to remove a few variables that were used for
housekeeping between the signal handler and the main loop.
---
include/dixstruct.h |6 ++
os/WaitFor.c| 11 +++
os/utils.c | 28 +++-
3 files changed, 8 insertions(+), 37 deletions(-)
diff --git a/include/dixstruct.h b/include/dixstruct.h
index dd6347f..bed31dc 100644
--- a/include/dixstruct.h
+++ b/include/dixstruct.h
@@ -150,11 +150,9 @@ extern long SmartScheduleTime;
extern long SmartScheduleInterval;
extern long SmartScheduleSlice;
extern long SmartScheduleMaxSlice;
-extern unsigned long SmartScheduleIdleCount;
extern Bool SmartScheduleDisable;
-extern Bool SmartScheduleIdle;
-extern Bool SmartScheduleTimerStopped;
-extern Bool SmartScheduleStartTimer(void);
+extern void SmartScheduleStartTimer(void);
+extern void SmartScheduleStopTimer(void);
#define SMART_MAX_PRIORITY (20)
#define SMART_MIN_PRIORITY (-20)
diff --git a/os/WaitFor.c b/os/WaitFor.c
index ec1592c..7683477 100644
--- a/os/WaitFor.c
+++ b/os/WaitFor.c
@@ -217,7 +217,8 @@ WaitForSomething(int *pClientsReady)
XFD_COPYSET(&AllSockets, &LastSelectMask);
#ifdef SMART_SCHEDULE
}
- SmartScheduleIdle = TRUE;
+ SmartScheduleStopTimer ();
+
#endif
BlockHandler((pointer)&wt, (pointer)&LastSelectMask);
if (NewOutputPending)
@@ -237,13 +238,7 @@ WaitForSomething(int *pClientsReady)
selecterr = GetErrno();
WakeupHandler(i, (pointer)&LastSelectMask);
#ifdef SMART_SCHEDULE
- if (i >= 0)
- {
- SmartScheduleIdle = FALSE;
- SmartScheduleIdleCount = 0;
- if (SmartScheduleTimerStopped)
- (void) SmartScheduleStartTimer ();
- }
+ SmartScheduleStartTimer ();
#endif
if (i <= 0) /* An error or timeout occurred */
{
diff --git a/os/utils.c b/os/utils.c
index 31cb0af..6fc1f7d 100644
--- a/os/utils.c
+++ b/os/utils.c
@@ -1513,10 +1513,6 @@ XNFstrdup(const char *s)
#ifdef SMART_SCHEDULE
-unsigned long SmartScheduleIdleCount;
-Bool SmartScheduleIdle;
-Bool SmartScheduleTimerStopped;
-
#ifdef SIGVTALRM
#define SMART_SCHEDULE_POSSIBLE
#endif
@@ -1526,7 +1522,7 @@ Bool SmartScheduleTimerStopped;
#define SMART_SCHEDULE_TIMER ITIMER_REAL
#endif
-static void
+void
SmartScheduleStopTimer (void)
{
#ifdef SMART_SCHEDULE_POSSIBLE
@@ -1537,38 +1533,28 @@ SmartScheduleStopTimer (void)
timer.it_value.tv_sec = 0;
timer.it_value.tv_usec = 0;
(void) setitimer (ITIMER_REAL, &timer, 0);
-SmartScheduleTimerStopped = TRUE;
#endif
}
-Bool
+void
SmartScheduleStartTimer (void)
{
#ifdef SMART_SCHEDULE_POSSIBLE
struct itimerval timer;
-SmartScheduleTimerStopped = FALSE;
timer.it_interval.tv_sec = 0;
timer.it_interval.tv_usec = SmartScheduleInterval * 1000;
timer.it_value.tv_sec = 0;
timer.it_value.tv_usec = SmartScheduleInterval * 1000;
-return setitimer (ITIMER_REAL, &timer, 0) >= 0;
+setitimer (ITIMER_REAL, &timer, 0);
#endif
-return FALSE;
}
#ifdef SMART_SCHEDULE_POSSIBLE
static void
SmartScheduleTimer (int sig)
{
-int olderrno = errno;
-
SmartScheduleTime += SmartScheduleInterval;
-if (SmartScheduleIdle)
-{
- SmartScheduleStopTimer ();
-}
-errno = olderrno;
}
#endif
@@ -1592,14 +1578,6 @@ SmartScheduleInit (void)
perror ("sigaction for smart scheduler");
return FALSE;
}
-/* Set up the virtual timer */
-if (!SmartScheduleStartTimer ())
-{
- perror ("scheduling timer&
