From: Dale <dalek1967@bellsouth.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] (OT) Reboot to Windows (using grub)
Date: Sun, 10 Feb 2008 00:22:27 -0600 [thread overview]
Message-ID: <47AE9823.3090108@bellsouth.net> (raw)
In-Reply-To: <alpine.LNX.1.00.0802092115150.13593@iabervon.org>
Daniel Barkalow wrote:
> On Sat, 9 Feb 2008, Dale wrote:
>
>
>> Peter Humphrey wrote:
>>
>>> On Saturday 09 February 2008 04:35:35 Daniel Barkalow wrote:
>>>
>>>
>>>
>>>> *This .sig left intentionally blank*
>>>>
>>>>
>>> It did? Where did it leave for?
>>>
>>>
>>>
>> That reminds me of the pages in the IBM service manuals. They would put
>> that on the "blank" pages. My questions was always this: If it has
>> that on it, is it blank? :/
>>
>
> In fact, my .sig is entirely blank. I just always type the same thing by
> hand after writing every email, and have been doing so for long enough to
> forget if there was actually a good reason to do so originally. There may
> have also been a good reason I didn't make it "*This .sig intentionally
> left blank*", which would match the word order of the IBM manuals (and the
> door in Zork).
>
> The IBM manuals actually had a good reason. I think it was that they were
> in loose-leaf binders so they could mail people new versions of individual
> chapters, and each chapter was therefore on pieces of paper that weren't
> shared with any other chapter (this also required page numbers like 6-15).
> This meant that if a chapter ended on a right-hand page, the other side of
> the paper couldn't have anything on it. But if it were actually blank,
> people would worry that it was a misprint (if two sheets stuck together in
> the printer and then came unstuck before shipping, this could happen). So
> they wanted to print something innocuous on that side.
>
> -Daniel
> *This .sig left intentionally blank*
>
This is funny, I used to put the IBM manuals together in my spare time.
LOL That was how they did it too. You get a new fresh one and they
just updated the pages that were changed. I used to also try to figure
out what was changed. Saw a couple that had typos. Most of the time it
was a serious change. I guess they made changes to the boards so that
led to the manual being changed too.
I also worked in a print shop. So yea, the pages can stick together
sometimes. I've had it happen to me a few times. Humidity in the south
makes them sticky.
Memories. . . . .
Dale
:-) :-) :-)
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-10 6:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 12:57 [gentoo-user] (OT) Reboot to Windows (using grub) Liviu Andronic
2008-02-02 13:11 ` Stroller
2008-02-02 13:41 ` Etaoin Shrdlu
2008-02-02 13:19 ` Mrugesh Karnik
2008-02-02 13:24 ` Alex Schuster
2008-02-02 22:44 ` Liviu Andronic
2008-02-03 15:20 ` Dan Farrell
2008-02-04 17:10 ` Mrugesh Karnik
2008-02-05 13:03 ` Neil Bothwick
2008-02-05 13:27 ` Arturo 'Buanzo' Busleiman
2008-02-05 13:34 ` Neil Bothwick
2008-02-08 19:14 ` Dan Farrell
2008-02-08 21:49 ` Dale
2008-02-08 22:20 ` Alan McKinnon
2008-02-09 4:35 ` Daniel Barkalow
2008-02-09 9:59 ` Peter Humphrey
2008-02-09 10:46 ` Dale
2008-02-09 21:33 ` Dan Farrell
2008-02-10 2:28 ` Daniel Barkalow
2008-02-10 6:22 ` Dale [this message]
2008-02-10 11:04 ` Peter Humphrey
2008-02-08 22:49 ` Neil Bothwick
2008-02-09 9:18 ` Liviu Andronic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47AE9823.3090108@bellsouth.net \
--to=dalek1967@bellsouth.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox