Sylvain Sauvage [EMAIL PROTECTED] writes:
Goswin von Brederlow, dimanche 21 janvier 2007, 22:21:07 CET
smugzilla [EMAIL PROTECTED] writes:
[...]
I choose No when asked if I really want
to remove the running kernel, then get two more error messages:
dpkg: error procecssing
[EMAIL PROTECTED] writes:
On Mon, Jan 22, 2007 at 06:51:20PM +1100, Hamish Moffatt wrote:
On Sun, Jan 21, 2007 at 07:49:21PM -0600, smugzilla wrote:
That brings me to my next question: why are the kernel naming
conventions inconsistent? uname -r says I am currently running
On Sun, Jan 21, 2007 at 11:58:02AM -0600, smugzilla wrote:
I'm trying a fresh install of debian on my old Athlon 64 3200 box and
this one is not proceeding as smoothly as the previous one. The initial
install is smooth enough (I'm not even trying to install gnome yet) but
I'm having
On Mon, Jan 22, 2007 at 06:51:20PM +1100, Hamish Moffatt wrote:
On Sun, Jan 21, 2007 at 07:49:21PM -0600, smugzilla wrote:
That brings me to my next question: why are the kernel naming
conventions inconsistent? uname -r says I am currently running
2.6.8-em64t-p4-smp but no corresponding
I'm trying a fresh install of debian on my old Athlon 64 3200 box and
this one is not proceeding as smoothly as the previous one. The initial
install is smooth enough (I'm not even trying to install gnome yet) but
I'm having problems as soon as I try to upgrade to sid. Basically the
chain of
Hi
You may be able to do some tricks for saving your system but I don't know
if you save time on it. If it boots and dpkg works, then you can download
initrdtools by hand and do dpkg -i initrd*.deb. What I can recommend is that
you use dselect to select the packages you really want to
smugzilla [EMAIL PROTECTED] writes:
I'm trying a fresh install of debian on my old Athlon 64 3200 box and
this one is not proceeding as smoothly as the previous one. The
initial install is smooth enough (I'm not even trying to install gnome
yet) but I'm having problems as soon as I try to
Goswin von Brederlow, dimanche 21 janvier 2007, 22:21:07 CET
smugzilla [EMAIL PROTECTED] writes:
[...]
I choose No when asked if I really want
to remove the running kernel, then get two more error messages:
dpkg: error procecssing kernel-image-2.6.8.12...
[...]
The only problem is that
Goswin von Brederlow wrote:
smugzilla [EMAIL PROTECTED] writes:
I'm trying a fresh install of debian on my old Athlon 64 3200 box and
this one is not proceeding as smoothly as the previous one. The
initial install is smooth enough (I'm not even trying to install gnome
yet) but I'm having
On Sun, Jan 21, 2007 at 07:49:21PM -0600, smugzilla wrote:
That brings me to my next question: why are the kernel naming
conventions inconsistent? uname -r says I am currently running
2.6.8-em64t-p4-smp but no corresponding version of kernel 2.6.18 is
available from Arizona's sid
Douglas Allan Tutty wrote:
On Sun, Jan 21, 2007 at 07:49:21PM -0600, smugzilla wrote:
That brings me to my next question: why are the kernel naming
conventions inconsistent? uname -r says I am currently running
2.6.8-em64t-p4-smp but no corresponding version of kernel 2.6.18 is
available
On Sun January 21 2007 17:49, smugzilla wrote:
That brings me to my next question: why are the kernel naming
conventions inconsistent? uname -r says I am currently running
2.6.8-em64t-p4-smp but no corresponding version of kernel 2.6.18 is
available from Arizona's sid repository. They do have
On Sun, Jan 21, 2007 at 07:49:21PM -0600, smugzilla wrote:
That brings me to my next question: why are the kernel naming
conventions inconsistent? uname -r says I am currently running
2.6.8-em64t-p4-smp but no corresponding version of kernel 2.6.18 is
available from Arizona's sid
13 matches
Mail list logo
