Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.electronics.design > #453200
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Newsgroups | sci.electronics.design |
| Subject | Re: big drives |
| Date | 2017-03-22 22:50 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <oavni1$6d0$1@dont-email.me> (permalink) |
| References | (2 earlier) <ppadncEiOrmhc0_FnZ2dnUU7-Y2dnZ2d@giganews.com> <oav0jt$m1m$1@dont-email.me> <m536dcl3u2tkkrd6qv5mnu534bpim00uqb@4ax.com> <oav6et$5nr$1@dont-email.me> <slh6dctp51cj813bmi4lqrvlu8pqr7qqfo@4ax.com> |
On 3/22/2017 9:00 PM, John Larkin wrote: > On Wed, 22 Mar 2017 17:58:45 -0700, Don Y > <blockedofcourse@foo.invalid> wrote: > >> On 3/22/2017 4:50 PM, John Larkin wrote: >>> On Wed, 22 Mar 2017 16:19:01 -0700, Don Y >>> <blockedofcourse@foo.invalid> wrote: >>> >>>> On 3/22/2017 2:37 PM, Jon Elson wrote: >>>>> tabbypurr@gmail.com wrote: >>>>> >>>>>> On Tuesday, 21 March 2017 17:21:23 UTC, John Larkin wrote: >>>>>>> I just happened to open my recycle bin and there was 42 Gbytes of >>>>>>> junk. >>>>>>> >>>>>>> I remember 256 Kbyte hard drives. A PC with a 10M drive was top-end. >>>>>>> >>>>>>> There's no point in reducing jpeg sizes, or even deleting stuff, any >>>>>>> more. I could never take enough pics, or create enough docs, to keep >>>>>>> up with the progress in hard drives. I suppose some people could >>>>>>> collect a large number of HD movies and use a terabyte somehow. >>>>>>> >>>>>>> It's impossible to crack one-time-pad encryption. Giant hard drives >>>>>>> and memory sticks make OTP files easy to physically hand off to >>>>>>> correspondents. >>>>>> >>>>>> I estimated the payback of deleting data some time last year. It came in >>>>>> at something like a penny or 2 an hour. >>>>> Well, the problem is I want physical, off-line backup of important stuff >>>>> (that's what I've created, not the OS, utilities, etc.) preferably located >>>>> in a couple places. So, getting rid of excess junk and redundant on-line >>>>> backups makes some sense, in thaty it makes those CDs, then DVDs, now Blu- >>>>> Ray backups fit on available media. >>>> >>>> I've hacked together a "system" (not a "device") whereby I track "files" >>>> (for want of a better term as it can mean finer grained things, as well) >>>> and their "locations" (volume, directory/container, etc.) in a relational >>>> database tagged with appropriate metadata (whatever *I* deem important >>>> so I can add notes like "this is a list of important telephone numbers") >>>> including a hash of the object's content. >>> >>> I always thought that any file system ought to have a notes field in >>> each file header block. Like "what is this?" >>> >>> I see so many files - Spice, schematics, READMEs, tech notes, pics, >>> source code - that has zero context. No author, no date, no rev ID, no >>> statement of WTF this IS. >> >> It goes far beyond just adding "comments". >> >> Once you have a "catalog" (database) of all your files, you can assign them >> unique identifiers (the RDBMS does it *for* you). And, you can then exploit >> the relational capabilities of the RDBMS to create *new* "catalogs"/collections >> based on whatever YOU think to be appropriate! >> >> So, I can note that objects 23, 3049, 345345, 5563, 456456, 30302221 are >> "songs". And, that songs have attributes like "artist", "duration", "genre", >> etc. I can then build a catalog (table) of "songs" wherein the first >> "column" is an "object identifier" -- that links directly to the OID in the >> "main FILE catalog". The other "columns" can be whatever I deem appropriate >> FOR SONGS! (it would be silly to add a "duration" column to the main file >> catalog as a file that isn't a song wouldn't have any notion of "duration"!) >> >> Files that happen to be photographs (e.g., 48846, 858473, 99223 and 7483002) >> can be *referenced* in a "photographs" catalog (table) -- accompanied by >> attributes (columns) like "date taken", "dimensions", "location", "camera", >> etc. >> >> Artwork for circuit boards can be collected in another table that carries >> annotations (attributes) for the associated "schematic" file, BoM file, >> revision, etc. >> >> I now more aggressively document the evolution of my designs by leveraging this >> ability; I can retrieve earlier versions of code/schematics/layouts and see >> what I found lacking in each. >> >> Etc. >> >> [E.g., my baking/cooking recipes are all cataloged. There are many versions >> of each of them. Some have simple annotations: "This is the style that Joe >> likes!" or "No tomato products for D&J!". Others are more cryptic/technical: >> "This builds on the XYZ version but replaces the baking powder with soda and >> tartar" (many of my recipes are in a CONSTANT state of flux -- e.g., my >> biscotti Rx probably exists in more than 100 variations!). This lets me see >> what I've tried in the past as well as what I found "lacking" in it: "This is >> the *BEST* version but it is considerably more involved to produce; use only if >> you are really after a primo result!"] >> >> So, you can access the catalog that is of most interest to you and use *it* >> to give you handles on the appropriate information (attributes) that you >> can then chase down to find the file(s) of interest in the archive. >> >> "Show me all artwork for project FOO..." >> "Show me all songs by artist BAZ..." >> "Show me the oldest revision of the specification for BLAH..." >> >> [Searching free-form comments is tedious and usually ineffective. It >> requires a lot of discipline in the way that you describe things *or* >> a lot of smarts in your search engine (e.g., are "project FOO", "proj FOO" >> and "FOO" all suitable matches for the first of these examples above? >> What if "FOO" was "APPLE"? Would it conflict with a comment describing a >> photograph of an *apple*?)] > > What happens when you email a file to someone else? Or put together a > separate project folder, like to a contract manufacturer or a > consultant? You can't include the database. Will that contract manufacturer be able to recognize your "augmented" file system? That's why you include a MANIFEST file in any package of electronic objects. There's no portable way to examine files of varying formats for "comments" embedded within. How do you examine the revision, date, author, etc. of a photograph? Of an AutoCAD 3D model? Of a DSO capture? etc. [I.e., you require specialty "viewers" for each of those file types/formats.] > I include the basics in every possible file; title, author, rev, date, > description, maybe a scope/introduction if that makes sense. Often a > rev history. > > Databases too often become toys. And lots of people absolutely hate > comments. Do you have a database that tracks part numbers, quantities, stock room locations, "where used", etc.? Is *it* a toy?? People hate *creating* comments -- often because they need some form of guidance as to WHAT it should "include", the form it should take, etc. The advantage of adding tags (attributes) to a table in a database is that the "fields" that are important (as defined by whomever created the table for that type of file object) have already been defined. It becomes a fill-in-the-blank exercise. Much more than "add some comment to this file"
Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-21 10:21 -0700
Re: big drives bitrex <bitrex@de.lete.earthlink.net> - 2017-03-21 13:47 -0400
Re: big drives George Herold <gherold@teachspin.com> - 2017-03-21 12:42 -0700
Re: big drives dagmargoodboat@yahoo.com - 2017-03-21 12:55 -0700
Re: big drives George Herold <gherold@teachspin.com> - 2017-03-21 13:37 -0700
Re: big drives bill.sloman@ieee.org - 2017-03-21 21:51 -0700
Re: big drives George Herold <gherold@teachspin.com> - 2017-03-22 07:26 -0700
Re: big drives Winfield Hill <hill@rowland.harvard.edu> - 2017-03-22 03:38 -0700
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-22 14:23 +0000
Re: big drives David Brown <david.brown@hesbynett.no> - 2017-03-22 16:43 +0100
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-22 18:35 +0000
Re: big drives David Brown <david.brown@hesbynett.no> - 2017-03-23 10:24 +0100
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-23 16:11 +0000
Re: big drives krw@notreal.com - 2017-03-23 13:05 -0400
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-23 17:39 +0000
Re: big drives krw@notreal.com - 2017-03-23 21:05 -0400
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-24 03:01 +0000
Re: big drives krw@notreal.com - 2017-03-23 23:09 -0400
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-24 04:15 +0000
Re: big drives krw@notreal.com - 2017-03-24 22:34 -0400
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 12:25 -0700
Re: big drives dplatt@coop.radagast.org (Dave Platt) - 2017-03-22 13:57 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 16:03 -0700
Re: big drives krw@notreal.com - 2017-03-22 20:29 -0400
Re: big drives tabbypurr@gmail.com - 2017-03-22 04:36 -0700
Re: big drives Spehro Pefhany <speffSNIP@interlogDOTyou.knowwhat> - 2017-03-22 08:57 -0400
Re: big drives Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2017-03-22 11:59 -0400
Re: big drives krw@notreal.com - 2017-03-22 13:23 -0400
Re: big drives Jon Elson <jmelson@wustl.edu> - 2017-03-22 16:38 -0500
Re: big drives krw@notreal.com - 2017-03-22 20:31 -0400
Re: big drives gray_wolf <g_wolf@nospam.com> - 2017-03-23 20:59 -0500
Re: big drives gray_wolf <g_wolf@nospam.com> - 2017-03-23 21:00 -0500
Re: big drives Robert Baer <robertbaer@localnet.com> - 2017-03-23 22:21 -0800
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-22 07:51 -0700
Re: big drives krw@notreal.com - 2017-03-22 13:23 -0400
Re: big drives Robert Baer <robertbaer@localnet.com> - 2017-03-23 22:19 -0800
Re: big drives tabbypurr@gmail.com - 2017-03-24 04:26 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 08:38 -0700
Re: big drives Jon Elson <jmelson@wustl.edu> - 2017-03-22 16:37 -0500
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-22 16:07 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 16:21 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-22 16:45 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 23:21 -0700
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 13:06 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 16:56 -0700
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 17:35 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 21:47 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 16:19 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-22 16:50 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 17:58 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-22 21:00 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 22:50 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-23 08:27 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 12:25 -0700
Re: big drives tabbypurr@gmail.com - 2017-03-24 04:31 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 06:38 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 08:41 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 11:38 -0700
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 13:55 -0700
Re: big drives tabbypurr@gmail.com - 2017-03-24 17:14 -0700
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 17:41 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 18:00 -0700
Re: big drives Joerg <news@analogconsultants.com> - 2017-03-23 09:35 -0700
Re: big drives "Michael A. Terrell" <mike.terrell@earthlink.net> - 2017-03-23 18:38 -0400
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 16:18 -0700
Re: big drives Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2017-03-23 18:29 -0400
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 18:38 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 18:54 -0700
Re: big drives pcdhobbs@gmail.com - 2017-03-23 19:16 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 19:28 -0700
Re: big drives pcdhobbs@gmail.com - 2017-03-23 19:55 -0700
Re: big drives krw@notreal.com - 2017-03-23 23:04 -0400
Re: big drives pcdhobbs@gmail.com - 2017-03-23 22:00 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 08:46 -0700
Re: big drives krw@notreal.com - 2017-03-24 22:38 -0400
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 22:22 -0700
Re: big drives pcdhobbs@gmail.com - 2017-03-23 23:08 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 00:21 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 09:00 -0700
Re: big drives David Brown <david.brown@hesbynett.no> - 2017-03-24 17:14 +0100
Re: big drives tabbypurr@gmail.com - 2017-03-24 09:19 -0700
Re: big drives David Brown <david.brown@hesbynett.no> - 2017-03-24 17:47 +0100
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 12:01 -0700
Re: big drives Jasen Betts <jasen@xnet.co.nz> - 2017-03-24 20:30 +0000
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 14:06 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 11:55 -0700
Re: big drives "Michael A. Terrell" <mike.terrell@earthlink.net> - 2017-03-25 04:00 -0400
Re: big drives upsidedown@downunder.com - 2017-03-24 22:18 +0200
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 14:15 -0700
Re: big drives Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-03-25 13:21 +0200
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-25 07:54 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-25 10:53 -0700
Re: big drives upsidedown@downunder.com - 2017-03-25 23:11 +0200
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-25 15:14 -0700
Re: big drives upsidedown@downunder.com - 2017-03-26 12:18 +0300
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-26 03:33 -0700
Re: big drives Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2017-03-26 16:36 -0400
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-26 14:13 -0700
Re: big drives Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-03-25 21:04 +0200
Re: big drives pcdhobbs@gmail.com - 2017-03-24 19:03 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 08:53 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 12:12 -0700
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 14:20 -0700
Re: big drives krw@notreal.com - 2017-03-24 22:43 -0400
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 20:10 -0700
Re: big drives krw@notreal.com - 2017-03-24 23:23 -0400
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 22:25 -0700
Re: big drives Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-03-25 13:23 +0200
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-23 19:36 -0700
Re: big drives upsidedown@downunder.com - 2017-03-24 10:14 +0200
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 01:31 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-23 16:21 -0700
Re: big drives "Michael A. Terrell" <mike.terrell@earthlink.net> - 2017-03-24 08:54 -0400
csiph-web