FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 03-18-2009, 05:37 PM
Ron Rhodes
 
Default (no subject)

Vincent wrote:
> On Wed, Mar 18, 2009 at 10:59 AM, Chris Ross <kristoff101@gmail.com> wrote:
>
>
>> I have the following hardware
>> Sony Picturebook PCG-C1XD
>> Pentium II 400 MHz
>> 128 MB Ram
>> 10Gb HDD
>> USB floppy
>> PCMCIA CD Drive
>> Display adapter Neomagic Magicmedia 256AV
>>
>> Due to the amount of available Ram I wonder whether or not I should go with
>> release 8.1 given the recommended config below, or go for an earlier
>> version.
>>
>> I will be using the laptop to browse and possible use with skype.
>>
>> I understand that installing should be done using the alternative installer
>> given the limited amount of memory.
>>
>> 8.10, (Intrepid Ibex) - "Xubuntu can run with starting from 192 (or even
>> just 128) MB RAM, but it is strongly recommended to have at least 256 MB
>> RAM"
>>
>> --
>> Thanks
>> Chris
>>
>>
>>
> 128MB RAM is going to be very, very unpleasant. Especially Skype will be a
> problem (it uses Qt libraries as opposed to GTK like most of Xubuntu, which
> means that will all have to be loaded in memory additionally which won't
> help speed-wise). Perhaps if you just browse with a light-weight browser it
> might be bearable, but really not recommended.
>
> You might want to check out a lighter distro, perhaps to get at least a bit
> of a user-friendly experience you might go with a light-weight Xfce-distro
> such as Wolvix (http://wolvix.org/), if not, something like Puppy Linux is
> probably the way to go.
>
> Or course, considering how it's all free-of-charge, you might as well just
> give it a try and see if you can bear it ;-)
> An older version of Xubuntu is probably either nothing better or too old to
> be supported and thus _strongly_ recommended against.
>
> Good luck,
>
Have you thought about upgrading your RAM to 256MB. The first thing to
do is open your computer up and see if you can identify the RAM, if it
is accessible and you can remove it you are halfway there. Next search
on google for the 256MB equivalent and check out prices, RAM is not
expensive these days. If your not risk averse you can try Ebay, I've
picked up RAM there for a few pence, the main expense being P&P.

HTH, Ron

--
xubuntu-users mailing list
xubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
 
Old 03-19-2009, 07:27 AM
"Nikolaus Gaberszig"
 
Default (no subject)

On 18 Mar 2009 Ron Rhodes wrote about Re: [xubuntu-users] (no subject):

> Have you thought about upgrading your RAM to 256MB.

IIRC the PCG-C1XD only supports 192 MB RAM (64 built-in + 128 additional)

Greetings
Nikolaus

--
Nikolaus Gaberszig



--
xubuntu-users mailing list
xubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
 
Old 03-21-2009, 09:18 PM
Daniel Hays
 
Default (no subject)

Hi there,

*

Could you please remove me from your mailing list?

*

Thank you

*

Daniel

Let ninemsn property help. Need a new place to rent, share or buy?
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 03-22-2009, 12:04 AM
Victor Padro
 
Default (no subject)

2009/3/21 Daniel Hays <e664295@hotmail.co.uk>






Hi there,

*

Could you please remove me from your mailing list?

*

Thank you

*

Daniel

Let ninemsn property help. Need a new place to rent, share or buy?


_______________________________________________

CentOS mailing list

CentOS@centos.org

http://lists.centos.org/mailman/listinfo/centos



We can't do that...
you have to do it by yourself.
go here and give it a try:
http://lists.centos.org/mailman/listinfo/centos

--
"It is human nature to think wisely and act in an absurd fashion."

"Todo el desorden del mundo proviene de las profesiones mal o mediocremente servidas"

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 10-30-2009, 10:21 PM
"Amedee Van Gasse (ub)"
 
Default (no subject)

On Fri, October 30, 2009 22:34, Chi Gao wrote:
> Hi I have reinstalled it and it again comes the problem when 73%

What is "it"? Your iPhone?
What is "the problem"?
Please replace "it" and "the problem" with actual words that describe
something.

> see attached file

There is no attached file.


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 11-17-2009, 02:34 PM
Mike Snitzer
 
Default (no subject)

From: Mikulas Patocka <mpatocka@redhat.com>

Subject: [PATCH] dm snapshot: rework writing to snapshot origin

The previous code selected one exception as "primary_pe", linked all
other exceptions on it and used reference counting to wait until all
exceptions are reallocated. This didn't work with exceptions with
different chunk sizes:
https://bugzilla.redhat.com/show_bug.cgi?id=182659

I removed all the complexity with exceptions linking and reference
counting. Currently, bio is linked on one exception and when that
exception is reallocated, the bio is retried to possibly wait for
other exceptions.

Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
---
drivers/md/dm-snap.c | 167 +++++++++++++++++----------------------------------
1 file changed, 58 insertions(+), 109 deletions(-)

Index: linux-2.6/drivers/md/dm-snap.c
================================================== =================
--- linux-2.6.orig/drivers/md/dm-snap.c
+++ linux-2.6/drivers/md/dm-snap.c
@@ -153,28 +153,6 @@ struct dm_snap_pending_exception {
struct bio_list origin_bios;
struct bio_list snapshot_bios;

- /*
- * Short-term queue of pending exceptions prior to submission.
- */
- struct list_head list;
-
- /*
- * The primary pending_exception is the one that holds
- * the ref_count and the list of origin_bios for a
- * group of pending_exceptions. It is always last to get freed.
- * These fields get set up when writing to the origin.
- */
- struct dm_snap_pending_exception *primary_pe;
-
- /*
- * Number of pending_exceptions processing this chunk.
- * When this drops to zero we must complete the origin bios.
- * If incrementing or decrementing this, hold pe->snap->lock for
- * the sibling concerned and not pe->primary_pe->snap->lock unless
- * they are the same.
- */
- atomic_t ref_count;
-
/* Pointer back to snapshot context */
struct dm_snapshot *snap;

@@ -961,6 +939,28 @@ static void flush_queued_bios(struct wor
flush_bios(queued_bios);
}

+static int do_origin(struct dm_dev *origin, struct bio *bio);
+
+/*
+ * Flush a list of buffers.
+ */
+static void retry_origin_bios(struct dm_snapshot *s, struct bio *bio)
+{
+ struct bio *n;
+ int r;
+
+ while (bio) {
+ n = bio->bi_next;
+ bio->bi_next = NULL;
+ r = do_origin(s->origin, bio);
+ if (r == DM_MAPIO_REMAPPED)
+ generic_make_request(bio);
+ else
+ BUG_ON(r != DM_MAPIO_SUBMITTED);
+ bio = n;
+ }
+}
+
/*
* Error a list of buffers.
*/
@@ -994,39 +994,6 @@ static void __invalidate_snapshot(struct
dm_table_event(s->ti->table);
}

-static void get_pending_exception(struct dm_snap_pending_exception *pe)
-{
- atomic_inc(&pe->ref_count);
-}
-
-static struct bio *put_pending_exception(struct dm_snap_pending_exception *pe)
-{
- struct dm_snap_pending_exception *primary_pe;
- struct bio *origin_bios = NULL;
-
- primary_pe = pe->primary_pe;
-
- /*
- * If this pe is involved in a write to the origin and
- * it is the last sibling to complete then release
- * the bios for the original write to the origin.
- */
- if (primary_pe &&
- atomic_dec_and_test(&primary_pe->ref_count)) {
- origin_bios = bio_list_get(&primary_pe->origin_bios);
- free_pending_exception(primary_pe);
- }
-
- /*
- * Free the pe if it's not linked to an origin write or if
- * it's not itself a primary pe.
- */
- if (!primary_pe || primary_pe != pe)
- free_pending_exception(pe);
-
- return origin_bios;
-}
-
static void pending_complete(struct dm_snap_pending_exception *pe, int success)
{
struct dm_exception *e;
@@ -1075,7 +1042,8 @@ static void pending_complete(struct dm_s
out:
dm_remove_exception(&pe->e);
snapshot_bios = bio_list_get(&pe->snapshot_bios);
- origin_bios = put_pending_exception(pe);
+ origin_bios = bio_list_get(&pe->origin_bios);
+ free_pending_exception(pe);

up_write(&s->lock);

@@ -1085,7 +1053,7 @@ static void pending_complete(struct dm_s
else
flush_bios(snapshot_bios);

- flush_bios(origin_bios);
+ retry_origin_bios(s, origin_bios);
}

static void commit_callback(void *context, int success)
@@ -1172,8 +1140,6 @@ __find_pending_exception(struct dm_snaps
pe->e.old_chunk = chunk;
bio_list_init(&pe->origin_bios);
bio_list_init(&pe->snapshot_bios);
- pe->primary_pe = NULL;
- atomic_set(&pe->ref_count, 0);
pe->started = 0;

if (s->store->type->prepare_exception(s->store, &pe->e)) {
@@ -1181,7 +1147,6 @@ __find_pending_exception(struct dm_snaps
return NULL;
}

- get_pending_exception(pe);
dm_insert_exception(&s->pending, &pe->e);

return pe;
@@ -1441,14 +1406,21 @@ static int snapshot_iterate_devices(stru
/*-----------------------------------------------------------------
* Origin methods
*---------------------------------------------------------------*/
-static int __origin_write(struct list_head *snapshots, struct bio *bio)
+
+/*
+ * Returns:
+ * DM_MAPIO_REMAPPED: bio may be submitted to origin device
+ * DM_MAPIO_SUBMITTED: bio was queued on queue on one of exceptions
+ */
+
+static int __origin_write(struct list_head *snapshots,
+ sector_t sector, struct bio *bio)
{
- int r = DM_MAPIO_REMAPPED, first = 0;
+ int r = DM_MAPIO_REMAPPED;
struct dm_snapshot *snap;
struct dm_exception *e;
- struct dm_snap_pending_exception *pe, *next_pe, *primary_pe = NULL;
+ struct dm_snap_pending_exception *pe, *pe_to_start = NULL;
chunk_t chunk;
- LIST_HEAD(pe_queue);

/* Do all the snapshots on this origin */
list_for_each_entry (snap, snapshots, list) {
@@ -1460,22 +1432,19 @@ static int __origin_write(struct list_he
goto next_snapshot;

/* Nothing to do if writing beyond end of snapshot */
- if (bio->bi_sector >= dm_table_get_size(snap->ti->table))
+ if (sector >= dm_table_get_size(snap->ti->table))
goto next_snapshot;

/*
* Remember, different snapshots can have
* different chunk sizes.
*/
- chunk = sector_to_chunk(snap->store, bio->bi_sector);
+ chunk = sector_to_chunk(snap->store, sector);

/*
* Check exception table to see if block
* is already remapped in this snapshot
* and trigger an exception if not.
- *
- * ref_count is initialised to 1 so pending_complete()
- * won't destroy the primary_pe while we're inside this loop.
*/
e = dm_lookup_exception(&snap->complete, chunk);
if (e)
@@ -1505,59 +1474,39 @@ static int __origin_write(struct list_he
}
}

- if (!primary_pe) {
- /*
- * Either every pe here has same
- * primary_pe or none has one yet.
- */
- if (pe->primary_pe)
- primary_pe = pe->primary_pe;
- else {
- primary_pe = pe;
- first = 1;
- }
-
- bio_list_add(&primary_pe->origin_bios, bio);
-
- r = DM_MAPIO_SUBMITTED;
- }
+ r = DM_MAPIO_SUBMITTED;

- if (!pe->primary_pe) {
- pe->primary_pe = primary_pe;
- get_pending_exception(primary_pe);
+ if (bio) {
+ bio_list_add(&pe->origin_bios, bio);
+ bio = NULL;
+
+ if (!pe->started) {
+ pe->started = 1;
+ pe_to_start = pe;
+ }
}

if (!pe->started) {
pe->started = 1;
- list_add_tail(&pe->list, &pe_queue);
+ start_copy(pe);
}

next_snapshot:
up_write(&snap->lock);
}

- if (!primary_pe)
- return r;
-
/*
- * If this is the first time we're processing this chunk and
- * ref_count is now 1 it means all the pending exceptions
- * got completed while we were in the loop above, so it falls to
- * us here to remove the primary_pe and submit any origin_bios.
+ * pe_to_start is a small performance improvement:
+ * To avoid calling __origin_write N times for N snapshots, we start
+ * the snapshot where we queued the bio as the last one.
+ *
+ * If we start it as the last one, it finishes most likely as the last
+ * one and exceptions in other snapshots will be already finished when
+ * the bio will be retried.
*/

- if (first && atomic_dec_and_test(&primary_pe->ref_count)) {
- flush_bios(bio_list_get(&primary_pe->origin_bios));
- free_pending_exception(primary_pe);
- /* If we got here, pe_queue is necessarily empty. */
- return r;
- }
-
- /*
- * Now that we have a complete pe list we can start the copying.
- */
- list_for_each_entry_safe(pe, next_pe, &pe_queue, list)
- start_copy(pe);
+ if (pe_to_start)
+ start_copy(pe_to_start);

return r;
}
@@ -1573,7 +1522,7 @@ static int do_origin(struct dm_dev *orig
down_read(&_origins_lock);
o = __lookup_origin(origin->bdev);
if (o)
- r = __origin_write(&o->snapshots, bio);
+ r = __origin_write(&o->snapshots, bio->bi_sector, bio);
up_read(&_origins_lock);

return r;

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 11-18-2009, 03:39 PM
"Phil Sharrock"
 
Default (no subject)

Hi,

I have a problem logging out of Fedora 8.0

The logout window will not appear when the logout icon is clicked on.

I have to reboot or shutdown using poweroff.

Any ideas ?

Phil


************************************************** **************
This e-mail and any files transmitted with it are confidential
and solely for the use of the intended recipient. If you have
received this e-mail in error you should not disseminate,
distribute or copy it. Please notify the sender immediately and
delete this e-mail from your system.
************************************************** **************


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 11-18-2009, 04:31 PM
"Patrick O'Callaghan"
 
Default (no subject)

On Wed, 2009-11-18 at 16:39 +0000, Phil Sharrock wrote:
> Hi,
>
> I have a problem logging out of Fedora 8.0

F8 hasn't been supported for over a year now.

> The logout window will not appear when the logout icon is clicked on.

Which desktop? Gnome? KDE? Other?

> I have to reboot or shutdown using poweroff.

Kill the desktop manager, e.g. (as root) "pkill kdm" or "pkill gdm" as
appropriate. Or do "init 3; init 5".

poc


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 11-18-2009, 09:31 PM
Anderson Aparecido
 
Default (no subject)

--
--
Att,

Anderson Aparecido
-----------------------------
Precisando de um Tecnico de Informatica ?
Acesse: www.tecnicocampinas.com.br

--
*.~.
/ *v * *Seja Livre, use GNU/Linux!
/( * * )
^^-^^
--



_______________________________________________
Fedora-games-list mailing list
Fedora-games-list@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-games-list
 
Old 11-21-2009, 02:08 AM
NoOp
 
Default (no subject)

On 11/21/2009 03:06 PM, Harry Paterson wrote:
(no subject)
Recommend that you restart with a valid subject & post again. Many
(most) folks might drop a '(no subject)' in the bin without looking at it.



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 

Thread Tools




All times are GMT. The time now is 12:42 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org