On Tue, Oct 17, 2006 at 11:42:00AM -0400, [EMAIL PROTECTED] wrote:
> On Mon, Oct 16, 2006 at 03:14:32PM -0500, cothrige wrote:
> > * [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> > >
> > > If you want a little more control over the details, with a usable
> > > text-based user interface, use 'apt
On Mon, Oct 16, 2006 at 03:14:32PM -0500, cothrige wrote:
> * [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> >
> > If you want a little more control over the details, with a usable
> > text-based user interface, use 'aptitude'.
> > after it's started in a text console (very useful if your X is br
cothrige <[EMAIL PROTECTED]>:
> In reading online it seems that the standard practice to apply
> security patches would be to run 'apt-get update' and then 'apt-get
> upgrade'. I am curious if this really is the best way and if so, how
> often should it be done?
i. Install apt-listbugs
On Mon, Oct 16, 2006 at 03:28:36PM -0500, cothrige wrote:
> * Andrei Popescu ([EMAIL PROTECTED]) wrote:
> > On Mon, Oct 16, 2006 at 08:36:20AM -0500, cothrige wrote:
> >
> > Scenario1: You install stable (now sarge) and the entry in your sources.list
> > is 'stable'. When etch will be released the
* Andrei Popescu ([EMAIL PROTECTED]) wrote:
> On Mon, Oct 16, 2006 at 08:36:20AM -0500, cothrige wrote:
>
> Scenario1: You install stable (now sarge) and the entry in your sources.list
> is 'stable'. When etch will be released the next dist-upgrade will upgrade
> your whole system to etch *without
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
>
> If you want a little more control over the details, with a usable
> text-based user interface, use 'aptitude'.
> after it's started in a text console (very useful if your X is broken)
> the command 'u' updates its package lists, 'U' then does the
On Mon, Oct 16, 2006 at 08:36:20AM -0500, cothrige wrote:
>
> One thing that I am now curious about is the setup of sources.list and
> the release of the next stable. For instance, my sources.list was
> initially setup with entries for 'etch' such as "deb
> http://ftp.ndlug.nd.edu/mirrors/debian/
On Mon, Oct 16, 2006 at 08:49:23AM -0400, [EMAIL PROTECTED] wrote:
> On Mon, Oct 16, 2006 at 04:19:16AM -0400, Kevin Mark wrote:
> > On Sun, Oct 15, 2006 at 01:29:43PM -0500, cothrige wrote:
> Unfortulately, aptitude doesn't know if you explicitly requested a
> package using apt-get, so you will
On Mon, Oct 16, 2006 at 10:36:14 -0400, Roberto C. Sanchez wrote:
> On Mon, Oct 16, 2006 at 08:49:23AM -0400, [EMAIL PROTECTED] wrote:
> >
> > Isn't there a plugin or something for aptitude that can tell you about
> > extant bugs in packages that it's going to update for you? I seem to
> > reme
On Mon, Oct 16, 2006 at 08:49:23AM -0400, [EMAIL PROTECTED] wrote:
>
> Isn't there a plugin or something for aptitude that can tell you about
> extant bugs in packages that it's going to update for you? I seem to
> remember hearing about it, not having time to install it, and now wishin
> I ha
On Mon, Oct 16, 2006 at 04:19:16AM -0400, Kevin Mark wrote:
> On Sun, Oct 15, 2006 at 01:29:43PM -0500, cothrige wrote:
> > In reading online it seems that the standard practice to apply
> > security patches would be to run 'apt-get update' and then 'apt-get
> > upgrade'. I am curious if this real
cothrige wrote:
> Very cool. Good to know about that. But, I found that my system
> doesn't have any idea about anything like apt-listbugs. I followed
> the link in the article and found that there were packages listed for
> stable and unstable. How does one normally proceed from there? Will
>
* Steve Kemp ([EMAIL PROTECTED]) wrote:
> On Mon, Oct 16, 2006 at 08:36:20AM -0500, cothrige wrote:
>
> > I am not familiar with apt-listbugs and apt-changes. What are those?
>
>http://www.debian-administration.org/articles/44
>
>They show you outstanding bugs/changes which will be app
On Mon, Oct 16, 2006 at 08:36:20AM -0500, cothrige wrote:
> I am not familiar with apt-listbugs and apt-changes. What are those?
http://www.debian-administration.org/articles/44
They show you outstanding bugs/changes which will be applied when
you upgrade.
> One thing that I am now cu
* Kevin Mark ([EMAIL PROTECTED]) wrote:
> Hi Patrick,
Hello Kevin,
> the best option if you want stability and (little or) no breakage is to
> run 'stable'. This is what Debian releases. Although there is now
> security support for testing also.
I had actually intended initially to install Stabl
On Sun, 15 Oct 2006 21:30:05 -0500
Ron Johnson <[EMAIL PROTECTED]> wrote:
> On 10/15/06 21:03, Roberto C. Sanchez wrote:
> > On Sun, Oct 15, 2006 at 09:47:01PM -0400, [EMAIL PROTECTED]
> > wrote:
> >> Personally, I always use aptitude so I can see what it wants to do
> >> before it does it.
> >>
>
On Sun, Oct 15, 2006 at 01:29:43PM -0500, cothrige wrote:
> In reading online it seems that the standard practice to apply
> security patches would be to run 'apt-get update' and then 'apt-get
> upgrade'. I am curious if this really is the best way and if so, how
> often should it be done?
>
> I
On 10/15/06 21:03, Roberto C. Sanchez wrote:
On Sun, Oct 15, 2006 at 09:47:01PM -0400, [EMAIL PROTECTED] wrote:
Personally, I always use aptitude so I can see what it wants to do
before it does it.
As do I. But personally, I'd rather that the 200MB X update and OOo
update be downloaded at 3
On Sun, Oct 15, 2006 at 09:47:01PM -0400, [EMAIL PROTECTED] wrote:
> Personally, I always use aptitude so I can see what it wants to do
> before it does it.
>
As do I. But personally, I'd rather that the 200MB X update and OOo
update be downloaded at 3 AM, when I am (hopefully asleep). That is
Personally, I always use aptitude so I can see what it wants to do
before it does it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sun, Oct 15, 2006 at 03:16:47PM -0700, P. Johnson wrote:
> Roberto C. Sanchez wrote:
>
> > I like it because you can configure it to update the package list and do
> > nothing, to update the package list and download any pending updates but
> > not install them, or to update, download and insta
Roberto C. Sanchez wrote:
> I like it because you can configure it to update the package list and do
> nothing, to update the package list and download any pending updates but
> not install them, or to update, download and install all without
> intervention.
I would avoid updating, downloading an
* Roberto C. Sanchez ([EMAIL PROTECTED]) wrote:
> Moving this back on list so every gets the benefit.
>
Very sorry. I hit the r instead of L. I tend to do that when I am
not thinking, and that is too often.
> With Etch there will be more updates. I also recommend against having
> them automat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Oct 15, 2006 at 04:40:31PM -0400, Grok Mogger wrote:
> > * Roberto C. Sanchez ([EMAIL PROTECTED]) wrote:
> > >
> > > I like it because you can configure it to update the package list
> and do
> > > nothing, to update the package list and downl
On Sun, Oct 15, 2006 at 04:40:31PM -0400, Grok Mogger wrote:
>
> Would you really want to run something like cron-apt to keep your system
> up to date? Is that generally what people do? Just run a big apt-get
> update, apt-get upgrade? I'd just think that could have negative
> consequences (
> * Roberto C. Sanchez ([EMAIL PROTECTED]) wrote:
> >
> > I like it because you can configure it to update the package list
and do
> > nothing, to update the package list and download any pending
updates but
> > not install them, or to update, download and install all without
> > intervention.
Moving this back on list so every gets the benefit.
On Sun, Oct 15, 2006 at 02:38:21PM -0500, cothrige wrote:
> * Roberto C. Sanchez ([EMAIL PROTECTED]) wrote:
> >
> > I like it because you can configure it to update the package list and do
> > nothing, to update the package list and download any
On Sun, Oct 15, 2006 at 01:29:43PM -0500, cothrige wrote:
> In reading online it seems that the standard practice to apply
> security patches would be to run 'apt-get update' and then 'apt-get
> upgrade'. I am curious if this really is the best way and if so, how
> often should it be done?
>
> I
28 matches
Mail list logo
