On 2013.09.18 14:36, Glen Barber wrote:
Changes between -ALPHA1 and -ALPHA2 include:
...
o Import Hyper-V paravirtualized drivers from projects/hyperv
branch.
These were merged in r255524 and are in -ALPHA1 (I am currently using them). Or
has something changed with them?
FreeBSD talkingzebra 10.0-ALPHA3 FreeBSD 10.0-ALPHA3 #0 r255918: Fri Sep 27
17:29:41 CDT 2013
toor@talkingzebra:/usr/obj/usr/src/sys/HYPERV amd64
Sometimes after a reboot, the interfaces get an IP (statically set), but there
is no connectivity. Starting or restarting the netif service
causes
On 2014.08.08 17:41, Daniel Peyrolon wrote:
What would be the better way to avoid this happening in the future?
Always update the bootloader before doing a zpool upgrade on your root pool.
___
freebsd-current@freebsd.org mailing list
On 2014.08.31 11:41, Allan Jude wrote:
That would seem to make sense. Where do these settings actually get
stored? Where would I find a list of the possible settings to create the
dialog?
Setting them in /etc/login.conf for the default user class is how I do it.
On 2014.09.01 20:51, Michelle Sullivan wrote:
And for the portsnap users?
In short, this change doesn't directly effect portsnap users.
Sure about that?
I'm sure of it. Your issue is with the tree itself, not the tool used to fetch
it.
Correct, take a 9.2 install disk, install it,
On 2014.09.01 21:27, Michelle Sullivan wrote:
Actually it's an inconvenience for someone like me and you. Not for
many freebsd users, and certainly not for me 6 months ago if I hadn't
been writing my own ports oh and what was it, 1.3.6 - 1.3.7? broke
shit... (badly) ...
There were
On 2014.09.01 21:39, Julian Elischer wrote:
sigh.. when are we as a project, all going to learn that reality in
business is
that you often need to install stuff that is old. Its not always your
choice.
The custommers require it..
You should try arguing with someone like Bank of Americas
On 2014.09.01 22:09, Michelle Sullivan wrote:
That's my point - there was a patch waiting to submit that knowingly
broke pkg_install at midnight on the day after the EOL... the EOL
shouldn't be an EOL - because it was really a 'portsnap after this date
before you upgrade and you're screwed it
On 2016.01.07 06:43, David Wolfskill wrote:
> The attached patch gets through the buildkernel. After install & reboot,
> I'm not seeing obvious issues -- I can still talk to the box over TCP, at
> least.
This exact change was committed about an hour ago.
On 2016.04.20 07:58, Lev Serebryakov wrote:
It is very worrying to see such reports without any reaction from
developers in one month before release. If there is one year till
release, it is nothing. But in one month we will have code slush, and
after that — release, which should be supported
10 matches
Mail list logo