I just upgraded my computer from a 486 to a petiumIII450.
I moved the old disk to the new computer in order to move the linux
instelation. Linux came up mostly fine exept for two magor problems:
The mouse doesn't respond under X. I tried most protocolst that looked
remotly apropriate.
The mouse is
On Thu, 25 Nov 1999, Micha Feigin wrote:
I just upgraded my computer from a 486 to a petiumIII450.
I moved the old disk to the new computer in order to move the linux
instelation. Linux came up mostly fine exept for two magor problems:
The mouse doesn't respond under X. I tried most
If it's a ps2 mouse (smallish, round connector) use /dev/psaux.
--
++
| Eric G. Milleregm2@jps.net |
| GnuPG public key: http://www.jps.net/egm2/gpg.asc |
++
I too gave /var 30MB when installing Debian for the 1st time.
I think it is worth mentioning because I took this figure from the Debian-FAQ.
I think it should be changed before potato is released. In view of today disk
sizes I would change it to 100MB.
Some other changes I would do for the
When attempting to upgrade, in pieces, from Slink to Potato, I got this
error message when typing apt-get dist-upgrade:
E: Sorry, you don't have enough free space in /var/cache/apt/archives/
Do I have too small a partition, is that the problem? What can I do to fix
this?
Thanks.
--
David J.
David J Kanter [EMAIL PROTECTED] writes:
DJK When attempting to upgrade, in pieces, from Slink to Potato, I
DJK got this error message when typing apt-get dist-upgrade:
DJK
DJK E: Sorry, you don't have enough free space in /var/cache/apt/archives/
DJK
DJK Do I have too small a partition, is that
Hi, all. I am a more or less experienced debian user, and I want to share this
with you;
I went through a few minor problems, when I recently decided that I had
scr*wed up my
system(Potato) and it was time for a reinstall.
I reinstalled from a set of Slink CDs, and proceeded to do an apt-get
Even easier work around:
$ apt-get upgrade libreadline
$ apt-get upgrade bash
Get the readline first.
--
Eric G. Miller
Powered by the POTATO (http://www.debian.org)!
Hello!
I have upgraded from slink to potato.
But something happend. I could not start X
after the upgrade. So I decided to config
XF86Config again. When I type XF86Setup I have
got following error : _X11TransSocketUNIXConnect-
Can't connect : errno = 111. So I tried xf86config
but when I type
...
-Original Message-
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]
Sent: Friday, April 30, 1999 8:16 AM
To: debian-user@lists.debian.org
Subject: upgrade problem
Hello!
I have upgraded from slink to potato.
But something happend. I could not start X
after the upgrade. So I
On Fri, 30 Apr 1999, [EMAIL PROTECTED] wrote:
Hello!
I have upgraded from slink to potato.
But something happend. I could not start X
after the upgrade. So I decided to config
XF86Config again. When I type XF86Setup I have
got following error : _X11TransSocketUNIXConnect-
Can't connect :
After upgrading to HAM from BO, I have not been able to get the LaTeX
key-bindings to work or even have the LaTeX menu items appear in emacs.
I've tried emacs19, emacs20-nomule and xemacs but to no avail. Has
anyone else run into this problem and if so, how did you solve it.
Thanks in advance!
Hello,
I hve some trouble upgrading from 1.3.1 to 2.0. I used the autoup.sh
script from www.debian.org and downloaded the required files
from ftp.debian.org this weekend.
All went well until the new bash took it's turn:
(Reading database ... 27298 files and directories currently installed.)
Just upgraded, got this:
Setting up mh (6.8.4-20) ...
chmod: /usr/lib/mh/spopfi: No such file or directory
dpkg: error processing mh (--install):
subprocess post-installation script returned error exit status 1
??
TIA for any help :)
Matt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Hi,
Thanks to the help of the fine folks in this mailing list, I was able to
upgrade to hamm reasonably easily. I am still poking around my system
to find out problems with the upgrade.
After the upgrade, I am unable to log into my machine with a username in
YP.
$ cat /etc/passwd
...some
On Tue, Jan 13, 1998 at 09:26:27PM -0800, Sudhakar Chandrasekharan wrote:
After the upgrade, I am unable to log into my machine with a username in
YP.
$ cat /etc/passwd
...some stuff...
+::0:0:::
OK
$ cat /etc/nsswitch.conf
passwd: db files
group: db files
shadow:
Nils Rennebarth wrote:
On Tue, Jan 13, 1998 at 09:26:27PM -0800, Sudhakar Chandrasekharan wrote:
After the upgrade, I am unable to log into my machine with a username in
YP.
$ cat /etc/nsswitch.conf
passwd: db files
group: db files
shadow: db files
For these
On Wed, 14 Jan 1998, Sudhakar Chandrasekharan wrote:
Also, I am in Panic Mode now.
* If I am unable to log in as root, how do I fix what I did to
nsswitch.conf? I was sensible enough to backup the old file before
making the changes. I am unable to locate my emergency disk (or
whatever
On Wed, Jan 14, 1998 at 09:18:55AM -0800, Sudhakar Chandrasekharan wrote:
Nils Rennebarth wrote:
passwd: db files
group: db files
shadow: db files
For these three replace db files with compat and you should be done.
How should it read? The HOWTO mentions this
In article [EMAIL PROTECTED],
Nils Rennebarth [EMAIL PROTECTED] wrote:
As for documentation try the command
info libc
then look at the section
* Name Service Switch
Well you could also just read the /usr/doc/nis/nis.debian.howto.gz
file which explains everything in detail.
Mike.
--
Nils Rennebarth wrote:
I tried to be clear but... anyway, my /etc/nsswitch.conf looks like this:
#---cut here to damage your monitor--
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
#
passwd: compat
[EMAIL PROTECTED] (Kevin J Poorman) writes:
I have fairly easily upgraded to hamm However I have had some uh ...
Kinks.
Heres the latest ...
I upgrades the ncurses packages to :
ncurses3.0
ncurses3.4
which seem to live together nicely from a debian perspective however when
I got
Hi,
I have fairly easily upgraded to hamm However I have had some uh ...
Kinks.
Heres the latest ...
I upgrades the ncurses packages to :
ncurses3.0
ncurses3.4
which seem to live together nicely from a debian perspective however when
I got the new Kernel source from ftp.kernel.org and untar'd
Another way to solve that blinking problem is to boot up from floppy,
and edit /edc/X11/config to remove the xdm start line. Or login from
another machine, if it has a network connection.
rick
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Thanks W Paul and other people responded my e-mail. After loading
ip_masq_ftp.o module to my gateway machine, ftp from the server
woked fine. That was exactly my problem of not loading the module
during boot time. Thanks again. Jimmy
On Tue, 9 Sep 1997, W Paul Mills wrote:
On Mon, 8 Sep
On Mon, 8 Sep 1997, Jimmy Lu wrote:
I have a similar problem on one of mey machine. I have two Linux
machines networked. The strange thing is that my gateway machine
works fine but not for the other one. When I try to ftp from that
machine, I can log to the ftp site but when I do ls, it
I have a similar problem on one of mey machine. I have two Linux
machines networked. The strange thing is that my gateway machine
works fine but not for the other one. When I try to ftp from that
machine, I can log to the ftp site but when I do ls, it just waits
forever.
I have a problem using the ftp upgrade method for 1.2 to 1.3. I have
manually retrieved the new software refered to in the ftp information. I
use the default options. I can connect manually to ftp.debian.org, but
when dselect tried to do it I get:
Using FTP to check directories...(stop with
In article [EMAIL PROTECTED],
James D. Freels [EMAIL PROTECTED] wrote:
In upgrading machine #2 (see earlier post on problems with machine #1)
from debian 1.1 to 1.2, and rebooting. I got an error on reboot
something about unable to initialize console and the machine hung.
I thought it may have
On Mon, 30 Dec 1996, James D. Freels wrote:
In upgrading machine #2 (see earlier post on problems with machine #1)
from debian 1.1 to 1.2, and rebooting. I got an error on reboot
something about unable to initialize console and the machine hung.
I thought it may have been a problem with my
In upgrading machine #2 (see earlier post on problems with machine #1)
from debian 1.1 to 1.2, and rebooting. I got an error on reboot
something about unable to initialize console and the machine hung.
I thought it may have been a problem with my upgrade.
Later I decided to wipe out the drive,
Dear Debian-Linux colleagues:
A few days ago, I had mentioned in this newsgroup a problem I was
having with using my commercial license of NAG Fortran on the new
Debian 1.1 upgrade. I wish to report here the fix to the problem.
As one might expect, the problem is due to Debian 1.1 being an
601 - 632 of 632 matches
Mail list logo
