On 2018-06-23 12:58, Eitan Adler wrote:
On 23 June 2018 at 08:50, James Gritton wrote:
On 2018-06-23 09:45, Eitan Adler wrote:
On 23 June 2018 at 08:30, James Gritton wrote:
On 2018-06-22 16:03, Miroslav Lachman wrote:
Chris H wrote on 2018/06/22 23:46:
On Fri, 22 Jun 2018 23:13:17
On 2018-06-23 09:45, Eitan Adler wrote:
On 23 June 2018 at 08:30, James Gritton wrote:
On 2018-06-22 16:03, Miroslav Lachman wrote:
Chris H wrote on 2018/06/22 23:46:
On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman"
<000.f...@quip.cz>
said
I don't know if it is b
On 2018-06-22 16:03, Miroslav Lachman wrote:
Chris H wrote on 2018/06/22 23:46:
On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman"
<000.f...@quip.cz> said
I don't know if it is better to discuss it in jail@ or stable@ list
so a do cross-post.
FreeBSD has many jail aware utilities but
On 2015-07-17 11:26, Per olof Ljungmark wrote:
On 2015-07-17 01:41, James Gritton wrote:
On 2015-07-15 13:52, Per olof Ljungmark wrote:
FreeBSD 10.2-PRERELEASE #0 r284949
The jail can be started, but when /etc/rc is executed:
root@mar:/ # sh -x /etc/rc
+ stty status ^T
/etc/rc: cannot create
On 2015-07-15 13:52, Per olof Ljungmark wrote:
FreeBSD 10.2-PRERELEASE #0 r284949
The jail can be started, but when /etc/rc is executed:
root@mar:/ # sh -x /etc/rc
+ stty status ^T
/etc/rc: cannot create /dev/null: Operation not supported
+ trap : 2
+ trap 'echo '\''Boot interrupted'\''; exit
Bjoern A. Zeeb wrote:
The plan as the status report will say is to get this in, merge it to
stable/7 before 7.2 and keep it in 8.
8 will also have vimages and ideally I'd like to see this entire jail
IP hacks be gone for 9, when vimage will provide the infrastructure,
etc. This means that 8
John Baldwin wrote:
On Thursday 19 June 2008 11:57:51 am James Gritton wrote:
John Baldwin wrote:
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock
John Baldwin wrote:
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a
specific (although mundane) hardware configuration, and each of several
servers
