On Feb 24, 2014, at 7:40 AM, Bryan Drewery wrote:
> Anything not meeting the bare-bones criteria can be installed with 'pkg
> install' or ports.
Try this in a shop where all your machines are completely air-gapped from the
internet.
signature.asc
Description: Message signed with OpenPGP usin
On Feb 24, 2014, at 7:56 AM, Poul-Henning Kamp wrote:
> Bullshit.
Sounds like your week didn't get off to a good start.
> You got FreeBSD in there in the first place, there clearly
> is some kind of aperture through which software can migrate.
Yes, we walk in a DVD-ROM with a FreeBSD installat
On Feb 24, 2014, at 8:50 AM, David Chisnall wrote:
> Or, purely hypothetically, if your goal was to make it work, you could just
> use Poudriere which will take a list of packages that you need and build a
> package set for you, which you can stick on a DVD / USB stick / whatever and
> take i
On Feb 27, 2014, at 12:20 PM, Matthew Rezny wrote:
> If IPv4LL is in active use, the DHCP
> client should continue to periodically look for a DHCP server and obtain a
> lease without manual user intervention (which is unfortunately required on
> both OS X and Windows, leading to sub-optimal e
On Feb 27, 2014, at 15:59, Matthew Rezny wrote:
> If they corrected that, it was after I abandoned the platform years ago.
It has been like that since at least 10.8.
And I am also tempted to say that Windows 7 acts the same, but I don't have one
at hand to double check.
_
On Jul 20, 2014, at 11:35 AM, Daniel Feenberg wrote:
> Rather they have said "An updated pf would not be
> suitable, as it would be incompatible with existing configuration files".
A major FreeBSD version increment is allowed to break that level of backwards
compatibility. Nothing prevents th
On Sep 12, 2014, at 2:40 PM, Baptiste Daroussin wrote:
> If you want interoperability just use /usr/bin/env bash as a shebang. Btw you
> cannot get interoprability with OS-X in there because the bash they do provide
> is the last GPL-2 recent bash have many incompatiblities with this old
> vers
On Sep 12, 2014, at 3:23 PM, Craig Rodrigues wrote:
> Forcing all upstream script writers to switch to "#!/usr/bin/env bash", or
> to convert their scripts to "#!/bin/sh" and remove all bash-specific
> behaviors, is getting harder and harder,
> since many people are exposed to MacOS X and Linux
On Sep 12, 2014, at 3:55 PM, Bryan Drewery wrote:
> There already is one and ports requires using it!
Doh!
signature.asc
Description: Message signed with OpenPGP using GPGMail
On 2013-04-29, at 8:27 PM, Teske, Devin wrote:
> http://www.youtube.com/watch?v=SXmv8quf_xM
>
> (Please, don't be drinking anything.. I disclaim all responsibility
> for keyboard damage)
Please, PLEASE, can we have a "Where Are They Now" segment about this kid? I
want to know which company he
A couple of months ago I wrote a shell implementation of adduser.
One of the things that bothered me about the old version was the
way its policy and configuration pretty much duplicated that of pw(8).
Being able to set inconsistent policy like this is not good. Also,
pw already implemented all of
> The linux hdparm program is so paranoid about this that you have to use
> extra arguments like "--yes-really-destroy-my-disk-drive" to do this.
I concur. Loudly. The ability to brick your hardware is just too
large to not make people go through the "I tell you three times"
dance. It's not lik
Dan Mack writes:
> I'm wondering if anyone can help point me at a good way to continously
> capture every inbound and outbound connection made to a freebsd system.
Assuming "connection" means "log every TCP connection setup" probably
the quickest way is to tcpdump every TCP packet with both SYN
Olivier Certner writes:
> I've never found any compelling reason in most uses to enable "atime", except
> perhaps local mail but as addressed in other answers it is a relic of the pa
> st mostly irrelevant today. And its drawbacks are well known and can be seri
> ous.
When UNIX ran on PDP-11s a
> > I do not have a strong opinion w.r.t. atime, but I do believe that
> > changing the default would be a POLA violation.
I'm not prepared to just accept that at face value.
I can't think of a single instance in at least the last three decades
where I have actually used or needed atime for *anyt
Warner Losh writes:
> > I'm really interested in hearing from people who actively use
> > atime on a regular basis for non-trivial purposes. What are
> > the modern use cases for atime?
> The consensus was we'd fix it in the installer.
Sure, but my question still stands. I'm genuinely curious
101 - 116 of 116 matches
Mail list logo
