What do you mean by merging? The code is totally different, it's
impossible to merge together.
Xavier Claessens
On mar, 2008-08-12 at 08:16 +0100, Andrew Sayers wrote:
How about merging with Ekiga? That would give you more developers and a
simple route towards being included in the default
On Mon, Aug 11, 2008 at 02:09:19PM -0700, Bryce Harrington wrote:
On Mon, Aug 11, 2008 at 11:52:25AM +0100, Matt Zimmerman wrote:
== Filesystem checking / AutoFsck ==
A suggestion was made to the technical board that Ubuntu could be smarter
about how and when it performs filesystem
Xavier Claessens wrote:
What do you mean by merging? The code is totally different, it's
impossible to merge together.
Xavier Claessens
I'm talking more about merging the projects than the codebases - finding
a way that you can all work on a single project that would satisfy users
and
Matt Zimmerman wrote:
On Mon, Aug 11, 2008 at 02:09:19PM -0700, Bryce Harrington wrote:
On Mon, Aug 11, 2008 at 11:52:25AM +0100, Matt Zimmerman wrote:
Some of the other ideas which have been proposed are:
Run fsck during shutdown (when the user isn't expecting to be able to use
the
On mar, 2008-08-12 at 11:50 +0100, Andrew Sayers wrote:
Xavier Claessens wrote:
What do you mean by merging? The code is totally different, it's
impossible to merge together.
Xavier Claessens
I'm talking more about merging the projects than the codebases - finding
a way that you can
On Tue, Aug 12, 2008 at 08:57:36PM +1000, Ian Chennell wrote:
Matt Zimmerman wrote:
On Mon, Aug 11, 2008 at 02:09:19PM -0700, Bryce Harrington wrote:
On Mon, Aug 11, 2008 at 11:52:25AM +0100, Matt Zimmerman wrote:
Some of the other ideas which have been proposed are:
Run fsck
2008/8/12 Lars Wirzenius [EMAIL PROTECTED]:
A way to avoid that would be to set up systems with LVM, and use an LVM
snapshot volume for running fsck. This would give fsck a frozen snapshot
of the system, and should work better. However, it requires some free
space to be used, and I haven't
I've been bitten bad by e2fsck where it's borked my system such that
I've had to reinstall. Since I don't want to be forced into that again,
I'm trying to disable it permanently and take my chances on losing a
file here or there.
However, I can't seem to shut it off.
So far, I've used
On Tue, Aug 12, 2008 at 10:07 AM, Paul S [EMAIL PROTECTED] wrote:
I've been bitten bad by e2fsck where it's borked my system such that
I've had to reinstall. Since I don't want to be forced into that again,
I'm trying to disable it permanently and take my chances on losing a
file here or
On Tue, Aug 12, 2008 at 10:29 AM, Alexander Jones [EMAIL PROTECTED] wrote:
2008/8/12 Mackenzie Morgan [EMAIL PROTECTED]:
On Tue, Aug 12, 2008 at 10:07 AM, Paul S [EMAIL PROTECTED] wrote:
I've been bitten bad by e2fsck where it's borked my system such that
I've had to reinstall. Since I don't
ti, 2008-08-12 kello 15:07 +0100, Matt Zimmerman kirjoitti:
On Tue, Aug 12, 2008 at 02:59:22PM +0100, Alexander Jones wrote:
2008/8/12 Lars Wirzenius [EMAIL PROTECTED]:
A way to avoid that would be to set up systems with LVM, and use an LVM
snapshot volume for running fsck. This would
On Tue, Aug 12, 2008 at 06:17:36PM +0300, Lars Wirzenius wrote:
ti, 2008-08-12 kello 15:07 +0100, Matt Zimmerman kirjoitti:
Indeed. The best we could do in a scenario like this would be to flag the
filesystem dirty so that it gets checked the next time it's possible.
I assume you mean the
Matt Zimmerman wrote:
The LVM solution isn't viable anyway; there's no guarantee that the metadata
on disk is in any way consistent while the filesystem is mounted. The
problem in your test isn't only that the filesystem is changing from
underneath it, it's also that it may not have been
Hi Bryce,
I mostly suspend my laptop, so shutting it down and rebooting is not
really done that often. Which means that I hit the day count more then I
hit the mount count. If you want, you can change the mount based
counting to a higher number with tune2fs (see the -c option in man
tune2fs). So
Olá Laurent e a todos.
I have testing it today.
For now, 2 small things:
There no window opening when a new conversation comes (even as an option) and i
cant change the name of my accounts.
Should I file this as bugs?
--
BUGabundo :o)
(``-_-´´) http://Ubuntu.BUGabundo.net
Linux user
Le mardi 12 août 2008 à 18:09 +0100, (``-_-´´) -- Fernando a écrit :
Olá Laurent e a todos.
I have testing it today.
For now, 2 small things:
There no window opening when a new conversation comes (even as an option) and
i cant change the name of my accounts.
Should I file this as bugs?
On Sat, 9 Aug 2008 16:55:29 +0200
Marcin ‘Qrczak’ Kowalczyk [EMAIL PROTECTED] wrote:
2008/8/8 Laurent Bigonville [EMAIL PROTECTED]:
The ubuntu desktop team considers using it instead of Pidgin for
intrepid as default IM client.
Please not, until Empathy supports protocols that Pidgin
On Tue, Aug 12, 2008 at 11:15:05AM +0100, Matt Zimmerman wrote:
On Mon, Aug 11, 2008 at 02:09:19PM -0700, Bryce Harrington wrote:
On Mon, Aug 11, 2008 at 11:52:25AM +0100, Matt Zimmerman wrote:
== Filesystem checking / AutoFsck ==
A suggestion was made to the technical board that
Seeing it from the perspective of an common user, fsck is something
whose function is unknown and therefore running it is senseless, so they
might turn if off directly or skip it always which is not good.
My idea:
- Mount the partition read-only
- Capture writes with something like AuFS/Union-FS
On Fri, Aug 8, 2008 at 10:12 PM, Laurent Bigonville [EMAIL PROTECTED] wrote:
Hello everyone,
Empathy[1] will be part of the upcoming GNOME 2.24 desktop.
The ubuntu desktop team considers using it instead of Pidgin for
intrepid as default IM client. If you are running intrepid, please give
On Mon, Aug 11, 2008 at 11:52:25AM +0100, Matt Zimmerman wrote:
== Filesystem checking / AutoFsck ==
A suggestion was made to the technical board that Ubuntu could be smarter
about how and when it performs filesystem integrity checks (fsck).
Decision: This should be discussed more
21 matches
Mail list logo