dieresis
in [Design]
|
Prev: [Way OT] dieresis
Next: SPDIF to AES/EBU
From: Dorsai on 10 Mar 2010 23:28 On Thu, 11 Mar 2010 03:39:05 +0000, Przemek Klosowski wrote: > On Mon, 01 Mar 2010 14:58:07 -0700, D Yuniskis wrote: > >> But, then I started thinking about it more. In particular, the fact >> that I *only* use it in this word! And, have *never* used it in other >> places where it "should" be used. >> >> (of course, no one *still* uses it at all, so this is a moot point) > > Pardon me, New Yorker always adds dieresis (pre:existing, co:operate, > etc). I assume it's the New Yorker style guide, because the authors who > also publish elsewhere do not show this in their other work (e.g. > Malcolm Gladwell). Now if y'all could just move this to alt.anal-retentive, the newsgroup would be good again. -- ---------------------------------------------------------------- Dorsai - Author of Erotic Fiction http://www.asstr.org/~Dorsai Real happiness is when you marry a girl for love and find out later she has money.
From: D Yuniskis on 11 Mar 2010 10:53 Fred Abse wrote: > On Tue, 09 Mar 2010 20:48:34 -0800, JosephKK wrote: > >> I use parted as needed. Not so skillful with dd yet. "cp -R *" and the >> like serve me pretty well. > > cp -R * won't transfer the boot sector, partition table, etc. > > Just use "dd if=/dev/hda of=/dev/hdc" with the target drive on the second > IDE. Then go to bed. It'll be finished in the morning :-) bs= is often a worthwhile speedup. > Don't do it with mounted drives. Boot with a startup floppy or CD with a > copy of dd and parted on it. Don't worry about BIOS settings. Linux > doesn't use them for I/O. I've actually run a 40 gig HDD on a machine with > an 8 gig BIOS limit, (with a 1024 cylinder boot partition to fool it). Clonezilla is your friend. > You'll find all your original partitions recreated on your new drive, with > empty space left if it's bigger. It'll boot, too. > > Then use parted to stretch the created partition to the size of the new > (bigger) HDD. Go for breakfast whilst that's running. > > Thanks for the offer of the monitors. I have quite a few spare already.
From: D Yuniskis on 12 Mar 2010 18:20
Fred Abse wrote: > On Fri, 12 Mar 2010 14:58:03 -0700, D Yuniskis wrote: > >> <frown> I don't run Linux so keep that in mind... >> >> Can't you (or, *don't* you?) build slices *within* a "partition"? E.g., I >> can set up an x86 PC to use one of the (4) partitions for DOS, another for >> some variant of Windows a third for NetBSD 3.1 and the fourth for NetBSD >> 5.0. >> >> DOS and Windows are happy -- since they deal with "partitions". > > I don't run DOS or Windows. Strictly Microsoft-free zone here. Just Linux. Doesn't matter. I could make them all {Net,Open,Free}BSD "partitions"... >> Within each of the NetBSD partitions, I create many (4, 8, 10?) "slices" >> (think: partition : disk :: slice : partition) and each of those is >> (potentially) a filesystem mounted someplace in the (NetBSD) hierarchy. >> >> E.g., /, /var, /usr, /usr/local, /usr/pkg, /home ... > > I don't know anything about NetBSD filesystems. Linux fdisk will make > NetBSD partitions, but I don't know whether there's an mkfs for NetBSD. > > I used to have /usr and /home on a separate physical drive, once, when all > I had were smallish drives. I can't see any point in having lots of > separate partitions otherwise. My boot partition is a relic of the days of > BIOS that would only boot from the first 1024 cylinders. Having partitions is a double-edged sword. Put everything in / and if something corrupts that file system, you're hosed. OTOH, keep / small and effectively R/O, then you can be reasonably sure that you can mount it (single user) and, from there, troubleshoot problems you might have with other "not yet mounted" file systems. You can also treat them as different file systems (with different characteristics). (there's a long list of the "cans" as well as the "downsides") When I first started sysadm'ing UN*X boxes (before the free eunices came into being), I found partitions to be a PITA. Over time, my attitude has flipped 180 on this issue... |