#
d0b2dbfa |
|
16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line sh pattern Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
#
34566598 |
|
20-Jun-2023 |
John Baldwin <jhb@FreeBSD.org> |
jail: Mute -Wunused-but-set-variable for yynerrs. This is in the generated parser when using %pure-parser. y.tab.c:382:14: error: variable 'yynerrs' set but not used [-Werror,-Wunused-but-set-variable] int yynerrs; ^ Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D40671
|
#
1da495d0 |
|
21-Nov-2019 |
Ed Maste <emaste@FreeBSD.org> |
revert r354935 and apply fix for cleandir failure This reapplies the RISC-V GNU ld workaround from r354896, r354899, and 354900, along with a fix for the build failure during cleandir. LINKER_TYPE was not being set during cleandir, resulting in Malformed conditional (${LINKER_TYPE} == "bfd" && ${MACHINE} == "riscv") from Cirrus-CI. PR: 242109 Sponsored by: The FreeBSD Foundation
|
#
fb1c294d |
|
20-Nov-2019 |
Glen Barber <gjb@FreeBSD.org> |
Revert r354896, r354899, r354900: Fix build. Sponsored by: Rubicon Communications, LLC (netgate.com)
|
#
7cef5cac |
|
20-Nov-2019 |
Li-Wen Hsu <lwhsu@FreeBSD.org> |
Use the correct variable, also limit the scope to bfd PR: 242109 Reported by: jhb Sponsored by: The FreeBSD Foundation
|
#
f10ddee8 |
|
20-Nov-2019 |
Li-Wen Hsu <lwhsu@FreeBSD.org> |
Limit the workaround to riscv only PR: 242109 Sponsored by: The FreeBSD Foundation
|
#
53c772bb |
|
20-Nov-2019 |
Li-Wen Hsu <lwhsu@FreeBSD.org> |
Workaround riscv64 build when using binutils 2.33.1 PR: 242109 Reviewed by: bapt Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D22457
|
#
cd38a86c |
|
12-Sep-2019 |
Michael Zhilin <mizhka@FreeBSD.org> |
[jail] removal by jid doesn't trigger pre/post stop scripts This commit fixes bug: command "jail -r" didn't trigger pre/post stop commands (and others) defined in config file if jid is specified insted of name. Also it adds basic tests for usr.sbin/jail to avoid regression. Reviewed by: jamie, kevans, ray MFC after: 5 days Differential Revision: https://reviews.freebsd.org/D21328
|
#
a9a39d40 |
|
10-Sep-2019 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Stop linking to libl by specifying we do not need yywrap MFC after: 3 days
|
#
ed0d9218 |
|
20-Jan-2016 |
Glen Barber <gjb@FreeBSD.org> |
Add a package for jail(8) and related utilities. Sponsored by: The FreeBSD Foundation
|
#
c6db8143 |
|
25-Nov-2014 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Convert usr.sbin to LIBADD Reduce overlinking
|
#
c6063d0d |
|
05-May-2014 |
Warner Losh <imp@FreeBSD.org> |
Use src.opts.mk in preference to bsd.own.mk except where we need stuff from the latter.
|
#
7e659f94 |
|
19-Apr-2013 |
Ed Schouten <ed@FreeBSD.org> |
Add the Clang specific -Wmissing-variable-declarations to WARNS=6. This compiler flag enforces that that people either mark variables static or use an external declarations for the variable, similar to how -Wmissing-prototypes works for functions. Due to the fact that Yacc/Lex generate code that cannot trivially be changed to not warn because of this (lots of yy* variables), add a NO_WMISSING_VARIABLE_DECLARATIONS that can be used to turn off this specific compiler warning. Announced on: toolchain@
|
#
5fb611c2 |
|
20-Jun-2011 |
Jamie Gritton <jamie@FreeBSD.org> |
Following r222465: Check for IPv4 or IPv6 to be available by the kernel to not provoke errors trying to query options not available. Make it possible to compile out INET or INET6 only parts.
|
#
15ede760 |
|
29-May-2011 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
Check for IPv4 or IPv6 to be available by the kernel to not provoke errors trying to query options not available. Make it possible to compile out INET or INET6 only parts. Reviewed by: jamie Sponsored by: The FreeBSD Foundation Sponsored by: iXsystems MFC after: 10 days
|
#
2671ee73 |
|
20-Oct-2010 |
Jamie Gritton <jamie@FreeBSD.org> |
Initial work on the new jail(8). There are more features to add, and some cleaning up to do on existing features, but this is pretty much what the final product will look like.
|
#
fe0506d7 |
|
09-Mar-2010 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Create the altix project branch. The altix project will add support for the SGI Altix 350 to FreeBSD/ia64. The hardware used for porting is a two-module system, consisting of a base compute module and a CPU expansion module. SGI's NUMAFlex architecture can be an excellent platform to test CPU affinity and NUMA-aware features in FreeBSD.
|
#
71ccf092 |
|
02-Jan-2010 |
Ed Schouten <ed@FreeBSD.org> |
The last big commit: let usr.sbin/ use WARNS=6 by default.
|
#
de6f3704 |
|
24-Jun-2009 |
Jamie Gritton <jamie@FreeBSD.org> |
Add libjail, a (somewhat) simpler interface to the jail_set and jail_get system calls and the security.jail.param sysctls. Approved by: bz (mentor)
|
#
413628a7 |
|
29-Nov-2008 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
MFp4: Bring in updated jail support from bz_jail branch. This enhances the current jail implementation to permit multiple addresses per jail. In addtion to IPv4, IPv6 is supported as well. Due to updated checks it is even possible to have jails without an IP address at all, which basically gives one a chroot with restricted process view, no networking,.. SCTP support was updated and supports IPv6 in jails as well. Cpuset support permits jails to be bound to specific processor sets after creation. Jails can have an unrestricted (no duplicate protection, etc.) name in addition to the hostname. The jail name cannot be changed from within a jail and is considered to be used for management purposes or as audit-token in the future. DDB 'show jails' command was added to aid debugging. Proper compat support permits 32bit jail binaries to be used on 64bit systems to manage jails. Also backward compatibility was preserved where possible: for jail v1 syscalls, as well as with user space management utilities. Both jail as well as prison version were updated for the new features. A gap was intentionally left as the intermediate versions had been used by various patches floating around the last years. Bump __FreeBSD_version for the afore mentioned and in kernel changes. Special thanks to: - Pawel Jakub Dawidek (pjd) for his multi-IPv4 patches and Olivier Houchard (cognet) for initial single-IPv6 patches. - Jeff Roberson (jeff) and Randall Stewart (rrs) for their help, ideas and review on cpuset and SCTP support. - Robert Watson (rwatson) for lots and lots of help, discussions, suggestions and review of most of the patch at various stages. - John Baldwin (jhb) for his help. - Simon L. Nielsen (simon) as early adopter testing changes on cluster machines as well as all the testers and people who provided feedback the last months on freebsd-jail and other channels. - My employer, CK Software GmbH, for the support so I could work on this. Reviewed by: (see above) MFC after: 3 months (this is just so that I get the mail) X-MFC Before: 7.2-RELEASE if possible
|
#
d7f03759 |
|
19-Oct-2008 |
Ulf Lilleengen <lulf@FreeBSD.org> |
- Import the HEAD csup code which is the basis for the cvsmode work.
|
#
d1df3fcd |
|
17-Nov-2004 |
Xin LI <delphij@FreeBSD.org> |
Initialize lcap and pwd to NULL. This allows a WARNS=6 clean build, hence bump it to 6. Note that the last commit message was not quite accurate. While the assumption exists in the code, it's not possible to have an uninitialized p there because if lflag is set when username is NULL then execution would be terminated earlier.
|
#
d6131f4b |
|
26-Mar-2003 |
Maxim Konovalov <maxim@FreeBSD.org> |
o Add -u <username> flag to jail(8): set user context before exec. PR: bin/44320 Submitted by: Mike Matsnev <mike@po.cs.msu.su> Reviewed by: -current MFC after: 6 weeks
|
#
90e655ea |
|
20-Jul-2001 |
David E. O'Brien <obrien@FreeBSD.org> |
Perform a major cleanup of the usr.sbin Makefiles. These are not perfectly in agreement with each other style-wise, but they are orders of orders of magnitude more consistent style-wise than before.
|
#
f6751868 |
|
29-Jun-2001 |
Dima Dorfman <dd@FreeBSD.org> |
Set WARNS=2 on programs that compile cleanly with it; add $FreeBSD$ where necessary. Submitted by: Mike Barcroft <mike@q9media.com>
|
#
345e52e7 |
|
26-Mar-2001 |
Ruslan Ermilov <ru@FreeBSD.org> |
- Backout botched attempt to introduce MANSECT feature. - MAN[1-9] -> MAN.
|
#
c73e22c3 |
|
20-Mar-2001 |
Ruslan Ermilov <ru@FreeBSD.org> |
Set the default manual section for usr.sbin/ to 8.
|
#
97d92980 |
|
27-Aug-1999 |
Peter Wemm <peter@FreeBSD.org> |
$Id$ -> $FreeBSD$
|
#
c020621f |
|
05-May-1999 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Various cosmetics. Submitted by: Rudolf Cejka <cejkar@dcse.fee.vutbr.cz> Reviewed by: phk
|
#
ce5c1cd1 |
|
04-May-1999 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Fix various bogons. Submitted by: Rudolf Cejka <cejkar@dcse.fee.vutbr.cz> Reviewed by: phk
|
#
75c13541 |
|
28-Apr-1999 |
Poul-Henning Kamp <phk@FreeBSD.org> |
This Implements the mumbled about "Jail" feature. This is a seriously beefed up chroot kind of thing. The process is jailed along the same lines as a chroot does it, but with additional tough restrictions imposed on what the superuser can do. For all I know, it is safe to hand over the root bit inside a prison to the customer living in that prison, this is what it was developed for in fact: "real virtual servers". Each prison has an ip number associated with it, which all IP communications will be coerced to use and each prison has its own hostname. Needless to say, you need more RAM this way, but the advantage is that each customer can run their own particular version of apache and not stomp on the toes of their neighbors. It generally does what one would expect, but setting up a jail still takes a little knowledge. A few notes: I have no scripts for setting up a jail, don't ask me for them. The IP number should be an alias on one of the interfaces. mount a /proc in each jail, it will make ps more useable. /proc/<pid>/status tells the hostname of the prison for jailed processes. Quotas are only sensible if you have a mountpoint per prison. There are no privisions for stopping resource-hogging. Some "#ifdef INET" and similar may be missing (send patches!) If somebody wants to take it from here and develop it into more of a "virtual machine" they should be most welcome! Tools, comments, patches & documentation most welcome. Have fun... Sponsored by: http://www.rndassociates.com/ Run for almost a year by: http://www.servetheweb.com/
|