On Fri, Mar 30, 2007 at 12:08:37AM +0200, Martin Zobel-Helas wrote:
Hi,
On Thu Mar 29, 2007 at 14:57:47 -0700, Andrew Sackville-West wrote:
On Thu, Mar 29, 2007 at 06:50:40PM -0300, Fernando Cacciola wrote:
Hi All
I just installed Debian Sarge from a 1-year old netinst CD on a HP
Fernando Cacciola wrote:
Hi All
I just installed Debian Sarge from a 1-year old netinst CD on a HP
Pavillion 1125LA notebook.
Then I run apt-get dist-upgrade.
What do I have now then? Still Sarge? 3.0, 3.1?
The third field in /etc/apt/sources.list will tell you which distribution
Hi All
I just installed Debian Sarge from a 1-year old netinst CD on a HP Pavillion
1125LA notebook.
Then I run apt-get dist-upgrade.
What do I have now then? Still Sarge? 3.0, 3.1?
TIA
Fernando Cacciola
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
On Thu, Mar 29, 2007 at 06:50:40PM -0300, Fernando Cacciola wrote:
Hi All
I just installed Debian Sarge from a 1-year old netinst CD on a HP Pavillion
1125LA notebook.
Then I run apt-get dist-upgrade.
What do I have now then? Still Sarge? 3.0, 3.1?
You still have sarge, unless you
Hi,
On Thu Mar 29, 2007 at 14:57:47 -0700, Andrew Sackville-West wrote:
On Thu, Mar 29, 2007 at 06:50:40PM -0300, Fernando Cacciola wrote:
Hi All
I just installed Debian Sarge from a 1-year old netinst CD on a HP
Pavillion
1125LA notebook.
Then I run apt-get dist-upgrade.
Andrew Sackville-West wrote:
You still have sarge, unless you changed the sources.list to point to
something else. You've got the most recent sarge w/ security updates
(I think that is on by default). I guess that's 3.1 r3 or so.
OK.
Q: That's because Etch is not yet the official latest Debian?
On Thu, 29 Mar 2007 19:16:20 -0300
Fernando Cacciola [EMAIL PROTECTED] wrote:
Andrew Sackville-West wrote:
You still have sarge, unless you changed the sources.list to
point to something else. You've got the most recent sarge w/
security updates (I think that is on by default). I guess
the official latest
Debian? or because dist-upgrade won't ever move ahead from
Sarge?
dist-upgrade is capable of upgrading you to etch, but it depends
on what you have in your sources.list. If sources.lists
references sarge, then dist-upgrade will not upgrade you to
etch. If it references stable
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Sorry again. After I emailed my response, I realized I for got to run
lilo. So ran it and got this error:
ChatagnierL-Home:/home/lchata# lilo
Fatal: Image name, label, or alias is too long: 'Linux-2.4.27-2-386'
Marty wrote:
Debian User Leonard Chatagnier wrote:
See below for links. Not sure what you mean by what happens when you
boot
using LinuxOLD. It boots normally as it did since first installed.
I do see that
Output module failed to load as was the case on my old sarge. If
your refering
to
Debian User Leonard Chatagnier wrote:
You can, if you will, tell me just how you remove a kernel(outline the
process).
Like any other package: apt-get remove pkgname or use aptitude, dselect,
etc.
I don't use the packaged kernels so I don't know but if it tries to re-install
LILO, I would
On Fri, Jun 24, 2005 at 01:35:23PM +0100, Clive Menzies wrote:
On (24/06/05 23:29), Chris Bannister wrote:
On Thu, Jun 23, 2005 at 11:05:34AM -0500, Leonard Chatagnier wrote:
Now I'm worried. Note: I don't have a reiserfs file system, only an
ext3 fs since day one on all
Marty wrote:
Debian User Leonard Chatagnier wrote:
You can, if you will, tell me just how you remove a kernel(outline
the process).
Like any other package: apt-get remove pkgname or use aptitude,
dselect, etc.
I don't use the packaged kernels so I don't know but if it tries to
re-install
Debian User Leonard Chatagnier wrote:
The 2.4.27-2-386 kernel was forced on me by the dist-upgrade. I planned
on going to the 2.6.6-2-686 kernel and will eventually, probably
soon. Kent
finally fixed lilo for me so that sarge boots now if you haven't
already read it.
You can, if you will,
On Fri, 24 Jun 2005 22:15:31 -0500, Debian User Leonard Chatagnier
[EMAIL PROTECTED] wrote:
I'm still trying to get a stable system for the last six months that
I've been using Debian ... Out of 3 or 4 sarge installs, only the last
one via testing worked out of the box and booted normally. The
Kent West wrote:
Debian User Leonard Chatagnier wrote:
The 2.4.27-2-386 kernel was forced on me by the dist-upgrade. I planned
on going to the 2.6.6-2-686 kernel and will eventually, probably
soon. Kent
finally fixed lilo for me so that sarge boots now if you haven't
already read it.
You
--- Kent West [EMAIL PROTECTED] wrote:
Leonard Chatagnier wrote:
VFS: Cannot open rootdevice 301 or 30:01
Please append a correct root= boot option
Kernel panic: VFS unable to mount root fs on 30:01
Ok, not worried at this time as I have my woody
CD's and can do a
rescbf24 to mount
On Thu, Jun 23, 2005 at 11:05:34AM -0500, Leonard Chatagnier wrote:
Now I'm worried. Note: I don't have a reiserfs file system, only an
ext3 fs since day one on all partitions.
If anyone can help me to get the system bootable again, I think I can
correct the lilo.conf problem
On (24/06/05 23:29), Chris Bannister wrote:
On Thu, Jun 23, 2005 at 11:05:34AM -0500, Leonard Chatagnier wrote:
Now I'm worried. Note: I don't have a reiserfs file system, only an
ext3 fs since day one on all partitions.
If anyone can help me to get the system bootable
Debian User Leonard Chatagnier wrote:
-Doesn't look like Kent is going to reply
to my last post:
I missed seeing any such post. Nor do I find one in the archives:
http://lists.debian.org/debian-user/2005/06/thrd8.html
--
Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
VFS: Cannot open rootdevice 301 or 30:01
Please append a correct root= boot option
Kernel panic: VFS unable to mount root fs on
Debian User Leonard Chatagnier wrote:
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
Kent West wrote:
Sarge's boot is hosed, but you've tried to boot off the Woody
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
Kent West wrote:
Sarge's boot is hosed, but you've
Debian User Leonard Chatagnier wrote:
Kent West wrote:
The line should be:
initrd=/initrd.img
I put the / in front of initrd.img and rebooted with kernel panic
again giving
these same boot messages:
VFS: Cannot open root device 301 or 03:01
Please append a correct root= boot
Debian User Leonard Chatagnier wrote:
The output of cat /etc/fstab, cfdisk and lilo.conf are shown at the end
of this message.
Hi Leonard,
I looked over your files. First did you verify the links /vmlinuz
and /vmlinuz.old? Second, what happens when you boot using LinuxOLD?
(Lacking an
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
Kent West wrote:
Sarge's boot is hosed, but you've
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Kent West wrote:
The line should be:
initrd=/initrd.img
I put the / in front of initrd.img and rebooted with kernel panic
again giving
these same boot messages:
VFS: Cannot open root device 301 or 03:01
Please
Marty wrote:
Debian User Leonard Chatagnier wrote:
The output of cat /etc/fstab, cfdisk and lilo.conf are shown at the end
of this message.
Hi Leonard,
I looked over your files. First did you verify the links /vmlinuz
and /vmlinuz.old? Second, what happens when you boot using LinuxOLD?
Debian User Leonard Chatagnier wrote:
See below for links. Not sure what you mean by what happens when you boot
using LinuxOLD. It boots normally as it did since first installed. I do see
that
Output module failed to load as was the case on my old sarge. If your refering
to my notes about
Debian User Leonard Chatagnier wrote:
Sorry again. After I emailed my response, I realized I for got to run
lilo. So ran it and got this error:
ChatagnierL-Home:/home/lchata# lilo
Fatal: Image name, label, or alias is too long: 'Linux-2.4.27-2-386'
ChatagnierL-Home:/home/lchata#
So, I
So frustrating, just fixed KDE Knotify problem and Debian only stayed fixed
until installed a dist-upgrade.
Stayed fixed less than a day. Ok, the problem is related to lilo.conf
for an initrd.img. I followed the dist-upgrade messages closely and
thought I did it as described, but apparently
Leonard Chatagnier wrote:
VFS: Cannot open rootdevice 301 or 30:01
Please append a correct root= boot option
Kernel panic: VFS unable to mount root fs on 30:01
Ok, not worried at this time as I have my woody CD's and can do a
rescbf24 to mount woody still installed and correct the lilo.conf
--- Kent West [EMAIL PROTECTED] wrote:
Leonard Chatagnier wrote:
VFS: Cannot open rootdevice 301 or 30:01
Please append a correct root= boot option
Kernel panic: VFS unable to mount root fs on 30:01
Ok, not worried at this time as I have my woody
CD's and can do a
rescbf24 to
Luis Finotti wrote:
Dear Basajaun and all,
Basajaun wrote:
[snip]
Well, you could try the old link trick. First of all locate the biggest
directory(ies) residing in /, e.g.
du -sh /*
then, move that directory and all of its contents to a bigger
partition, where space is not a
Leonard Chatagnier wrote:
Leonard Chatagnier said:
tar: ./lib/modules/2.6.8-2-686/modules.symbols: Cannot write: No space
left on device
tar: Error exit delayed from previous errors
I chacked partition space with df and seem to have ample room as shown
ChatagnierL-Home:~# df
Filesystem
Joris Huizer wrote:
Leonard Chatagnier wrote:
Leonard Chatagnier said:
tar: ./lib/modules/2.6.8-2-686/modules.symbols: Cannot write: No
space left on device
tar: Error exit delayed from previous errors
I chacked partition space with df and seem to have ample room as shown
[snip]
Phil said:
Your / partition is where /lib lives, and you've only got ~18MB. I'd say
your modules directory should take up more than that. 30MB+. Prolly not
enough space.
Hey Phil, thanks, that explains it. Now how to get more space on /? I
could resize partitions with cfdisk and
On Wed, Jun 08, 2005 at 05:36:21AM -0400, Tom Allison wrote:
if resizing / really cannot be done, maybe create a new /lib partition
instead
Don't do this! /lib, /bin and /etc MUST be on your root filesystem or
the system won't boot.
Frank
--
Debugging is twice as hard as writing the code
Obviously, the following line:
cp -R /big_dir /scratch/
should read:
mv /big_dir /scratch/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Thanks to all you guys for your suggestions. I'll have to study a while
before I decide how to proceed as I tend
to get symlinks backwards even after reading man. I actually feel more
comfortable resizind partitions.
One thing I'd like to kow before closing this thread, how does one know,
or
Dear Basajaun and all,
Basajaun wrote:
[snip]
Well, you could try the old link trick. First of all locate the biggest
directory(ies) residing in /, e.g.
du -sh /*
then, move that directory and all of its contents to a bigger
partition, where space is not a problem, e.g.
cp -R /big_dir
I was running Testing Sarge 2.6.8-2-686-13 Stock and just completed
wajig distupgrading to Stable Sarge picking up a
new version of the 2.6.8-2-686 KI-16(I think). Everything went smoothly
until unpacking and installing modules.
The following is an example of the error output except that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leonard Chatagnier said:
tar: ./lib/modules/2.6.8-2-686/modules.symbols: Cannot write: No space
left on device
tar: Error exit delayed from previous errors
I chacked partition space with df and seem to have ample room as shown
Leonard Chatagnier said:
tar: ./lib/modules/2.6.8-2-686/modules.symbols: Cannot write: No space
left on device
tar: Error exit delayed from previous errors
I chacked partition space with df and seem to have ample room as shown
ChatagnierL-Home:~# df
Filesystem 1K-blocks Used
would a dpkg-reconifigure xserver-xfree86 have fixed this??
C
On Thursday 06 January 2005 07:43, Mike Chandler wrote:
On Wednesday 05 January 2005 06:24 pm, John A Chaves wrote:
On Wednesday 05 January 2005 07:45 pm, [EMAIL PROTECTED] wrote:
I just now checked and I don't have the file
would a dpkg-reconifigure xserver-xfree86 have fixed this??
C
No. That was the first idea I tried. If I didn't have access to this mailing
list, my system would be useless. Thanks!
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Hi there,
I had the same problem, kdm took my keyboard from me. I fixed it by
copying the kdmrc.dpkg-dist over the exisiting kdmrc, which I have
chosen to keep during install (which wass the cause of the problem;).
Thanks to the guys at #debian and #debian-kde who pointed me there!
Cheers,
On Thursday 06 January 2005 09:06 am, Peter B. Schmidt wrote:
Hi there,
I had the same problem, kdm took my keyboard from me. I fixed it by
copying the kdmrc.dpkg-dist over the exisiting kdmrc, which I have
chosen to keep during install (which wass the cause of the problem;).
Thanks to the
On Wednesday 05 January 2005 01:12 am, [EMAIL PROTECTED] wrote:
Sorry if this has been covered, search function gets no result...
I have been running sarge flawlessly since May 2004, doing regular apt-get
dist-upgrades.
Today, dist-upgrade included over 100 MBs of mostly KDE stuff, and
John A Chaves said:
I had the same problem. Don't know which Xserver options
cause the problem, but restoring /etc/kde3/kdm/Xservers
from /etc/kde3/kdm/Xservers.dpkg-old solved it for me.
...file as bug...
--
--Luke CS Sysadmin, Montana State University-Bozeman
--
To UNSUBSCRIBE, email
- Original Message -
From: John A Chaves [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Tuesday, January 04, 2005 11:44 PM
Subject: Re: sarge dist-upgrade today, no more keyboard
On Wednesday 05 January 2005 01:12 am, [EMAIL PROTECTED] wrote:
Sorry if this has been covered
Hello, all.
I hope that you can help me.
While upgrading My Sarge machine this morning, I have got problems with a
conflict during the process.
apt-get complains that:
/usr/lib/kde3/gsthumbnail.la already exists in kdebase-kio-plugins when trying
to unpack kdegraphics-kfile-plugins
As usual
- Original Message -
From: John A Chaves [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Tuesday, January 04, 2005 11:44 PM
Subject: Re: sarge dist-upgrade today, no more keyboard
On Wednesday 05 January 2005 01:12 am, [EMAIL PROTECTED] wrote:
Sorry if this has been covered
On Wednesday 05 January 2005 07:45 pm, [EMAIL PROTECTED] wrote:
I just now checked and I don't have the file Xservers.dpkg-old in that
directory.
Are you sure that's where it is? I don't have any way to search for it
without a keyboard.
I think that you only get the .dpkg-old file if you
On Wednesday 05 January 2005 06:24 pm, John A Chaves wrote:
On Wednesday 05 January 2005 07:45 pm, [EMAIL PROTECTED] wrote:
I just now checked and I don't have the file Xservers.dpkg-old in that
directory.
Are you sure that's where it is? I don't have any way to search for it
without a
Sorry if this has been covered, search function
gets no result...
I have been running sarge flawlessly since May
2004, doing regular apt-get dist-upgrades.
Today, dist-upgrade included over 100 MBs of mostly
KDE stuff, and others... anyway it finished without errors, when I rebooted, the
From Carlos Sousa on Monday, 2004-09-06 at 22:38:14 +0100:
On Mon, 6 Sep 2004 23:18:25 +0200 Conrad Newton wrote:
[...]
It is not an answer to your question, and maybe it is not even
relevant to your problem, but I am having similar problems
here with tetex-base. When I try to correct the
On Mon, 6 Sep 2004 14:32:09 -0500
Will Trillich [EMAIL PROTECTED] wrote:
post deleted
No answer to your question
I'm running Sarge
I just ran
aptitude update aptitude upgrade, which ran fine, but ran (for
giggles) aptitude -f install.
Why in the galaxy would these files be
From Carlos Sousa on Monday, 2004-09-06 at 22:38:14 +0100:
On Mon, 6 Sep 2004 23:18:25 +0200 Conrad Newton wrote:
[...]
It is not an answer to your question, and maybe it is not even
relevant to your problem, but I am having similar problems
here with tetex-base. When I try to correct the
f.y.i.
in trying an upgrade (dist-upgrade) from woody to sarge, we ran
into trouble with the following sympoms:
[EMAIL PROTECTED] apt-get -f install postgresql
Reading Package Lists... Done
Building Dependency Tree... Done
You might want to run `apt-get -f install' to correct these:
The
From Will Trillich on Monday, 2004-09-06 at 14:32:09 -0500:
f.y.i.
in trying an upgrade (dist-upgrade) from woody to sarge, we ran
into trouble with the following sympoms:
[EMAIL PROTECTED] apt-get -f install postgresql
(snip)
dpkg: error processing postgresql (--remove):
Package is
On Mon, 6 Sep 2004 23:18:25 +0200 Conrad Newton wrote:
[...]
It is not an answer to your question, and maybe it is not even
relevant to your problem, but I am having similar problems
here with tetex-base. When I try to correct the problem,
I get a system crash or even trigger a reboot.
The
Greetings Debian Gurus,
Well, I've learned a lot this week
about how Debian works in the real
world. Up to now I've just been
having a blissful run of beginner's
luck, it seems. The past five days
have seen me chasing down supposed
hardware incompatibilities, sifting
through partial,
Incoming from Jerry Spicklemire:
Is there any way to back up in time to
a state where sarge is complete, and
therefore upgradable, even if it is
in a less than ideal state? I can always
I'd suggest you backup /etc and $HOME and re-install, using
woody/stable sources.list. Then if you
Jerry Spicklemire wrote:
The following packages have unmet dependencies:
e2fsprogs: PreDepends: libblkid1 (= 1.34-1) but it
is not installable
PreDepends: libss2 (= 1.34-1) but it is
not installable
PreDepends: libuuid1 (= 1.34-1) but it
is not installable
coreutils:
Hi!
I'm tracking Sarge now, and for the past couple of days, when I tried
dist-upgrade, it has wanted to remove pretty much every KDE package on
my system...
Like:
[EMAIL PROTECTED]:/home/kjetil apt-get -s dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating
On Thu, Feb 12, 2004 at 05:20:30PM +0100, Kjetil Kjernsmo wrote:
I'm tracking Sarge now, and for the past couple of days, when I tried
dist-upgrade, it has wanted to remove pretty much every KDE package on
my system...
KDE's not yet completely working in sarge, so I can't say I'm surprised.
On Thursday 12 February 2004 11:20 am, Kjetil Kjernsmo wrote:
I'm tracking Sarge now, and for the past couple of days, when I tried
dist-upgrade, it has wanted to remove pretty much every KDE package on
my system...
KDE is currently broken in Sarge. The 3.1.5 packages coming from Sid
should
On Thursday 12 February 2004 18:09, Adam Aube wrote:
On Thursday 12 February 2004 11:20 am, Kjetil Kjernsmo wrote:
I'm tracking Sarge now, and for the past couple of days, when I
tried dist-upgrade, it has wanted to remove pretty much every KDE
package on my system...
KDE is currently
Kjetil Kjernsmo kjetil at kjernsmo.net writes:
I'm tracking Sarge now, and for the past couple of days, when I tried
dist-upgrade, it has wanted to remove pretty much every KDE package on
my system...
Make sure to check the DebianKDE Wiki page as well:
On Thu, Feb 12, 2004 at 05:20:30PM +0100, Kjetil Kjernsmo wrote:
I'm tracking Sarge now, and for the past couple of days, when I tried
dist-upgrade, it has wanted to remove pretty much every KDE package on
my system...
When I upgraded from stable to Sarge about 3-4 months ago, it removed
Hi all,
I did a dist-upgrade yesterday with sarge, and had a problem. If I use
apt-get -f install , I get the following error:
Removing pxfonts ...
chmod: failed to get attributes of `/etc/texmf/dvips/updmap': No such
file or directory
dpkg: error processing pxfonts (--remove):
subprocess
Hello Glen,
Glen Snyder wrote:
I did a dist-upgrade yesterday with sarge, and had a problem. If I use
apt-get -f install , I get the following error:
Sorry, but what do you want to install?
Removing pxfonts ...
chmod: failed to get attributes of `/etc/texmf/dvips/updmap': No such
file or
73 matches
Mail list logo
