Peter Humphrey wrote:
> On Friday, 21 December 2018 13:08:20 GMT Dale wrote:
>> Neil Bothwick wrote:
>>> On Fri, 21 Dec 2018 08:28:25 +, J. Roeleveld wrote:
Considering that they, like all SSDs have a limited write cycle, I only
use mine for the compiled software. I still use a tmpfs
On Friday, 21 December 2018 13:08:20 GMT Dale wrote:
> Neil Bothwick wrote:
> > On Fri, 21 Dec 2018 08:28:25 +, J. Roeleveld wrote:
> >> Considering that they, like all SSDs have a limited write cycle, I only
> >> use mine for the compiled software. I still use a tmpfs for compiling.
> >
> >
Neil Bothwick wrote:
> On Fri, 21 Dec 2018 08:28:25 +, J. Roeleveld wrote:
>
>> Considering that they, like all SSDs have a limited write cycle, I only
>> use mine for the compiled software. I still use a tmpfs for compiling.
> Modern SSDs should outlive a hard drive, and have done so here.
>
On Fri, 21 Dec 2018 08:28:25 +, J. Roeleveld wrote:
> Considering that they, like all SSDs have a limited write cycle, I only
> use mine for the compiled software. I still use a tmpfs for compiling.
Modern SSDs should outlive a hard drive, and have done so here.
--
Neil Bothwick
Pound
On Fri, 21 Dec 2018 09:22:23 +, Peter Humphrey wrote:
> I want to fit a couple of ordinary SSDs as well, but I'm snookered by -
> countersunk mounting screws! The ones I have stand about 1mm proud,
> which is enough to stop the housing sliding home. I know - I should
> make the effort to
J. Roeleveld wrote:
> On December 21, 2018 12:27:28 AM UTC, Dale wrote:
>
> Dale wrote:
>> J. Roeleveld wrote:
>>> On December 20, 2018 11:45:29 AM UTC, Dale
>>> wrote:
>>>
>>> Peter Humphrey wrote:
>>>
>>>
>>>
>>> Next upgrade idea:
>>> - mainboard with NVME slot
On Friday, 21 December 2018 08:28:25 GMT J. Roeleveld wrote:
> Considering that they, like all SSDs have a limited write cycle, I only use
> mine for the compiled software. I still use a tmpfs for compiling.
This box has a Samsung SM951 256GB NVMe drive, and it's 21 months old. It runs
BOINC
On December 21, 2018 12:27:28 AM UTC, Dale wrote:
>Dale wrote:
>> J. Roeleveld wrote:
>>> On December 20, 2018 11:45:29 AM UTC, Dale
>wrote:
>>>
>>> Peter Humphrey wrote:
>>>
>>>
>>>
>>> Next upgrade idea:
>>> - mainboard with NVME slot
>>> - NVME drive for your OS.
>>>
>>> Your CPU and
Dale wrote:
> J. Roeleveld wrote:
>> On December 20, 2018 11:45:29 AM UTC, Dale wrote:
>>
>> Peter Humphrey wrote:
>>
>>
>>
>> Next upgrade idea:
>> - mainboard with NVME slot
>> - NVME drive for your OS.
>>
>> Your CPU and memory will be the next bottleneck :)
>>
>>
>> --
>> Sent from my
J. Roeleveld wrote:
> On December 20, 2018 11:45:29 AM UTC, Dale wrote:
>
> Peter Humphrey wrote:
>
> On Thursday, 20 December 2018 08:12:43 GMT Dale wrote:
>
> Thanks for the help. When I boot next time, maybe it will
> log the error and I can see what is
On December 20, 2018 11:45:29 AM UTC, Dale wrote:
>Peter Humphrey wrote:
>> On Thursday, 20 December 2018 08:12:43 GMT Dale wrote:
>>
>>> Thanks for the help. When I boot next time, maybe it will log the
>error
>>> and I can see what is going on.
>> You could also try CTRL-S to pause the screen
Peter Humphrey wrote:
> On Thursday, 20 December 2018 08:12:43 GMT Dale wrote:
>
>> Thanks for the help. When I boot next time, maybe it will log the error
>> and I can see what is going on.
> You could also try CTRL-S to pause the screen update and CTRL-Q to let it
> continue.
>
I did try
On Thursday, December 20, 2018 9:12:43 AM CET Dale wrote:
> J. Roeleveld wrote:
> > On December 20, 2018 4:41:26 AM UTC, Dale wrote:
> > Howdy,
> >
> > I just installed a new video card. After a couple weeks of USPS
> > dragging it around, it finally came in. Anyway, I got it
On Thursday, December 20, 2018 11:04:55 AM CET Peter Humphrey wrote:
> On Thursday, 20 December 2018 08:12:43 GMT Dale wrote:
> > Thanks for the help. When I boot next time, maybe it will log the error
> > and I can see what is going on.
>
> You could also try CTRL-S to pause the screen update
On Thursday, 20 December 2018 08:12:43 GMT Dale wrote:
> Thanks for the help. When I boot next time, maybe it will log the error
> and I can see what is going on.
You could also try CTRL-S to pause the screen update and CTRL-Q to let it
continue.
--
Regards,
Peter.
J. Roeleveld wrote:
> On December 20, 2018 4:41:26 AM UTC, Dale wrote:
>
> Howdy,
>
> I just installed a new video card. After a couple weeks of USPS
> dragging it around, it finally came in. Anyway, I got it installed and
> was booting up. I noticed somewhere between the
On December 20, 2018 4:41:26 AM UTC, Dale wrote:
>Howdy,
>
>I just installed a new video card. After a couple weeks of USPS
>dragging it around, it finally came in. Anyway, I got it installed and
>was booting up. I noticed somewhere between the kernel part and it
>going through the runlevel
Howdy,
I just installed a new video card. After a couple weeks of USPS
dragging it around, it finally came in. Anyway, I got it installed and
was booting up. I noticed somewhere between the kernel part and it
going through the runlevel part, there was something that failed. I saw
a little red
18 matches
Mail list logo