| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
has eliminated alignment and endian problems that were making it fail on
some platforms.
PR: 180438
PR: 189415
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
many thanks for their continued support of FreeBSD.
While I'm there, also implement a new build knob, WITHOUT_HYPERV to
disable building and installing of the HyperV utilities when necessary.
The HyperV utilities are only built for i386 and amd64 targets.
This is a stable/10 candidate for inclusion with 10.1-RELEASE.
Submitted by: Wei Hu <weh microsoft com>
MFC after: 1 week
|
|
|
|
|
|
| |
- Reconnect with some minor modifications, in particular now selsocket()
internals are adapted to use sbintime units after recent'ish calloutng
switch.
|
|
|
|
|
|
|
|
| |
piece of bsdinstall (although this time with a symlink instead of duplicated
source code).
Discussed on: freebsd-geom
MFC after: 3 months
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GIANT from VFS. In addition, disconnect also netsmb, which is a base
requirement for SMBFS.
In the while SMBFS regular users can use FUSE interface and smbnetfs
port to work with their SMBFS partitions.
Also, there are ongoing efforts by vendor to support in-kernel smbfs,
so there are good chances that it will get relinked once properly locked.
This is not targeted for MFC.
|
|
|
|
|
|
|
|
|
|
|
|
| |
GIANT from VFS. In addition, disconnect also netncp, which is a base
requirement for NWFS.
In the possibility of a future maintenance of the code and later
readd to the FreeBSD base, maybe we should think about a better location
for netncp. I'm not entirely sure the / top location is actually right,
however I will let network people to comment on that more specifically.
This is not targeted for MFC.
|
|
Reviewed by: arch@ (many times, no objection)
|