Mailing List Archive

   tlug.jp -> Mailing List -> tlug archive -> tlug Mailing List Archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[tlug] Re: Tlug Digest, Vol 28, Issue 49

UNSUBSCRIBE ME....is it so damn hard to do?




Bill


On Sat, 19 Apr 2008, tlug-request@example.com wrote:

Send Tlug mailing list submissions to
	tlug@example.com

To subscribe or unsubscribe via the World Wide Web, visit
	http://www.tlug.jp/mailman/listinfo/tlug
or, via email, send a message with subject or body 'help' to
	tlug-request@example.com

You can reach the person managing the list at
	tlug-owner@example.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tlug digest..."


Today's Topics:

  1. Re: OT: DC Power Transmission can be more efficient (jep200404)
  2. Re: OOwriter vertical glyph problem with Hiragino fonts
     (Gernot Hassenpflug)
  3. OT:  Putting "intellectual" into "intellectual Property" (CL)
  4. Re: Ping vs www server (Stephen J. Turnbull)
  5. Re: Kernel panic (Stephen J. Turnbull)
  6. Re: Kernel panic (SL Baur)


----------------------------------------------------------------------

Message: 1
Date: Fri, 18 Apr 2008 18:19:23 -0400
From: jep200404 <jep200404@example.com>
Subject: Re: [tlug] OT: DC Power Transmission can be more efficient
To: Tokyo Linux Users Group <tlug@example.com>
Message-ID: <20080418181923.55055489.jep200404@example.com>
Content-Type: text/plain; charset=US-ASCII

"SL Baur" wrote:

DC power transmission has always been lossier and thus more
expensive to deliver than AC.


Things have changed.

Where the lines are long, now DC tranmission lines are often more
efficient and practical that AC ones.

  http://en.wikipedia.org/wiki/High-voltage_direct_current#Advantages_of_HVDC_over_AC_transmission
  http://en.wikipedia.org/wiki/List_of_HVDC_projects

By the way, there can be reasons other than efficiency for using
DC power tranmission. DC can be used to bridge unsynchronized
AC systems, such as between Japan's 50 Hz and 60 Hz AC systems.

---

I remember when computers had big honkin' power supplies
with a big (possibly ferro-resonant) transformer, big diodes,
big capacitors, and big heat sinks on linear regulators.
They were big, heavy, and inefficient. Switching power supplies
were uncommon. The closest most folks got to switchers was the
vibrator thing for tube radios in cars.

Now, the vast majority of computers (including those running
Linux) have switching power supplies. Laptops usually have
several (switching) DC to DC converters inside.
Even many wall warts have switching power supplies now.

Of course the same technology behind the switching power
supplies, is scaled up for DC power transmission.

Nonetheless, I tip my hat to Tesla.




------------------------------

Message: 2
Date: Sat, 19 Apr 2008 08:05:43 +0900
From: "Gernot Hassenpflug" <aikishugyo@example.com>
Subject: Re: [tlug] OOwriter vertical glyph problem with Hiragino
	fonts
To: "Tokyo Linux Users Group" <tlug@example.com>
Message-ID:
	<4fefd6340804181605y5b3eeecco21a3be578bc0d13b@example.com>
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Apr 19, 2008 at 5:34 AM, Stephen J. Turnbull <stephen@example.com> wrote: 
Gernot Hassenpflug writes:

 > Can anyone replicate this? I have heard that there are bugs in the HG
 > fonts, but I hope that OOWriter would be able to work with them anyway
 > (as MS Word does).

 I can't speak for upstream, but NeoOffice is completely unable to
 handle fonts as Word does.  Almost all Word documents I have to read
 in NOo (how apropos, as in "Just say ~") are broken with respect to
 kerning and justification.  This is very likely due to substitution of
 Hiragino fonts (standard on the Mac) for pretty much everything else.


Oh dear. That is a very sad situation. I'll try to post my query on a
Japanese OO forum later today and see what transpires.



------------------------------

Message: 3
Date: Sat, 19 Apr 2008 09:50:58 +0900
From: CL <az.4tlug@example.com>
Subject: [tlug] OT:  Putting "intellectual" into "intellectual
	Property"
To: Tokyo Linux Users Group <tlug@example.com>
Message-ID: <480941F2.6080004@example.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Received this in private mail from a lawyer I do research work for.  I
found it fascinating.  Follow the links at the bottom of the page for
additional background.

CL

=-=-=-=-=-=-=-=-=-=

This is QUITE the giggle.

Monster sent Blue Jeans a cease and desist letter. I doubt they knew
that the head of Blue Jeans Cable was a lawyer.  Likely mistake number one.

<http://www.audioholics.com/news/industry-news/blue-jeans-strikes-back>

The letter starts "Let me begin by stating, without equivocation, that
I have no interest whatsoever in infringing upon any intellectual
property belonging to Monster Cable.  Indeed, the less my customers
think my products resemble Monster's, in form or in function, the
better."

Near the end is says "Not only am I unintimidated by litigation; I
sometimes rather miss it."

Interiorly, there appear to be a number of other mistakes or they had
the real junior lawyers in the firm, throw together the "usual"
boilerplate that has sufficient intimidation value.  Looks like they
really did not do their homework.  I wonder how man billable hours
were charged for it?  I wonder how many billable hours will be billed
in replying to the gauntlet.

It's a pretty good read.



------------------------------

Message: 4
Date: Sat, 19 Apr 2008 10:02:52 +0900
From: "Stephen J. Turnbull" <stephen@example.com>
Subject: Re: [tlug] Ping vs www server
To: Tokyo Linux Users Group <tlug@example.com>
Message-ID: <87abjqejwj.fsf@example.com>
Content-Type: text/plain; charset=us-ascii

Josh Glover writes:

> 2. Public servers should drop echo message types (0, IIRC) on the
> floor while dealing with the rest of ICMP

I don't get this.  Public servers can be pinged via TCP on at least
one port by definition.  "Echo" is a tiny part of the stack, and it's
way low (technically, ICMP is encapsulated in IP same as UDP or TCP,
but considered to be part of IP rather than a higher level, see RFC
1122).  If you don't trust this part of your stack, what can you
trust?

It's the other parts of ICMP that are hard.



------------------------------

Message: 5
Date: Sat, 19 Apr 2008 10:06:02 +0900
From: "Stephen J. Turnbull" <stephen@example.com>
Subject: Re: [tlug] Kernel panic
To: Tokyo Linux Users Group <tlug@example.com>
Message-ID: <878wzaejr9.fsf@example.com>
Content-Type: text/plain; charset=us-ascii

Attila Kinali writes:

> Err... The inability to understand the system one is working
> with is no excuse to give very dangerouse advices.
> Updates _are_absolutely_necessary_ to keep your system safe.

Eh?

First, neither the OP nor the people he is quoting are distinguishing
between *security updates* and *major system upgrades*, and the OP at
least is clearly in a context of the latter.  Those are actually
openly hazardous, since they typically introduce new functionality to
your system.

Second, security updates are merely a convenience in keeping your
system safe.  The only thing that can really keep a system safe is
operator vigilance.  I don't care how consistent you are about keeping
updated, you can't stay ahead of what the vendors don't know about yet.

> Otherwise you'll catch sooner or later a worm, or someone hacks
> into your system and misuses it for hacking other system or sending
> spam.

Do you have evidence for this claim?  If you don't run any network
services, you won't catch a worm for sure.  Trojans are a problem, but
no security update can prevent a user bent on executing a trojan from
doing so.  Linux viruses are legion, but I've not heard of any that
managed to propagate in the wild (I'm no expert, but you'd think it
would be pretty famous if it did happen).  As for getting hacked, I've
not heard of successful attacks on properly configured (ie, no access
by password) sshd, either.




------------------------------

Message: 6
Date: Fri, 18 Apr 2008 18:15:32 -0700
From: "SL Baur" <steve@example.com>
Subject: Re: [tlug] Kernel panic
To: "Tokyo Linux Users Group" <tlug@example.com>
Message-ID:
	<ed10ee420804181815n13f0fdc1jcb30705bd6c97756@example.com>
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Apr 18, 2008 at 6:06 PM, Stephen J. Turnbull <stephen@example.com> wrote: 
Attila Kinali writes:

 > Err... The inability to understand the system one is working
 > with is no excuse to give very dangerouse advices.
 > Updates _are_absolutely_necessary_ to keep your system safe.

 Eh?

 First, neither the OP nor the people he is quoting are distinguishing
 between *security updates* and *major system upgrades*, and the OP at
 least is clearly in a context of the latter.  Those are actually
 openly hazardous, since they typically introduce new functionality to
 your system.


Actually, any system upgrade to a critical component is potentially hazardous.
And it's actually a lot more dangerous when you have little idea of what you're
changing if it's all covered up by a dumbed down GUI.

An interesting factoid I saw on slashdot today was that the process of reverse
engineering an exploit based on a Microsoft security patch update has
apparently been automated.

 > Otherwise you'll catch sooner or later a worm, or someone hacks
 > into your system and misuses it for hacking other system or sending
 > spam.


Microsoft group think at its best.

 As for getting hacked, I've
 not heard of successful attacks on properly configured (ie, no access
 by password) sshd, either.


I recall one.  I'll try to dig up the details.  If I'm remembering
correctly it involved
a two-stage breakin.  First into a "less" heavily fortified network to
steal ssh private
keys from an admin and then second into the *heavily* fortified server
target.  This
was from around 2000 and there was a challenge involved.

-sb (First post!  from my finally WiFi enabled work Lenovo notebook)



------------------------------

--
To unsubscribe from this mailing list,
please see the instructions at http://www.tlug.jp/list.html

Please visit our sponsor at http://www.primustel.co.jp/tlug/

End of Tlug Digest, Vol 28, Issue 49
************************************


Home | Main Index | Thread Index

Home Page Mailing List Linux and Japan TLUG Members Links