On Mon, Jul 10, 2000 at 18:50, [EMAIL PROTECTED] wrote:
Hi!
I recently upgraded my slink box to potato with apt. Everything works
well but the new ssh:
neptun:/home/papt# dpkg --configure ssh
Setting up ssh (1.2.3-5) ...
^
I think this was fixed around -7, and I
Adrian Thiele wrote:
Peter Allen wrote:
(everything looked fine on boot), I then tried to login:
When I try I can type my username, it waits three seconds and
asks for my username again. (No password asked for and no login)
When you ran the config after the install did you keep your PAM
Timothy C. Phan wrote:
Hi,
I'm a user who are way behind the debian upgrade. I've
recently mirror the slink and plan to upgrade from my
debian 1.3.1 to slink. However, I've just noticed the potato
was recently frozen. I'd like to solicite you all comment
on whether I should
Hi All,
It seems to me that potato would support the latest jdk1.2.2
better than slink and I'm also need the use of jdk1.2.2 as
well.
In this case, I'll go for potato from hamm. Well, I just need
to know one more thing, does potato support IPMASQ the same as the
previous versions
On Sat, Jan 15, 2000 at 01:01:51PM -0800, Michael Perry wrote:
Hi all-
I just got dsl here so have a system I would like to take from slink to
potato using the apt-get install dist-upgrade. Has anyone done this
recently? Any issues?
I did the upgrade last friday on my laptop. no real
On Sat, Jan 15, 2000 at 01:56:51PM -0800, Michael Perry wrote:
I just got dsl here so have a system I would like to take from slink to
potato using the apt-get install dist-upgrade. Has anyone done this
recently? Any issues? Also would just like to say thanks to everyone that
develops for
Hi,
On Thu, Nov 11, 1999 at 11:04:11PM -0600, David J. Kanter was heard to state:
I have Slink, but have spent some time over the last few days updating
essentially all the required base and standard packages from Potato. So,
when I look at packages for Slink or for Potato, which one am I
On Thu, 11 Nov 1999, Randy M.Kaplan wrote:
rkapla Can someone provide a definition of slink? of potato?
slink = debian v2.1
potato = debian 2.2
is that what u wanted ??
nate
[mailto:[EMAIL PROTECTED] ]--
Vice President Network Operations
*- On 11 Nov, Randy M.Kaplan wrote about slink and potato
Can someone provide a definition of slink? of potato?
Slink is the current stable version of Debian 2.1r3. The code name
slink comes from the Slinky character in the movie Toy Story.
Potato is the current unstable version of Debian
slink: to move in a quiet, furtive manner; to sneak
potato: a plant, emSolarnum Tuberosum/em, native to South America
and widely cultivated for its starchy, edible tubers.
Randy M.Kaplan wrote:
Can someone provide a definition of slink? of potato?
Thanks,
Randy Kaplan
--
On Mon, 18 Oct 1999, Dave Baker wrote:
On Sun, 17 Oct 1999, Todd Suess wrote:
I was brave, I just did apt-get dist-upgrade and waiting about 10 hours
for it to download everything and upgrade. Have had very little trouble
with it.
-Todd
ps. for this to work, you of course
I was brave, I just did apt-get dist-upgrade and waiting about 10 hours
for it to download everything and upgrade. Have had very little trouble
with it.
-Todd
ps. for this to work, you of course have to have apt installed and
a entry in sources.list pointing to an unstable archive.
At
Slink is the current stable debian release version, which is 2.1
Potato is the current unstable release version, which is due
to be released before the end of the year, god willing. :)
Often you will see Slink = Stable, Potato = Unstable, but
I have been using potato for a while now will
Those are directory aliases, they go to the same place.
If you cd to slink you will get to stable
if you cd to potato you will get to unstable.
regards,
Todd
Then how come at ftp.debian.org there's a directory named slink and also
a directory named stable, and a directory named potato and
On Sun, Oct 17, 1999 at 10:00:51PM -0500, Ben Wong wrote:
Then how come at ftp.debian.org there's a directory named slink and also
a directory named stable, and a directory named potato and also a
directory
named unstable?
Ever heard of a symlink?
unstable - potato
stable - slink
I know
On Sun, 17 Oct 1999, Ben Wong wrote:
snip
I have been using potato for a while now will little or no problems,
and it works a lot better in many ways, at least for me.
snip
what is better about potato? ( i'm still new to debian ; so just wondering
if i should go slink - potato )
thanks you
On Mon, Oct 18, 1999 at 02:17:27PM +, RAVIKANT K RAO wrote:
what is better about potato? ( i'm still new to debian ; so just wondering
if i should go slink - potato )
Potato is newer stuff. The trade-off is that it is less stable -
hasn't been tested as thoroughly. Potato is almost ready
On Sun, 17 Oct 1999, Todd Suess wrote:
I was brave, I just did apt-get dist-upgrade and waiting about 10 hours
for it to download everything and upgrade. Have had very little trouble
with it.
-Todd
ps. for this to work, you of course have to have apt installed and
a entry in
On Sun, 17 Oct 1999, Ben Wong wrote:
: Slink is the current stable debian release version, which is 2.1
: Potato is the current unstable release version, which is due
: to be released before the end of the year, god willing. :)
:
: Often you will see Slink = Stable, Potato = Unstable,
On Sun, Oct 17, 1999 at 10:00:51PM -0500, Ben Wong wrote:
Then how come at ftp.debian.org there's a directory named slink and also
a directory named stable, and a directory named potato and also a
directory
named unstable?
They're aliases. stable always points to the current stable
Slink is the current stable debian release version, which is 2.1
Potato is the current unstable release version, which is due
to be released before the end of the year, god willing. :)
Often you will see Slink = Stable, Potato = Unstable, but
I have been using potato for a while now will little
Often you will see Slink = Stable, Potato = Unstable, but
I have been using potato for a while now will little or no problems,
and it works a lot better in many ways, at least for me.
I am running slink but I want to upgrade to potato. How do I go about?
What is the best way?
-gnana
Damon Muller ([EMAIL PROTECTED]) wrote:
If I want to
check out something that is only in Potato, I go and use apt-get to grab
and install it. If it uses glibc2.1, it'll get that, and any other libs
that it depends on.
Yup.
Being `binary compatible', does this mean that all the apps that I
Hi Greg Wooledge; unless Mutt is confused, you wrote:
Damon Muller ([EMAIL PROTECTED]) wrote:
If I want to
check out something that is only in Potato, I go and use apt-get to grab
and install it. If it uses glibc2.1, it'll get that, and any other libs
that it depends on.
Yup.
Damon Muller [EMAIL PROTECTED] writes:
Because of the developments such as glibc2.1, perl, and probably
numerous other things, you can't take something out of Potato and put it
on a Slink system and expect it to work. It's an all-or-nothing
arrangement. They may both be `GNU/Linux', but they
Hi Miles Bader; unless Mutt is confused, you wrote:
Damon Muller [EMAIL PROTECTED] writes:
Because of the developments such as glibc2.1, perl, and probably
numerous other things, you can't take something out of Potato and put it
on a Slink system and expect it to work. It's an
Damir J. Naden [EMAIL PROTECTED] writes:
I have been told that glibc2.1 and glibc2.0 are binary compatible.
For most purposes, they are. Of course this is software, and software
has bugs, so there are almost certainly odd cases where things don't
work; but they appear to be quite the exception.
That was supposed to be the point of my message -- In my experience,
upgrading from glibc 2.0 to 2.1 is *trivial*, and needs no special
consideration, migration guides, hand-holding sessions, or support
groups.
Stop whining and just do it.
-Miles
p.s. The `stop whining' bit was for
-BEGIN PGP SIGNED MESSAGE-
On Tue, 5 Oct 1999, Damir J. Naden wrote:
I have been in this thread way too long :-), but ... I have to agree
with Damon's post. And I have been told that glibc2.1 and glibc2.0 are
binary compatible.
Glibc 2.1 is binary compatible with glibc 2.0. That
On Mon, Oct 04, 1999 at 03:38:05AM +0100, Mark Brown was heard to state:
The stable GNOME packages are actually produced by the Debian
maintainers - they're just distributed from the GNOME site.
So, why would they not be introduced into slink-proposed-updates?
The only things in
[EMAIL PROTECTED] writes:
I've been slowly upgrading my packages from slink to potato, and
frankly, have never had a single problem.
How are you doing this? Do you just go get the packages and 'dpkg -i' them
or do you use apt? There are a bunch of things I want to upgrade on my
system
Brad [EMAIL PROTECTED] writes:
There's a howto somewhere on the Debian site saying which packages have to
be updated to use a 2.2 kernel with Slink.
Do you have any idea where this would be? I've been searching the
debian site for this kind of info with no luck. I did try a 2.2.10
kernel, and
Hi Miles Bader; unless Mutt is confused, you wrote:
Brad [EMAIL PROTECTED] writes:
There's a howto somewhere on the Debian site saying which packages have to
be updated to use a 2.2 kernel with Slink.
Do you have any idea where this would be? I've been searching the
debian site for this
Hi Mark Brown; unless Mutt is confused, you wrote:
Damir, are you sure mutt is using vim? If you have nvi installed and
haven't adjusted the alternatives vi will default to that and if you
normally use a shell alias to select your vi mutt won't pick that up.
Yup, I'm positive. I am a control
Hi Brad; unless Mutt is confused, you wrote:
Hmmm... exactly 80-column lines, more or less. 72 or 76 is much better
though, it leaves room for replies.
Ooops, sorry, I don't know how that happened; my vimrc files specs 76 columns,
maybe I need separate command in muttrc?
I'm not sure what
-BEGIN PGP SIGNED MESSAGE-
On Sat, 2 Oct 1999, Damir J. Naden wrote:
Hi Brad; unless Mutt is confused, you wrote:
Hmmm... exactly 80-column lines, more or less. 72 or 76 is much better
though, it leaves room for replies.
Ooops, sorry, I don't know how that happened; my vimrc
On Sun, Oct 03, 1999 at 01:55:22AM -0500, Brad wrote:
On Sat, 2 Oct 1999, Damir J. Naden wrote:
Hi Brad; unless Mutt is confused, you wrote:
Hmmm... exactly 80-column lines, more or less. 72 or 76 is much better
though, it leaves room for replies.
Ooops, sorry, I don't know how that
Based on some advice in this thread, I decided to try upgrading a few
non-critical packages to see how it would go. After getting a few things
upgraded without a hitch, I decided to give samba a try. It broke.
After downgrading samba (also easy) so it would keep working, I looked
for the problem
-BEGIN PGP SIGNED MESSAGE-
Hmmm... exactly 80-column lines, more or less. 72 or 76 is much better
though, it leaves room for replies.
On Fri, 1 Oct 1999, Damir J. Naden wrote:
Hi Brad; unless Mutt is confused, you wrote:
---stuff snipped here--
Depending on the particular
-BEGIN PGP SIGNED MESSAGE-
On Fri, 1 Oct 1999 [EMAIL PROTECTED] wrote:
My real question is: To upgrade from slink to potato, should I go to a
2.2 kernel under slink first? I know those issues are documented on
the Debian site. If so, what kernel version is most likely to prevent
As for the version, i'd go with the latest stable (2.2.12, unless they
released 2.2.13 just today). There's even a brand new Debian package so
you won't have to compile your own if you don't want.
Where would I be able to find that package?
--
Bart Szyszka [EMAIL PROTECTED] ICQ:4982727
B
-BEGIN PGP SIGNED MESSAGE-
On Sat, 2 Oct 1999, B. Szyszka wrote:
As for the version, i'd go with the latest stable (2.2.12, unless they
released 2.2.13 just today). There's even a brand new Debian package so
you won't have to compile your own if you don't want.
Where would I be
On Fri, Oct 01, 1999 at 09:17:07AM -0700, [EMAIL PROTECTED] wrote:
Wouldn't it be nice is this information was collated at one location so
that people could build on what's already been done and not have to try
everything new every time. That's what open source is about--sharing.
What I am
[EMAIL PROTECTED] writes:
When I talked with some Debian folks at Linux World, they indicated
that Potato was fairly stable and that I could safely upgrade a Slink
installation to Potato without problems. However, when looking at the
mailing list archives, it seems that it isn't so. For one,
I've been slowly upgrading my packages from slink to potato, and
frankly, have never had a single problem. I was nervous about upgrading
perl, because I've seen all sorts of veiled references to possible
hosage (although I've never seen a concise statement of the actual
problem), but
On Fri, Oct 01, 1999 at 03:52:47PM +0900, Miles Bader wrote:
I've been slowly upgrading my packages from slink to potato, and
frankly, have never had a single problem. I was nervous about upgrading
perl, because I've seen all sorts of veiled references to possible
hosage (although I've never
On Fri, Oct 01, 1999 at 12:54:24AM -0700, [EMAIL PROTECTED] wrote:
This is what I've heard, but not what I see in the mailing list archive
where people ask about problems with Potato and they are answered only
That's what unstable means. In other words, you're on your own, pal.
Well, it's a
In linux.debian.user, [EMAIL PROTECTED]
Some people just don't have the luxury of working with Unstable. However, much
of the software released, like Gnome, GIMP, LyX and such *is* stable.
Enlightenment 0.15.x is quite stable, albeit incomplete. It is no less stable
than the 0.14.6 that ships on
On Fri, Oct 01, 1999 at 08:17:41AM -0600, [EMAIL PROTECTED] wrote:
On Fri, Oct 01, 1999 at 03:52:47PM +0900, Miles Bader wrote:
I've been slowly upgrading my packages from slink to potato, and
frankly, have never had a single problem. I was nervous about upgrading
perl, because I've seen
Well, it's a bit better than that - particularly if you keep up with the
various lists (mostly -user and -devel) you should be all right. It's
more a case of pay attention and be prepared to fix things if they
break than anything else. I'd guess that a fair proportion of
developers are
When I asked a similar question a long time ago (but still when slink
was stable!) it was explained to me thusly: if you start modifying
stable, then you might break it. That means that if one permitted
regular modifications/upgrades to stable packages, one would have to
go through the
On Fri, Oct 01, 1999 at 08:17:41AM -0600, [EMAIL PROTECTED] wrote:
How are you doing this? Do you just go get the packages and 'dpkg -i' them
or do you use apt? There are a bunch of things I want to upgrade on my
system but I assumed that all of the potato packages would have dependencie
On Fri, Oct 01, 1999 at 09:58:59AM -0700, [EMAIL PROTECTED] wrote:
Rob,
I'm no apt expert. Would you write up a section on Apt for a Debian
Update HowTo? I will voluteer to edit and put it together as well
as providing content. If need be, I will even host it on my server.
The HowTo
[EMAIL PROTECTED] wrote:
I will, however, write up a Debian Update HowTo which
lists those Unstable modules which people have ported to Slink so that
every other person who wants to do this doesn't have to go through the
agony of researching everything anew.
I know of no
http://www.internatif.org/bortzmeyer/debian/apt-sources/
This is the type of information that should be linked to on the Debian host
site. One should not have to come to the Mailing Lists to find this. The
logical place to put this is with the Gnome Slink update link.
I can see that much of
[EMAIL PROTECTED] wrote:
http://www.internatif.org/bortzmeyer/debian/apt-sources/
This is the type of information that should be linked to on the Debian host
site.
Unfortunately, the Debian web page is pretty static except for
the dynamically generated package indices. Nothing much
-BEGIN PGP SIGNED MESSAGE-
On Thu, 30 Sep 1999 [EMAIL PROTECTED] wrote:
When I talked with some Debian folks at Linux World, they indicated
that Potato was fairly stable and that I could safely upgrade a Slink
installation to Potato without problems. However, when looking at the
On Thu, 22 Apr 1999, Christian Dysthe wrote:
Hi,
Hi
updated to potato. Looks like everything went fine except for these two errors
I get when I boot:
1. [mntent]: no final newline at the end of /etc/fstab
Put in a newline at the end of /etc/fstab?
2. Modprobe can't find netpf19
This
On Thu, 22 Apr 1999, Christian Dysthe wrote:
Hi,
updated to potato. Looks like everything went fine except for these two errors
I get when I boot:
1. [mntent]: no final newline at the end of /etc/fstab
edit your fstab and add a blank line on the end
2. Modprobe can't find netpf19
59 matches
Mail list logo
