tom arnall wrote:
i attempted the distr-upgrade and after i rebooted did:
[EMAIL PROTECTED]:~$ uname -r
2.6.16.4
so i did the distr-upgrade again. following is the session output. '31 not
fully installed or removed.' is where it gets interesting:
[EMAIL PROTECTED]:~$ sudo apt-get
On Sunday 20 January 2008 11:46, Marty wrote:
tom arnall wrote:
i attempted the distr-upgrade and after i rebooted did:
[EMAIL PROTECTED]:~$ uname -r
2.6.16.4
so i did the distr-upgrade again. following is the session output. '31
not fully installed or removed.' is where it gets
On Sun, Jan 20, 2008 at 11:20:03 -0800, tom arnall wrote:
i attempted the distr-upgrade and after i rebooted did:
[EMAIL PROTECTED]:~$ uname -r
2.6.16.4
I think you should follow the Sarge-Etch upgrade notes, adapting them
to your somewhat different situation. There are a couple of issues to
tom arnall wrote:
On Sunday 20 January 2008 11:46, Marty wrote:
tom arnall wrote:
i attempted the distr-upgrade and after i rebooted did:
[EMAIL PROTECTED]:~$ uname -r
2.6.16.4
so i did the distr-upgrade again. following is the session output. '31
not fully installed or removed.' is
On Sunday 20 January 2008 12:17, Marty wrote:
tom arnall wrote:
On Sunday 20 January 2008 11:46, Marty wrote:
tom arnall wrote:
i attempted the distr-upgrade and after i rebooted did:
[EMAIL PROTECTED]:~$ uname -r
2.6.16.4
so i did the distr-upgrade again. following is the
On Sunday 20 January 2008 12:37, Marty wrote:
tom arnall wrote:
Marty,
should i be concerned about the following. i did this without pointing
sources.list to the new repository.
Well, fix that. :-)
[EMAIL PROTECTED]:~$ sudo apt-get dist-upgrade
It's a typical cascade of errors
tom arnall wrote:
Marty,
should i be concerned about the following. i did this without pointing
sources.list to the new repository.
Well, fix that. :-)
[EMAIL PROTECTED]:~$ sudo apt-get dist-upgrade
It's a typical cascade of errors caused by the first few individual package
On Sunday 20 January 2008 12:03, Florian Kulzer wrote:
On Sun, Jan 20, 2008 at 11:20:03 -0800, tom arnall wrote:
i attempted the distr-upgrade and after i rebooted did:
[EMAIL PROTECTED]:~$ uname -r
2.6.16.4
I think you should follow the Sarge-Etch upgrade notes, adapting them
to your
On Sun, Jan 20, 2008 at 02:46:31PM -0500, Marty [EMAIL PROTECTED] was heard
to say:
tom arnall wrote:
i attempted the distr-upgrade and after i rebooted did:
[EMAIL PROTECTED]:~$ uname -r
2.6.16.4
so i did the distr-upgrade again. following is the session output. '31
not fully installed
tom arnall wrote:
On Sunday 20 January 2008 12:37, Marty wrote:
tom arnall wrote:
Marty,
should i be concerned about the following. i did this without pointing
sources.list to the new repository.
Well, fix that. :-)
[EMAIL PROTECTED]:~$ sudo apt-get dist-upgrade
It's a typical cascade
When installing a new system (etch), is there any trick I need to know for
getting my home directory right? I have the one from old system backed up.
When I go to restore it on the new system, I assume the installer will have
put some kind of home directory on the new system under my username.
tom arnall wrote:
When installing a new system (etch), is there any trick I need to know for
getting my home directory right? I have the one from old system backed up.
When I go to restore it on the new system, I assume the installer will have
put some kind of home directory on the new system
On Sunday 20 January 2008 14:32, Marty wrote:
tom arnall wrote:
When installing a new system (etch), is there any trick I need to know
for getting my home directory right? I have the one from old system
backed up. When I go to restore it on the new system, I assume the
installer will
tom arnall wrote:
On Sunday 20 January 2008 14:32, Marty wrote:
The simplest solution is to start with a new drive. Unplug and remove your
current drive if it contains anything valuable, put it in a safe place. As
the saying goes, when you're stuck in the hole, stop digging.
don't have
On Sunday 20 January 2008 15:36, Marty wrote:
tom arnall wrote:
On Sunday 20 January 2008 14:32, Marty wrote:
The simplest solution is to start with a new drive. Unplug and remove
your current drive if it contains anything valuable, put it in a safe
place. As the saying goes, when
On Sunday 20 January 2008 17:49, Marty wrote:
tom arnall wrote:
besides my home directory, what else should i think about backing up?
I would back up etc as well.
what would be the advantage of 'rsync'?
It makes perfect copies of directory trees.
is there a problem with 'cp -R' in this
tom arnall wrote:
besides my home directory, what else should i think about backing up?
I would back up etc as well.
what would be the advantage of 'rsync'?
It makes perfect copies of directory trees.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
tom arnall wrote:
On Sunday 20 January 2008 17:49, Marty wrote:
tom arnall wrote:
besides my home directory, what else should i think about backing up?
I would back up etc as well.
Come to think of it, I might also grab var, and maybe run dpkg-query and save
the output, to make
18 matches
Mail list logo
