Outstanding, thank you. Curious though, how is Gnome looking these days 
(meaning, is it v3 or 2.x).

I have read of the craziness of 3 and the introduction of Unity (albeit that is 
ubuntu).

If 3 is used (or when) I assume it would be closer to what I currently have 
under Sid (and that would be ok) or even 2.x 


Nonetheless, thanks for the info. I'll have time tomorrow to read up a bit and 
perhaps next time I post, it'll be under 9

Sent from my HTC.

----- Reply message -----
From: "Adam Vande More" <[email protected]>
Date: Fri, Feb 3, 2012 12:10 am
Subject: Possible move back to FreeBSD
To: "Chris" <[email protected]>
Cc: "[email protected]" <[email protected]>


On Thu, Feb 2, 2012 at 11:34 PM, Chris <[email protected]> wrote:

> I have been using Debian for a few years now (previous BSD user) and I'm
> considering moving back.
>
> Admittedly, I have gotten used to the simplicity of using apt-get to
> update the system.
>
> What will pull me back is if there is an equivalent to use. I do not
> intend on custom kernels, and I don't intend on using ports (it was the
> many hours spent keeping the ports tree current along with installed ports).
>
> If someone would suggest the material to read and perhaps a synopsis of
> the process, I would be happy to do the leg work.
>


freebsd-update(1) and pkgng should get you to relative feature parity w/
Debian.   However pkgng just entered beta, and likely won't make it into
the base system anytime soon.  That being said, beta testers are wanted and
it's largely functional.

/usr/ports/UPDATING is still the standard method along with a ports
managment tool of your choice eg portmaster(1).



-- 
Adam Vande More
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"

Reply via email to