I'm venting a little here ... sorry :)
I've been at work since 9 pm Saturday night - it is now 7 am Sunday.
Why? Well, we run BSDI here and I'm upgrading from 2.1 to 3.0 ... and
compared to upgrading Debian 1.2 to 1.3, it sucks. To all the kind
folks who've spent many long nights making Debian L
> compared to upgrading Debian 1.2 to 1.3, it sucks. To all the kind
> folks who've spent many long nights making Debian Linux a quality
> product, thank you.
I have to agree. After switching to Linux I'm constantly impressed
with everything about Debian (I ran SLS and then Slackware before).
>And, speaking of that, can I ask a stupid question? Okay.
> What/where/when is Debian 1.3 going to be released? I'm using 1.2,
> getting upgrades through the net with dselect in its default setup
> pointing at debian.org and the stable, non-free, and contrib
> subdirectories.
>
>I read
Randy Edwards <[EMAIL PROTECTED]> writes:
>And, speaking of that, can I ask a stupid question? Okay.
> What/where/when is Debian 1.3 going to be released? I'm using 1.2,
> getting upgrades through the net with dselect in its default setup
> pointing at debian.org and the stable, non-free, an
On Sun, 1 Jun 1997, Nathan E Norman wrote:
>
> BTW, while I was waiting for the BSDI upgrade, I upgraded my secondary
> DNS server (a Debian box). It took about an hour :) I'm still working
> on BSDI ...
You get what you pay for :-)
Bob
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the wo
On Sun, 1 Jun 1997, Randy Edwards wrote:
> > compared to upgrading Debian 1.2 to 1.3, it sucks. To all the kind
> > folks who've spent many long nights making Debian Linux a quality
> > product, thank you.
>
>I have to agree. After switching to Linux I'm constantly impressed
> with everythi
Bob Nielsen <[EMAIL PROTECTED]> writes:
>
> Just replace stable with frozen in dselect and things should work fine. I
Hm... I've found (so far...) on rather important flaw. Perhaps I'm
missing it, but it appears that xlockmore doesn't know about shadow
passwords?
--sf
--
TO UNSUBSCRIBE F
>
> BTW, while I was waiting for the BSDI upgrade, I upgraded my secondary
> DNS server (a Debian box). It took about an hour :) I'm still working
> on BSDI ...
If Software in the Public Interest charged big bucks for Debian support,
Debian might be a bear to install too ;)
It is probably jus
> Just replace stable with frozen in dselect and things should work fine. I
> upgraded by ftp over a ppp link (~39 MB) and it went as slick as can be
> (it took a few hours of course.)
>
> After struggling with two Red Hat upgrades and getting a system which
> worked but could only be upgraded
-BEGIN PGP SIGNED MESSAGE-
On Sun, 1 Jun 1997, Randy Edwards wrote:
> > compared to upgrading Debian 1.2 to 1.3, it sucks. To all the kind
> > folks who've spent many long nights making Debian Linux a quality
> > product, thank you.
>
>I have to agree. After switching to Linux I'm
On Jun 1, Randy Edwards wrote
>
>I read a fragment of one message somewhere that 1.3 is actually in the
> frozen subdirectory; is that true? If I were to make my dselect point at
> stable, non-free, contrib, and frozen would that cause the upgrade? Or
> should I wait until it's moved from fr
On Jun 1, stephen farrell wrote
>
> Hm... I've found (so far...) on rather important flaw. Perhaps I'm
> missing it, but it appears that xlockmore doesn't know about shadow
> passwords?
Are you sure you're running the latest version from frozen? (i.e. 4.02-1)
It's got not problem with my shado
>
>--n2rw/3z4jIqBvZU5
>Content-Type: text/plain; charset=us-ascii
>
>On Jun 1, stephen farrell wrote
>>
>> Hm... I've found (so far...) on rather important flaw. Perhaps I'm
>> missing it, but it appears that xlockmore doesn't know about shadow
>> passwords?
>
>Are you sure you're running the
On Jun 1, stephen farrell wrote
>
> Perhaps I didn't set up shadow stuff correctly? I kind of stumbled
> upon it: I noticed references to it, and I typed pwconv (which I
> recognized from my solaris systems) and things seemed to work pretty
> happily (except xlock), so I figured that this was it.
On Sun, 1 Jun 1997, Jim Pick wrote:
> Just set dselect to point at: frozen non-free contrib
Wait!! Hold this upgrade!! Hehe sorry all but i was about to try
the upgrade tomorrow but i was going to use bo. What am i suppossed to
use Bo or Frozen???
Also i am going to setup a mirro
>
> Wait!! Hold this upgrade!! Hehe sorry all but i was about to try
> the upgrade tomorrow but i was going to use bo. What am i suppossed to
> use Bo or Frozen???
frozen is actually a symlink currently pointing to bo/
In a couple of days a symlynk "stable" will point to the same directory
On Mon, 2 Jun 1997, System Account (what a cute name!:) wrote:
> Wait!! Hold this upgrade!! Hehe sorry all but i was about to try
> the upgrade tomorrow but i was going to use bo. What am i suppossed to
> use Bo or Frozen???
Frozen, I think. BTW I always use unstable for this purpose.
>
> > To all the kind folks
> > who've spent many long nights making Debian Linux a quality
> > product, thank you.
I *must* agree. A year ago, I gave up trying to get a SCO Unix box
(3.2v4.2) running all the Internet services I wanted. Every single service
I wanted to get running was a complete P
> I'm extremely happy with the way Debian 1.3, it's a huge improvement
> over 1.2. I'm sure you'll like it too. :-)
Is there a list of "improvements" / changes between 1.2.x and 1.3
available?
Later,
Kevin Traas
Systems Analyst
Edmondson Roper CA
http://www.eroper.bc.ca
--
TO UNSUBSCRIBE FRO
> > I'm extremely happy with the way Debian 1.3, it's a huge improvement
> > over 1.2. I'm sure you'll like it too. :-)
>
> Is there a list of "improvements" / changes between 1.2.x and 1.3
> available?
I'm not really aware of a list. Each package gets updated on an individual
basis, so you c
20 matches
Mail list logo
