freebsd-chat Digest, Vol 256, Issue 2
Sisantha Godawela-Ohle
ekerberos at web.de
Sun Apr 27 23:52:59 UTC 2008
Hello!
pl. someone tell me how to reinstall libkrb5.so.9, as i mistakenly remove it ( by installing Postgree or pureFTPd got the message that this should be deinstall!!)
Now i`m unable to log or start gnome-session but only kde!
thanks for any positive solution.
regards,
Sisantha
PS. version os is freebsd7.0
> -----Ursprüngliche Nachricht-----
> Von: freebsd-chat at freebsd.org
> Gesendet: 23.04.08 14:01:21
> An: freebsd-chat at freebsd.org
> Betreff: freebsd-chat Digest, Vol 256, Issue 2
> Send freebsd-chat mailing list submissions to
> freebsd-chat at freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freebsd.org/mailman/listinfo/freebsd-chat
> or, via email, send a message with subject or body 'help' to
> freebsd-chat-request at freebsd.org
>
> You can reach the person managing the list at
> freebsd-chat-owner at freebsd.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-chat digest..."
>
>
> Today's Topics:
>
> 1. Re: port management practices (Brian)
> 2. Re: port management practices (christopher)
> 3. Re: port management practices (Ravna)
> 4. Re: port management practices (Matthew D. Fuller)
> 5. Re: port management practices (christopher)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Apr 2008 08:02:06 -0700
> From: Brian <bri at brianwhalen.net>
> Subject: Re: port management practices
> To: freebsd-chat at freebsd.org
> Message-ID: <480DFDEE.5020303 at brianwhalen.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Jason C. Wells wrote:
> > I don't.
> >
> > It's too much work. I don't update ports for the duration of a major
> > release's life. What ever ports came out for 6.3 (that's when I quit
> > trying to manage ports) are typically what I am running. When 7.1 is
> > released (I don't run x.0 releases) I will reinstall ports based on a
> > homegrown script and a couple text files.
> >
> > My response is brief but I'll tell you I have tried everything. There
> > was much suffering that went into my ports management method. I'm much
> > happier now. I spend more time using my computers and less time
> > maintaining them.
> >
> > The problem is non-trivial. I am curious how -ports folks maintain
> > their sanity. That's a phenomena worth studying.
> >
> > Regards,
> > Jason
> >
> >
> I suppose this is relative to the number of ports installed, but it
> really isnt that difficult under normal circumstances. If you have one
> that needs to be treated differently, then ask why does it indeed to be
> treated differently and is it worth it. Over the last few years, I have
> had very few problems where portsnap followed by portupgrade didn't
> work. The dependency problems are the toughest, the last one of those
> I had I fixed with portmanager. For me, a goal worth pursuing is to
> make it easier, so you don't need to be a longterm user to figure out
> how to easily update system and/or ports, it should be a little easier
> AND apparent; even Microsoft and Redhat tell you when there are updates
> to be applied.
>
> Brian
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 22 Apr 2008 09:12:45 -0700
> From: christopher <skeptikos at gmail.com>
> Subject: Re: port management practices
> To: freebsd-chat at freebsd.org
> Message-ID: <20080422091245.818e3e86.skeptikos at gmail.com>
> Content-Type: text/plain; charset=US-ASCII
>
> On Tue, 22 Apr 2008 08:02:06 -0700
> Brian <bri at brianwhalen.net> wrote:
>
> > Jason C. Wells wrote:
> > > I don't.
> > >
> > > It's too much work. I don't update ports for the duration of a
>
> > I suppose this is relative to the number of ports installed, but it
> > really isnt that difficult under normal circumstances. If you have one
> > that needs to be treated differently, then ask why does it indeed to be
> > treated differently and is it worth it. Over the last few years, I have
> > had very few problems where portsnap followed by portupgrade didn't
> > work. The dependency problems are the toughest, the last one of those
> > I had I fixed with portmanager. For me, a goal worth pursuing is to
> > make it easier, so you don't need to be a longterm user to figure out
> > how to easily update system and/or ports, it should be a little easier
> > AND apparent; even Microsoft and Redhat tell you when there are updates
> > to be applied.
>
> I've kind of taken to the same practice as Jason by
> sticking with things once my system is up and running.
> It worked for me very well and it kept me with 5.4 for
> quite a long time. When I did do upgrades, I actually
> reinstalled them all by doing pkg_delete -a.
>
> I checked out the ports TODO, and there were some
> interesting things there, but nothing topical for my
> original query.
>
> I finally upgraded to 7.0, and that's when I ran into
> just the one issue with openoffice, actually cups is
> still giving me some issues, but that's not as vital. I
> use my system as a desktop, so there is gimp,
> openoffice, kde (for when my gf needs to use my
> computer), inkscape and a bunch of multimedia stuff.
> Some people say that FreeBSD isn't good, nor intended
> to be run as a desktop, but I am actually quite happy
> with it ~ Chris
>
> --
> christopher <skeptikos at gmail.com>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 23 Apr 2008 00:29:49 +0200
> From: Ravna <ravna at nerdshack.com>
> Subject: Re: port management practices
> To: freebsd-chat at freebsd.org
> Message-ID: <480E66DD.4040008 at nerdshack.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> It's my philosophy, that a little each day, is better than lots, once in
> a while.
> Cron updates my ports tree every night and does a "portupgrade -a"
> after that.
> The output is saved to a file, so I can deal with problems.
> I do a "buildworld/buildkernel" every week, if there are changes in the
> source.
> Nothing has ever been older than a few days.
> I don't see why my box should be bored while I'm asleep.
> It's always on, anyway.
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 22 Apr 2008 17:49:56 -0500
> From: "Matthew D. Fuller" <fullermd at over-yonder.net>
> Subject: Re: port management practices
> To: christopher <skeptikos at gmail.com>
> Cc: freebsd-chat at freebsd.org
> Message-ID: <20080422224956.GV67042 at over-yonder.net>
> Content-Type: text/plain; charset=us-ascii
>
> On Sun, Apr 20, 2008 at 09:17:17PM -0700 I heard the voice of
> christopher, and lo! it spake thus:
> >
> > I know about csup, portupgrade, etc., and I think they are great,
> > but if you only have one app that you want to upgrade because it was
> > buggy at a previous time, then it doesn't seem like a practical
> > undertaking when you consider all of the other apps involved and the
> > build times for things such as openoffice and kde.
>
> But it's usually not necessary to rebuild all the other apps.
>
> Certainly the deeper you go into dependancies, the greater the risk of
> downstream impact; a lot of things depend on libX11, so updating that
> may require rebuilding a lot of things. But the closer you get to the
> leaves, the less the issue is.
>
> I'm fairly sure I've *NEVER* used 'portupgrade -a'. I always use
> portversion to spit out the list of outdated things, and pick and
> choose what I update when. Wine takes a long time to build, so I
> usually hold that off 'till I don't mind nailing the system up for an
> hour or so. Some things I have local patches to, so I do them
> manually later. Deeper bits with a lot of things depending on them I
> save until I'll have a bit of time to deal with potential fallout
> (which is surprisingly rare, considering the complexity of the system;
> a great testament to the work of the maintainers). A lot of things I
> just drop into the todo list and fire off whenever they come up.
>
>
> I've had hiccups and oopses, but on the whole, it works very smoothly,
> and has for many years on many systems. I always hear these horror
> stories from people, but they keep obstinately refusing to happen to
> me. Life's rough sometimes 8-}
>
>
> --
> Matthew Fuller (MF4839) | fullermd at over-yonder.net
> Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
> On the Internet, nobody can hear you scream.
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 22 Apr 2008 20:04:18 -0700
> From: christopher <skeptikos at gmail.com>
> Subject: Re: port management practices
> To: freebsd-chat at freebsd.org
> Message-ID: <20080422200418.6afcdc84.skeptikos at gmail.com>
> Content-Type: text/plain; charset=US-ASCII
>
> On Wed, 23 Apr 2008 00:29:49 +0200
> Ravna <ravna at nerdshack.com> wrote:
>
> > It's my philosophy, that a little each day, is better than lots, once in
> > a while.
> > Cron updates my ports tree every night and does a "portupgrade -a"
> > after that.
> > The output is saved to a file, so I can deal with problems.
> > I do a "buildworld/buildkernel" every week, if there are changes in the
> > source.
>
> Wow, that's bold. I have to say, that while it seems
> to make sense, I'm pretty scared of trying it out. I
> would hate to think that I wake up and openoffice
> doesn't work for the paper I have to write. One of these
> days when I get an extra machine up and running, I'll
> be sure to try it though.
>
> --
> christopher <skeptikos at gmail.com>
>
>
> ------------------------------
>
> _______________________________________________
> freebsd-chat at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-chat
> To unsubscribe, send any mail to "freebsd-chat-unsubscribe at freebsd.org"
>
> End of freebsd-chat Digest, Vol 256, Issue 2
> ********************************************
>
_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten!
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114
More information about the freebsd-chat
mailing list