On Tuesday, April 05, 2016 12:22:49 PM Gary Jennejohn wrote:
> On Tue, 5 Apr 2016 10:22:04 +0100
> David Chisnall wrote:
>
> > On 5 Apr 2016, at 10:07, Gergely Czuczy wrote:
> > >
> > > Also, quite often entries from the base system are changed
> > > manually, think of root's/toor's password.
On Tue, 5 Apr 2016 13:42:48 -0400 (EDT)
Benjamin Kaduk wrote:
> On Tue, 5 Apr 2016, Gary Jennejohn wrote:
>
> > Will there be an option not to merge? I never update /etc when
> > I do installworld because what I have works for me and I see no
> > need to make any changes to a working system.
On 2016-04-05 13:42, Benjamin Kaduk wrote:
On Tue, 5 Apr 2016, Gary Jennejohn wrote:
Will there be an option not to merge? I never update /etc when
I do installworld because what I have works for me and I see no
need to make any changes to a working system.
And you expect your system to cont
On Tue, 5 Apr 2016, Gary Jennejohn wrote:
> Will there be an option not to merge? I never update /etc when
> I do installworld because what I have works for me and I see no
> need to make any changes to a working system.
And you expect your system to continue working after a new system user is
a
On Tue, Apr 05, 2016 at 12:22:49PM +0200, Gary Jennejohn wrote:
> On Tue, 5 Apr 2016 10:22:04 +0100
> David Chisnall wrote:
>
> > On 5 Apr 2016, at 10:07, Gergely Czuczy wrote:
> > >
> > > Also, quite often entries from the base system are changed
> > > manually, think of root's/toor's password
On Tue, 5 Apr 2016 10:22:04 +0100
David Chisnall wrote:
> On 5 Apr 2016, at 10:07, Gergely Czuczy wrote:
> >
> > Also, quite often entries from the base system are changed
> > manually, think of root's/toor's password. Are such cases
> > going to be dealt with properly between upgrades, includ
On 5 Apr 2016, at 10:07, Gergely Czuczy wrote:
>
> Also, quite often entries from the base system are changed manually, think of
> root's/toor's password. Are such cases going to be dealt with properly
> between upgrades, including self-built-and-packaged base systems? Currently
> it can be a
On 2016-01-27 23:33, Glen Barber wrote:
As many know, work has been in progress for quite some time to provide
the ability to package and upgrade the FreeBSD base system using pkg(8).
The majority of the initial implementation has provided much of the core
functionality to make this possible, ho
On Fri, Jan 29, 2016 at 01:24:53PM -0800, Maxim Sobolev wrote:
> Pentium-IV in 1980? I think we are talking about +35 years from now.
+35 years is incorrect calculated.
Only +14.
> On Fri, Jan 29, 2016 at 12:40 AM, Slawa Olhovchenkov wrote:
>
> > On Thu, Jan 28, 2016 at 10:30:25PM -0800, Maxi
Pentium-IV in 1980? I think we are talking about +35 years from now.
-Max
On Fri, Jan 29, 2016 at 12:40 AM, Slawa Olhovchenkov wrote:
> On Thu, Jan 28, 2016 at 10:30:25PM -0800, Maxim Sobolev wrote:
>
> > That would be like trying to install FreeBSD 11 on PDP-11 hardware. Good
> > luck with th
On Thu, Jan 28, 2016 at 10:30:25PM -0800, Maxim Sobolev wrote:
> That would be like trying to install FreeBSD 11 on PDP-11 hardware. Good
> luck with that, Slawa, you'll need it! :)
On Pentium-IV.
___
freebsd-current@freebsd.org mailing list
https://lis
That would be like trying to install FreeBSD 11 on PDP-11 hardware. Good
luck with that, Slawa, you'll need it! :)
On Thu, Jan 28, 2016 at 8:09 AM, Allan Jude wrote:
> On 2016-01-28 11:06, Slawa Olhovchenkov wrote:
> > On Thu, Jan 28, 2016 at 02:18:06PM +0100, Baptiste Daroussin wrote:
> >
> >>
On Thu, Jan 28, 2016 at 02:58:52PM -0500, Nikolai Lifanov wrote:
>
>
> On January 28, 2016 1:23:22 PM EST, Glen Barber wrote:
> >On Thu, Jan 28, 2016 at 09:12:53PM +0300, Slawa Olhovchenkov wrote:
> >> I see two hudge problem for support upgrades from older RELEASE
> >> versions (supported too):
On January 28, 2016 1:23:22 PM EST, Glen Barber wrote:
>On Thu, Jan 28, 2016 at 09:12:53PM +0300, Slawa Olhovchenkov wrote:
>> I see two hudge problem for support upgrades from older RELEASE
>> versions (supported too): key (used for repo signing) change and need
>> to access ports packages to i
On Thu, Jan 28, 2016 at 06:23:22PM +, Glen Barber wrote:
> On Thu, Jan 28, 2016 at 09:12:53PM +0300, Slawa Olhovchenkov wrote:
> > I see two hudge problem for support upgrades from older RELEASE
> > versions (supported too): key (used for repo signing) change and need
> > to access ports packa
On Thu, Jan 28, 2016 at 09:12:53PM +0300, Slawa Olhovchenkov wrote:
> I see two hudge problem for support upgrades from older RELEASE
> versions (supported too): key (used for repo signing) change and need
> to access ports packages to install (installed outdated release can't
> find pkg packet for
On Thu, Jan 28, 2016 at 05:56:31PM +, David Chisnall wrote:
> On 28 Jan 2016, at 17:45, NGie Cooper wrote:
> >
> > Also, consider that you're going to be allowing upgrades from older RELEASE
> > versions of the OS which might be using a fixed copy of pkgng -- how are
> > you going to suppo
On Thu, Jan 28, 2016 at 09:45:16AM -0800, NGie Cooper wrote:
>
> > On Jan 28, 2016, at 09:38, Slawa Olhovchenkov wrote:
> >
> >> On Thu, Jan 28, 2016 at 09:28:32AM -0800, NGie Cooper wrote:
> >>
> >>
> >>> On Jan 28, 2016, at 08:06, Slawa Olhovchenkov wrote:
> >>
> >>
> >> ...
> >>
> >>>
On 28 Jan 2016, at 17:45, NGie Cooper wrote:
>
> Also, consider that you're going to be allowing upgrades from older RELEASE
> versions of the OS which might be using a fixed copy of pkgng -- how are you
> going to support that?
I believe that the plan is to promote the pkg tool somewhat close
> On Jan 28, 2016, at 09:38, Slawa Olhovchenkov wrote:
>
>> On Thu, Jan 28, 2016 at 09:28:32AM -0800, NGie Cooper wrote:
>>
>>
>>> On Jan 28, 2016, at 08:06, Slawa Olhovchenkov wrote:
>>
>>
>> ...
>>
>>> What about upgrade strongly outdated system?
>>> For example 11.0 at time 18.0? I.e. p
On 2016-01-28 12:25, Slawa Olhovchenkov wrote:
> On Thu, Jan 28, 2016 at 12:04:00PM -0500, Allan Jude wrote:
>
>> On 2016-01-28 12:00, Slawa Olhovchenkov wrote:
>>> On Thu, Jan 28, 2016 at 11:09:56AM -0500, Allan Jude wrote:
>>>
>> Yes, but but real usage of it would happen in a second step be
On Thu, Jan 28, 2016 at 11:09:56AM -0500, Allan Jude wrote:
> The approach for offering an upgrade from 10.x to 11.0 will be the more
> interesting endeavour.
>
At present, the plan is to provide supported 10.x releases with the
knowledge of what is added/removed in 11.0-RELEASE, be it through
a
On Thu, Jan 28, 2016 at 09:28:32AM -0800, NGie Cooper wrote:
>
> > On Jan 28, 2016, at 08:06, Slawa Olhovchenkov wrote:
>
>
> ...
>
> > What about upgrade strongly outdated system?
> > For example 11.0 at time 18.0? I.e. packages for 11.0 don't available,
> > pkg from 11.0 don't undertund pac
> On Jan 28, 2016, at 08:09, Allan Jude wrote:
...
> According to our current release schedule, FreeBSD 18.0 will not come
> out for 35 years (2051).
>
> The general approach would appear to be just downloading new packages
> and updating the system. For a drastic upgrade like that, you'd like
> On Jan 28, 2016, at 08:06, Slawa Olhovchenkov wrote:
...
> What about upgrade strongly outdated system?
> For example 11.0 at time 18.0? I.e. packages for 11.0 don't available,
> pkg from 11.0 don't undertund package base from 18.0 and etc.
This is an important question to ask and solve. Th
On Thu, Jan 28, 2016 at 12:04:00PM -0500, Allan Jude wrote:
> On 2016-01-28 12:00, Slawa Olhovchenkov wrote:
> > On Thu, Jan 28, 2016 at 11:09:56AM -0500, Allan Jude wrote:
> >
> Yes, but but real usage of it would happen in a second step because of
> many
> rought edges to be dea
This is going to be huge for FreeBSD. Thank you Glen, Bapt and I
believe Peter Wemm as well.
Having been engineering lead on multiple appliances based on FreeBSD
this is going to revolutionize and make life so much easier for future
appliance endeavors and general manageability of FreeBSD.
On 2016-01-28 12:00, Slawa Olhovchenkov wrote:
> On Thu, Jan 28, 2016 at 11:09:56AM -0500, Allan Jude wrote:
>
Yes, but but real usage of it would happen in a second step because of many
rought edges to be deal with. but yes the information would be available
see:
https://
On Thu, Jan 28, 2016 at 11:09:56AM -0500, Allan Jude wrote:
> >> Yes, but but real usage of it would happen in a second step because of many
> >> rought edges to be deal with. but yes the information would be available
> >>
> >> see:
> >> https://www.youtube.com/watch?v=Br6izhH5P1I
> >> and
> >> h
On 2016-01-28 11:06, Slawa Olhovchenkov wrote:
> On Thu, Jan 28, 2016 at 02:18:06PM +0100, Baptiste Daroussin wrote:
>
>> On Thu, Jan 28, 2016 at 12:46:39PM +, Thomas Mueller wrote:
>>> from Glen Barber:
>>>
As many know, work has been in progress for quite some time to provide
the a
On Thu, Jan 28, 2016 at 02:18:06PM +0100, Baptiste Daroussin wrote:
> On Thu, Jan 28, 2016 at 12:46:39PM +, Thomas Mueller wrote:
> > from Glen Barber:
> >
> > > As many know, work has been in progress for quite some time to provide
> > > the ability to package and upgrade the FreeBSD base sy
On Thu, Jan 28, 2016 at 12:46:39PM +, Thomas Mueller wrote:
> from Glen Barber:
>
> > As many know, work has been in progress for quite some time to provide
> > the ability to package and upgrade the FreeBSD base system using pkg(8).
> > The majority of the initial implementation has provided
from Glen Barber:
> As many know, work has been in progress for quite some time to provide
> the ability to package and upgrade the FreeBSD base system using pkg(8).
> The majority of the initial implementation has provided much of the core
> functionality to make this possible, however much work
Awesome. Thanks for the update, and info Glen. It looks like I will be
subscribing to another list tonight!
Joe Maloney
On 01/27/16 16:33, Glen Barber wrote:
As many know, work has been in progress for quite some time to provide
the ability to package and upgrade the FreeBSD base system usin
As many know, work has been in progress for quite some time to provide
the ability to package and upgrade the FreeBSD base system using pkg(8).
The majority of the initial implementation has provided much of the core
functionality to make this possible, however much work still needs to be
done.
Ov
35 matches
Mail list logo