On Wed, Feb 11, 2015 at 10:36:19AM -0500, trondd wrote:
> On 2/10/15, Diana Eichert wrote:
> > names to something more useful than "p3p2"!!!.
> >
> That's an easy one. I have "eno16780032". Awesome.
It is somehow related to network interfaces layout on motherboard.
This stupid default already 3
On 2015-02-11 19:54, Jan Stary wrote:
> On Feb 11 14:49:17, h...@barrera.io wrote:
> > Hi,
> >
> > I upgraded to -snapshot today, and did all the proper postgresql upgrade:
> > pg_dump, moved the old db out the the way, re-init'd, started, and
import.
> >
> > The thing is, upon receiving connection
On Wed, Feb 11, 2015 at 6:43 AM, Janne Johansson
wrote:
> You can invent how many journals and whatevers you like to hope to prevent
> the state from being inconsistent, but broken or breaking sectors will
> sooner or later force you to run over all files and read/check them, and
> in that case
>
On 02/11/15 11:58, Jan Stary wrote:
On Feb 10 17:48:22, na...@mips.inka.de wrote:
On 2015-02-10, yary wrote:
I know FFS2 can handle that size easily, but I'm worried about fsck
taking forever. This machine will have 1.5GB RAM, from what I've read
that's not enough memory to fsck a 4TB volume
First thanks for helping!
On Wed, Feb 11, 2015 at 09:29:04AM +0100, Alexandre Ratchov wrote:
> the noise might be caused by a noisy microphone amp (even if
> there's no microphone plugged). By mutting the microphoe, the noise
> may disappear. Could you post the output of "mixerctl -a" ?
Thanks, f
Hi,
I upgraded to -snapshot today, and did all the proper postgresql upgrade:
pg_dump, moved the old db out the the way, re-init'd, started, and import.
The thing is, upon receiving connections, postgres dies horribly. The log is
just this following iterating over and over:
WARNING: terminati
Thanks all for the tuning flags & the example. I'll take a look at the man
pages and file set. Doesn't look like the 4TB FFS2 will be a problem on
this machine after all.
On Feb 10 17:48:22, na...@mips.inka.de wrote:
> On 2015-02-10, yary wrote:
>
> > I know FFS2 can handle that size easily, but I'm worried about fsck
> > taking forever. This machine will have 1.5GB RAM, from what I've read
> > that's not enough memory to fsck a 4TB volume without painful
> > swap
On 2/10/15, Diana Eichert wrote:
> names to something more useful than "p3p2"!!!.
>
That's an easy one. I have "eno16780032". Awesome.
I try to stay away from as much of the Linux configuration as possible
and administer the applications. My contribution is running "yum
upgrade" every 3 days o
On Wed, Feb 11, 2015 at 1:40 PM, Giancarlo Razzolini
wrote:
> I don't know if you know this, but just put net.ifnames=0 in your
> kernel's parameters and it will revert to the old way.
As usual with linux, every new enhancement or modification is always
accompanied by a knob to fully annihilate
2015-02-10 17:44 GMT+01:00 yary :
> I know FFS2 can handle that size easily, but I'm worried about fsck
> taking forever. This machine will have 1.5GB RAM, from what I've read
> that's not enough memory to fsck a 4TB volume without painful
> swapping. Is there some filesystem-plus-options for rece
Oh yeah, systemd. The new and improved init replacement.
It sure looks less complex,
http://en.wikipedia.org/wiki/Systemd#mediaviewer/File:Systemd_components.svg
Yeah, I know about net.ifnames=0, but that just gets you back
to the ethX paradigm. So very "helpful" in a very generic
way. What ab
> >Both works with OpenBSD 5.4.
>
> Ok, I've remembered ACPI and given it a try to disable in UKC.
> Now, the stuff works. :-)
But now you're depriving us of the means to help you.
Please send a 5.4 dmesg if you still have it, and 5.6 dmesgs with and
without acpi disabled, as well as `acpidump'
On 10-02-2015 22:26, Diana Eichert wrote:
> My day job entails a lot of Linux support, lately I've been
> dealing with the big screwup associated with network interface
> naming. WHY can't Linux follow BSD's straightforward NIC
> naming?
This answer is a simple one: systemd
> It's positively bizar
Wave.. Thanks Diana.
I still owe you a beer or thirteen.
On Tue, Feb 10, 2015 at 5:26 PM, Diana Eichert wrote:
> I don't post much any more, my OpenBSD systems "just work".
>
> Just wanted to post a thank you to OpenBSD because it does
> "just work".
>
> My day job entails a lot of Linux support
Am 2015-02-11 12:25, schrieb Markus Kolb:
Hello,
what is your policy for legacy hardware?
I'd like to reactivate an old laptop for special purpose with OpenBSD.
But I've problems to run supported releases on it.
The latest working version is OpenBSD 5.4.
Since 5.5 you can read in dmesg (dmesg.b
On Tue, Feb 10, 2015 at 11:35:32PM +0100, Jan Stary wrote:
> On Feb 10 17:48:22, na...@mips.inka.de wrote:
> > On 2015-02-10, yary wrote:
> >
> > > I know FFS2 can handle that size easily, but I'm worried about fsck
> > > taking forever. This machine will have 1.5GB RAM, from what I've read
> >
Hello,
what is your policy for legacy hardware?
I'd like to reactivate an old laptop for special purpose with OpenBSD.
But I've problems to run supported releases on it.
The latest working version is OpenBSD 5.4.
Since 5.5 you can read in dmesg (dmesg.boot is attached):
cbb0 at pci0 dev 4 functio
On Wed, Feb 11, 2015 at 02:27:32AM -0200, Henrique Lengler wrote:
>
> Hi,
>
> I'm new in OpenBSD (I'm loving it), I came from Linux. I installed the
> last (5.6) version, and I started to use, without doing any change in
>
19 matches
Mail list logo
