On Sat, Jan 16, 2016 at 09:13:23AM -0800, Scott Czepiel wrote:
> On Fri, Jan 15, 2016 at 5:46 PM, Ken Moffat <[email protected]> wrote:
> > But people who
> > have been dipping in to LFS in more recent years have noted a lot of
> > changes, particularly since 7.0 where the bootscripts were changed.
> 
> I had actually not noticed but reviewing my notes I see that it was
> using BSD-style init back then.  Not that I would argue against Svs V,
> but I am curious to read about how/why the project made the change.
> Is there a link to a discussion (hopefully not flame war) on the list
> about it?
> 

I haven't attempted to look at changes in the detail of the
bootscripts between 2.4.3 and 3.0, but 3.0 definitely mentions
sysvinit in explaining how the bootscripts work, and a *very* quick
glance at 2.4.3 suggests little had changed in the actual scripts.

http://archive.linuxfromscratch.org/lfs-museum/

If there was indeed a change, I suppose there will probably be a
comment in the archives -

http://lists.linuxfromscratch.org/pipermail/lfs-dev/

> > I haven't run badblocks in years - can you remind me why you run it
> > on "spinning rust" but not on SSDs, please ?
> 
> SSDs use a "wear leveling" feature in the firmware to gradually
> distribute writes evenly across the NAND cells.  Since failure rate is
> pretty much a direct function of write cycles, the idea is to prevent
> one small set of cells from being over-written too many times.  That's
> why you can't actually specify a sector or block to write to on an SSD
> because the firmware intercepts the IO calls and decides where to map
> a logical IO address to a physical one.  SSDs are also typically
> over-provisioned, so that once cells start to fail, they can be marked
> as bad and re-mapped by the firmware.  So there's basically no point
> in looking for bad blocks, because the firmware will be handling that.
> And you can't even check all the blocks on an SSD because again, the
> over-provisioning hides a lot of extra cells from your view.  So in
> sum, running bad blocks on an SSD will just reduce your cells'
> expected life by one write cycle!
> 

Thanks - I've only ever run badblocks when I suspected a disk had
problems, and so far I haven't noticed any problems on my SSDs.

> > > 3) prime95 - run for a few hours and make sure nothing catches on fire!
> >
> > Is there a Live CD, for that ?  I've seen it mentioned in the usual
> > hardware sites, but only in the context of running under Windows.
> 
> There isn't a live CD, just a direct download from the website.  The
> source is available but the binary ought to run on an LSB compliant
> distro.

Thanks.

ĸen
-- 
This email was written using 100% recycled letters.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to