Am 24.02.2015 um 03:14 schrieb Canek Peláez Valdés:
> Stefan, if you already have systemd (which I believe you do), why don't you
> compile in the support for microhttpd and use the journal? This is the
> exact scenario for which systemd-journal-gatewayd[1] was written.
very good ... enabled it o
> On Feb 24, 2015, at 2:50, Peter Humphrey wrote:
>
> Thank Goodness! Someone who knows enough to trim out the bits of the
> message he's not replying to.
>
> Why do you others make me page-down eight times to find what you've
> written in reply to the last three lines of the preceding message
I would always recommend a secure erase of an SSD - if you want a "fresh
start". That will mark all the NAND cells as clear of data. That will
benefit the longevity of your device / wear levelling.
I've been messing about with native exfat over the past few months. I found
this to be a pretty dece
On Tue, Feb 24, 2015 at 4:50 AM, Stefan G. Weichinger wrote:
> Am 24.02.2015 um 03:14 schrieb Canek Peláez Valdés:
>
>> Stefan, if you already have systemd (which I believe you do), why don't you
>> compile in the support for microhttpd and use the journal? This is the
>> exact scenario for which
On Tue, Feb 24, 2015 at 6:54 AM, Bob Wya wrote:
> I would always recommend a secure erase of an SSD - if you want a "fresh
> start". That will mark all the NAND cells as clear of data. That will
> benefit the longevity of your device / wear levelling.
Not a bad idea, though if you're trimming you
* Rich Freeman [150224 07:32]:
> On Tue, Feb 24, 2015 at 6:54 AM, Bob Wya wrote:
> > I would always recommend a secure erase of an SSD - if you want a "fresh
> > start". That will mark all the NAND cells as clear of data. That will
> > benefit the longevity of your device / wear levelling.
>
> N
I just saw this today:
> [20] hardened/linux/amd64/no-emul-linux-x86
> [21] hardened/linux/amd64/selinux
> [22] hardened/linux/amd64/no-multilib
> [23] hardened/linux/amd64/no-multilib/selinux
> [24] hardened/linux/amd64/x32
but I don't understand the difference between 20 and 24. I
On 02/24/2015 03:53 PM, Douglas J Hunley wrote:
> I just saw this today:
>> [20] hardened/linux/amd64/no-emul-linux-x86 [21]
>> hardened/linux/amd64/selinux [22]
>> hardened/linux/amd64/no-multilib [23]
>> hardened/linux/amd64/no-multilib/selinux [24]
>> hardened/linux/amd64/x32
>
> but I don't u
On Tuesday 24 February 2015 07:31:26 Rich Freeman wrote:
> In general though there is a reason that sysadmins tend to be very
> conservative with filesystems. I doubt most even jumped onto ext4 all
> that quickly even though that was very stable from the start of being
> declared as such. You re
On Tue, Feb 24, 2015 at 8:11 AM, Todd Goodman wrote:
>
> Can you explain why a log-based filesystem like f2fs would have any
> impact on wear leveling?
>
> As I understand it, wear leveling (and bad block replacement) occurs on
> the SSD itself (in the Flash Translation Layer probably.)
>
Well, i
On 24.02.2015 13:14, Rich Freeman wrote:
> I suspect this is trivial - it looks like something like this would work:
> http://.../entries?_SYSTEMD_UNIT=postfix.service
Yes, correct, as I thought this is the easy part.
Works:
http://mythtv.local:19531/entries?_SYSTEMD_UNIT=postfix.service
(usin
On Tue, Feb 24, 2015 at 10:33 AM, Stefan G. Weichinger
wrote:
[ ... ]
> Maybe I could set up some other web-app that (a) looks at the link
> pointing to the postfix.service-logs and (b) filters them?
(With my programmer's hat on): I think the easiest way would be to create a
little client that do
On Tue, Feb 24, 2015 at 10:33 AM, Stefan G. Weichinger wrote:
> Maybe I could set up some other web-app that (a) looks at the link
> pointing to the postfix.service-logs and (b) filters them?
>
> I could post to the systemd-devel-ml ... btw ;-)
>
Seems like there should be a systemd-users mailing
* Rich Freeman [150224 10:19]:
> On Tue, Feb 24, 2015 at 8:11 AM, Todd Goodman wrote:
> >
> > Can you explain why a log-based filesystem like f2fs would have any
> > impact on wear leveling?
> >
> > As I understand it, wear leveling (and bad block replacement) occurs on
> > the SSD itself (in the
On Sun, 22 February 2015, at 11:48 pm, lee wrote:
>
I believe this may be bug 406623.
https://bugs.gentoo.org/show_bug.cgi?id=406623
>>>
>>> That's almost three years old and should apparently be fixed?
>>
>> It's only been closed in the last few weeks.
>
> Still I wonder why
On Tue, Feb 24, 2015 at 11:31 AM, Todd Goodman wrote:
>
> But the device is still doing wear leveling and bad block
> replacement so you're beholden to those algorithms and what you think
> you're allocating as sequential blocks of the flash are not necessarily so.
>
> Of course any decent wear le
On 24.02.2015 17:01, Rich Freeman wrote:
> Seems like there should be a systemd-users mailing list, actually.
> This sort of situation is completely distro-agnostic.
Yes! And systemd-devel ml is always kind of "they will laugh at me and
say ugly things!" ;-)
> You certainly could design such an
On Tue, Feb 24, 2015 at 3:27 PM, Stefan G. Weichinger wrote:
> On 24.02.2015 17:01, Rich Freeman wrote:
>
>> Seems like there should be a systemd-users mailing list, actually.
>> This sort of situation is completely distro-agnostic.
>
> Yes! And systemd-devel ml is always kind of "they will laugh
ordered myself a new and shiny ssd last week.
one thinkpad still had that 60GB OCZ Vertex3 and that was a bit tight
now and then.
So I ordered a Samsung SSD 850 EVO 500GB for my desktop and planned to
move the former 840 EVO 250GB to the thinkpad.
Done today.
Moving was rather *boring* ->
par
On Tue, Feb 24, 2015 at 1:43 AM, Mick wrote:
> On Monday 23 Feb 2015 08:39:42 Walter Dnes wrote:
>>
>> Looks like it's time to play around with the "ip" command and try to
>> duplicate my current setup. Does anyone have a multi-route setup
>> similar to mine configured with iproute2? The net.exa
On Tue, Feb 24, 2015 at 06:43:19AM +, Mick wrote
> PS. Did you look at setting your desired subnet rather than a local-link
> auto-configured address at your HDHomerun device?
Not yet. I'm still cleaning up some odds-n-ends of my "simple upgrade"
from 32-bit to 64-bit mode. Also, as a m
Super obvious question... but can you enable AHCI mode for your SATA
Controller - in the BIOS.
Are you using HP supplied SATA cables - because these may be sucky crap. If
so I would try replacing them - especially if they don't have latches on
the plugs.
I think this is the specification for your
22 matches
Mail list logo
