Date: Sun, 12 Jul 2015 21:42:24 -0400 From: Quartz <quartz@sneakertech.com> To: kpneal@pobox.com Cc: FreeBSD questions <freebsd-questions@freebsd.org> Subject: Re: Questions about freebsd-update Message-ID: <55A31780.2050103@sneakertech.com> In-Reply-To: <20150712192836.GA3919@neutralgood.org> References: <559C6B73.8050509@sneakertech.com> <559EA8B8.8080701@sneakertech.com> <559ED47E.8050905@hiwaay.net> <559F25F8.1030508@sneakertech.com> <559F2853.5000103@sneakertech.com> <55A12660.9090304@gmx.de> <55A20318.8010506@sneakertech.com> <20150712192836.GA3919@neutralgood.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> What level of granularity would you prefer for freebsd-update? With OSX/Windows I can see the past list of system updates/KBs made available since the base OS came out. I apparently can't do that with freebsd-update. With OSX/Windows I have the option of foregoing the most recent update(s) and installing only an older version if necessary. I apparently can't do that with freebsd-update. With OSX/Windows I have the ability to download some of the major updates separately as standalone packages, which I can then copy over via usb stick and install offline. I apparently can't do that with freebsd-update. I originally started this thread hoping that I was just wrong about freebsd-update, that maybe it was more advanced than I thought, that there was a simpler way to do updates besides the src/make/install dance. It's clear to me now that the situation is what I thought it was, so I'll just continue dealing with it the way I always have.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55A31780.2050103>