breakthrough discovery in Cholesterol control - ave

[Healthwatch - xa]

FOR IMMEDIATE RELEASE:

March 23, 2005. Associates News

Flozar Heart Health News:

Breakthrough Natural Cholesterol Reduction System:
60% of people are at risk. are YOU?

No Dangerous side effects such as dizziness, nausea, yellow skin & more.

http://healthwatch.anationpickle.com/2fl2/ 

Try Flozar for 30 days - if you AND your physician are not amazed,
return for full refund.

westminster  depot  swarm 

- Sent to debian-devel@lists.debian.org based on previous subscrition request 
on Sat, 26 Mar 2005 04:21:46 -0100

to opt-out please click: www.wallaceentry.com/ach/  .

Sent by the HealthWatch network LTD
402 Berkshire Road
Bermuda, Bermuda, L2A4H0


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: NEW handling: About rejects, and kernels

[Andreas Barth]

* Henning Makholm ([EMAIL PROTECTED]) [050326 00:55]:
> Scripsit [EMAIL PROTECTED] (Marco d'Itri)
 
> > And one of the reasons for which licensing for documentation has not
> > been discussed is that most people were not aware of the scope of the
> > "editorial" changes, so there was no reason to discuss anything.
 
> You can keep repeating that lie from now to eternity; it will not
> cause it to become true.

Sorry, Henning, but actually only very few people realized that these
changes were intended to change ftp-masters behaviour.  And, if you
re-read the discussion after Anthonys announcement of the changes,
Marco is right here.


Cheers,
Andi
-- 
   http://home.arcor.de/andreas-barth/
   PGP 1024/89FB5CE5  DC F1 85 6D A6 45 9C 0F  3B BE F1 D0 C5 D1 D9 0C


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to pin certain packages from experimental?

[Marc Haber]

On Tue, 22 Mar 2005 02:21:39 +1100, [EMAIL PROTECTED] (Paul
Hampson) wrote:
>On Mon, Mar 21, 2005 at 12:36:52PM +0100, Marc Haber wrote:
>> On Mon, 21 Mar 2005 08:47:22 +0100, Adeodato Simó <[EMAIL PROTECTED]>
>> wrote:
>> >* Marc Haber [Mon, 21 Mar 2005 08:03:21 +0100]:
>> >> |  Version Table:
>> >> | 4.50-4 555
>> >> |500 http://debian.debian.zugschlus.de sid/main Packages
>> >> | *** 4.50-1 555
>> >> |100 /var/lib/dpkg/status
>> >> | 4.44-2 555
>> >> |500 http://debian.debian.zugschlus.de sarge/main Packages
>> >> |[2/[EMAIL PROTECTED]:~$   
>> >
>> >> available versions (4.44-2, 4.50-1 and 4.50-4) are pinned to priority
>> >> 555.
>
>> >> And I see that the pin is somewhat wrong, as the 555 pin should only
>> >> apply to packages available from the experimental distribution and not
>> >> to sarge and sid.
>
>> >  The priority of each version/location is the number at the left of it,
>> >  in this case, 500, 100, 500. Those numbers are correct.
>
>> So you're basically saying that my pin doesn't work at all?
>
>Well, the above output doesn't show a version in experimental...

When 4.50-1 was installed on the system in question. there was 4.50-1
in experimental. 4.50-2 went to unstable and thus 4.50-1 was
automatically removed from experimental.

>"How APT Interprets Priorities" in apt-preferences(5) seems to suggest
>that a '500' priority won't be upgraded automatically, that's the
>priority assigned to non-target distribution packages:

The previous 4.44 version on the system was updated to 4.50-1 from
experimental while the 500 pin was in place.

>"causes a version to be installed unless there is a version available
>belonging to some other distribution or the installed version is more
>recent"

4.50-4 is part of the target distribution, and there is no version
available belonging to some other distribution, and the installed
version is not more recent. Or does apt get confused by the 4.44-2
package available from sarge?

>Try setting sid (or sarge) as your target distribution, and 4.50-4
>should rise to 990, and be auto-upgraded. However, this means your
>experimental pin for this package is too low, and needs to be "990 < P
><=1000" to get the effect of "If there's a newer one in experimental,
>grab it".

Hm. What distribution does apt take as target distribution if none is
set in /etc/apt/apt.conf.d?

>> How got 4.50-1 installed then in the first place?
>
>That would depend on the policy state when it was instslled.

The policy was the same as listed above, pinning the distribution to
500.

>From what you said earlier, I'd guess that 4.50-1 was installed when it
>was in experimental, and the priority was therefore 500 < x <= 990,
>which means it'll be installed if there's no version belonging to the
>target release. And the above policy output shows there _is_ no target
>release set.

The priority was 500.

Shouldn't installation set a target release automatically? Why don't
I have a target release set?

>The upshot here (and the same lesson I learnt futzing with apt-pinning)
>is: Set a target release, or it won't do what you expect. ^_^

I see. I expected that to happen automatically.

>Or at the very least, (if for example you use other archives that
>also claim to be unstable, and you only want to fall back on them
>if Debian/unstable doesn't have what you need:)
>
>Package: *
>Pin: release o=Debian,a=Unstable,c=main
>Pin-Priority: 990
>
>Which is roughly the same as picking a target release, but doesn't
>give 990 to non-Debian archives marked Unstable.

I see.

Greetings
Marc

-- 
-- !! No courtesy copies, please !! -
Marc Haber |   " Questions are the | Mailadresse im Header
Mannheim, Germany  | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834

Re: Getting openswan 2.2.0 back into sarge

[Jamin W . Collins]

On Mar 24, 2005, at 2:39 AM, Rene Mayrhofer wrote:
Hi all,
[Please CC me in replies, I am currently not subscribed to this list.]
As some have already noticed, openswan has been removed from testing a 
while
ago, most probably because of bug #291274, which did not apply to 
package
version 2.2.0-4 (the one that has been removed from testing).
There are other problems with the 2.2.0 version such as #261892 which 
effectively cripples the network stack.

--
Jamin W. Collins
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: NEW handling: About rejects, and kernels (Was: Re: NEW handling ...)

[Marco d'Itri]

On Mar 25, Adam McKenna <[EMAIL PROTECTED]> wrote:

> No matter how you feel about the term "editorial changes", it seems to me
> that if these changes were really so bad, and the majority of the project is
> now against them, they should be easy enough to roll back.
Adam, meet Apathy.
Apathy, meet Adam.

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Re: NEW handling: About rejects, and kernels

[Henning Makholm]

Scripsit [EMAIL PROTECTED] (Marco d'Itri)

> And one of the reasons for which licensing for documentation has not
> been discussed is that most people were not aware of the scope of the
> "editorial" changes, so there was no reason to discuss anything.

You can keep repeating that lie from now to eternity; it will not
cause it to become true.

-- 
Henning Makholm  "Den nyttige hjemmedatamat er og forbliver en myte.
Generelt kan der ikke peges på databehandlingsopgaver af
  en sådan størrelsesorden og af en karaktér, som berettiger
  forestillingerne om den nye hjemme- og husholdningsteknologi."

Re: Let's stop feeding the NVidia cuckoo

[Henning Makholm]

Scripsit Paul Hedderly <[EMAIL PROTECTED]>
> On Thu, Mar 24, 2005 at 05:33:50PM +, Henning Makholm wrote:
>> Scripsit Paul Hedderly <[EMAIL PROTECTED]>

>> What you are showing here is that "code that can be compiled" is not a
>> working defintion of "source code".

> It not only works, but has been used for a long time.

No it hasn't. Nobody has ever claimed that, say, Bison output
qualifies as "source code" even though it is evidently compilable.

At least not until the recent influx of people who want to force
Debian to use a free-as-in-beer definition of freedom instead of
time-honored free-as-in-speech.

> What you are showing is that you have a dislike for source that is hard
> to modify (fair enough) and would like for it not to be called 'source
> code' if you feel it is hard to read/modify.

Strawman. Under that definition all code in a language that somebody
doesn't understand would cease to be source code either. That is
obviously not workable either.

> it literally means code that can be used to generate a binary.

No it doesn't.

-- 
Henning Makholm  "Ambiguous cases are defined as those for which the
   compiler being used finds a legitimate interpretation
   which is different from that which the user had in mind."


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: NEW handling: About rejects, and kernels (Was: Re: NEW handling ...)

[Adam McKenna]

On Thu, Mar 24, 2005 at 12:48:14PM -0600, Adam Majer wrote:
> Andreas Barth wrote:
> 
> > Actually, I believe the Debian project as whole _wants_ to getting
> >
> >software released. That was at least the decision in all GRs where
> >people didn't hide the intents ("editorial changes").
>
> Indeed. These types of changes are akin to changing a country's
> constitution and calling these "editorial changes" bill. But then again
> we can always change it back and call the change "editorial changes" as
> well.

No matter how you feel about the term "editorial changes", it seems to me
that if these changes were really so bad, and the majority of the project is
now against them, they should be easy enough to roll back.

All we need is another GR.  Stop bitching and propose one.

--Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: intend-to-implement: script to obtain Debian Source

[Junichi Uekawa]

Hi,

> > Optional source patching is non-standard in Debian, and 
> > I would like a standard interface to interact with Debian 
> > source.
> 
> So would I. Which is why I filed #250202

I have had a vague recollection that there was something 
which had not been implemented yet; thanks for pointing it out.

The discussion is pointing to a direction that is human-parsed 
and requiring a large amount of change in Debian archive.
I would like an interim solution before that is implemented.


Background:

1. I would like to keep an up-to-date CVS repository of Debian source code

2. I would like to automate source-importing Debian packages to gonzui (a 
source-code searching engine)


regards,
junichi

-- 
Junichi Uekawa, Debian Developer
17D6 120E 4455 1832 9423  7447 3059 BF92 CD37 56F4
http://www.netfort.gr.jp/~dancer/





pgp4S0uuS3Dae.pgp
Description: PGP signature

Re: How to define a release architecture

[Rob Browning]

Peter 'p2' De Schrijver <[EMAIL PROTECTED]> writes:

> The arch should still be available, but a big enough collection of
> existing machines will do here IMO. Not that this holds for mips as
> there are new MIPS based systems available. Both broadcom and PMC
> announced new MIPS based chips for example. And there is AMD
> (Alchemy) and a bunch of others using MIPS as well.

Similarly, though I've never actually used one, this seemed like it
might be an interesting router:

  http://www.routerboard.com/rb500.html

and if I *were* to use one, I'd certainly prefer to run Debian on it
if I could.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: intend-to-implement: script to obtain Debian Source

[Wouter Verhelst]

On Sat, Mar 26, 2005 at 06:54:19AM +0900, Junichi Uekawa wrote:
> Optional source patching is non-standard in Debian, and 
> I would like a standard interface to interact with Debian 
> source.

So would I. Which is why I filed #250202.

Be sure to read the whole bug -- there's quite some discussion about the
pro and cons of several approaches

-- 
 EARTH
 smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
 WATER
 -- with thanks to fortune


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

intend-to-implement: script to obtain Debian Source

[Junichi Uekawa]

Hi,

I am planning to implement a script to obtain Debian source.
Is there anyone who has already done that ?

It is planned to have the following features:

1. wrapper to dpkg-source -x 
2. heuristically parse debian/rules file to 
   extract and patch the Debian source as 
   dbs/dpatch requires.

Optional source patching is non-standard in Debian, and 
I would like a standard interface to interact with Debian 
source.



regards,
junichi


pgp8LSb9ZGTKC.pgp
Description: PGP signature

Re: Another load of typos

[Aaron M. Ucko]

Florian Zumbiehl <[EMAIL PROTECTED]> writes:

>> FLTK

Please consider this ambiguous (like FAQ), as upstream favors the
pronunciation "fulltick" (and makes a point of noting so on the main
http://www.fltk.org/ page because a lot of users nevertheless do spell
it out).

Thanks.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Let's stop feeding the NVidia cuckoo

[Allan Sandfeld Jensen]

On Friday 04 March 2005 17:47, Thiemo Seufer wrote:
> Kalle Kivimaa wrote:
> > Goswin von Brederlow <[EMAIL PROTECTED]> writes:
> > > Source code is source code. Obfuscated or not does not change that. It
> > > fullfills at least the letter of DFSG#2. For it to violate DFSG#2 you
> > > would have to show that it is not source and the gcc already prooves
> > > you wrong there. If you use 'obfuscation' or in other words
> > > 'readability' as measurement what source is then a lot of perl code
> > > would not qualify in my eyes.
> >
> > Source code is commonly defined as "the author's most preferred source
> > of making modifications".
>
> That's not the common definition but the GPL one. IMO the IOCCC stuff
> is source, and it's unlikely the author wrote it in the final form.
>
But wouldn't that make the NV driver GPL incompatible even if considered open 
source?
 
`Allan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#301408: ITP: ipodder -- an Internet audio program ("podcast") download tool

[Hilko Bengen]

Package: wnpp
Severity: wishlist

* Package name: ipodder
  Version : 2.0
  Upstream Author : Adam Curry et. al.
* URL or Web page : http://ipodder.sourceforge.net
* License : GPL
  Description : an Internet audio program ("podcast") download tool

iPodder is a Podcasting application, allowing users to capture and
listen to Internet audio programs.

It allows users to select and download shows and music and to play
whenever they want on their iPods, portable digital media players, or
computers automatically, after specifying which music or shows they
want to listen to.

Homepage: http://ipodder.sourceforge.net/

Upstream's main development and testing platform seems to be Windows
and MacOS X -- the Linux version offered for download is still 1.1. 
However, I have successfully run the 2.0 version checked out from CVS.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Our Final Newsletter??? Maybe not!

[Kasket Kyle]

Ok, well it looks like some people just can't see progress, or 
understand
bulk email law. well, even though I do include an opt-out mechanism for
people who do not wish to receive our newsletter. In any case, I am tired
of the harrasment and tired of people sending complaints to our host. So,
everyone is now off of our mailing list. yes, you are no longer on our
mailing list after this e-mail adress.

But...

If you would like to continue getting these updates, of which I'm sure a
lot of you are, simply visit http://www.kasketrecords.com and sign up for
the newsletter. Its that easy to get all of the newest updates, show info,
and exclusive audio!

Allright, that's it, if you get the next fanletter your a true fan.

Remember, http://www.kasketrecords.com and sign up for the newsletter.
Peace.

-Kasket Kyle
http://www.kasketrecords.com
http://www.braintraumahiphop.com



THERE IS NO NEED TO REPLY TO THIS TO BE REMOVED! YOU HAVE ALLREADY BEEN
REMOVED!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

How to detect which user is connected to $DISPLAY

[Michelle Konzack]

Hello *,

curently I am coding a tool which run from cron (as root) periodicly
and if a $USER is loged into X it shows Messages.

My Problem is, HOW to find the $USER who is connected to a $DISPLAY.

If I start two xserver I have e.g. :0 and :1.

I was serching for a command which tell me which user was opening the
xsession but without luck.  'who' does not work for this.

Thanks in advance
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Re: If Debian's too radical for you... [was: NEW handling: About rejects, and kernels]

[Raphael Hertzog]

Le jeudi 24 mars 2005 à 11:13 +1100, Matthew Palmer a écrit :
> "Some would say that this has already happened".  Not a fork, per se,
> but Ubuntu's licencing policy (and the general level-headedness of the
> people I know who are deeply involved in it) suggests that it may be
> the refuge you seek.

It's not the right answer. When I joined Debian, we were not considered
as fanatic. In facts, we were much more pragmatic... Debian was
separated from the FSF because it decided to stay pragmatic and refused
to remove non-free just for the intellectual satisfaction of the
fanatics.

Nowadays, we're going backwards and it's not good. I don't want to leave
Debian, I want Debian to stay like it has always been. So I prefer to
fight the fanatics inside Debian instead of leaving.

Cheers,
-- 
Raphaël Hertzog -+- http://www.ouaza.com
Formation Linux et logiciel libre : http://www.logidee.com
Earn money with free software: http://www.geniustrader.org


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Fwd: Re: Server Hardware

[Daniel Burrows]

  I just saw the attached email message on a LUG mailing list.  It's the first 
time I've heard of this, and it looks a bit worrying, especially since a lot 
of newer machines are shipping SATA-only these days.

  What I'm wondering is:

   (a) Does the default sarge kernel run afoul of the problems alluded to in 
this email?  I suppose the issue would be that you don't get the usual 
benefits of journalling.

  (b) If it does, is there a big fat warning somewhere in the installer when 
the user tries to partition a SATA disk with a journalling filesystem?

  Daniel

-- 
/- Daniel Burrows <[EMAIL PROTECTED]> -\
|   If we do not change our direction   |
|   we are likely to end up where we are headed.|
\-- Listener-supported public radio -- NPR -- http://www.npr.org ---/
--- Begin Message ---
On Wed, 23 Mar 2005 21:23:14 -0500, Jeff Wolfe <[EMAIL PROTECTED]> wrote:
> James Gingerich wrote:
> > Hello All,
> >
> > I'm getting ready to make a purchasing decision with limited funds and
> > would like some advice.
> >
> > My department is looking to purchase a new tower server, running Linux
> > of course.  Its main purpose is a web server (Apache front end, Tomcat
> > application server), but also uses its own RDBMS, and a little mail and
> > file sharing (samba).  It backs up regularly, with little changes.
> >
> > I'm trying to determine what the best comprimise of hardware for my cost
> > is.  I believe the key items are processor, memory, and hard drive(s).
> > I just don't know which is more important for the server to squeeze the
> > best performance, i.e.; weighing 2 processors vs. more memory vs. SCSI
> > drives?
> >
> > Here is what I come up with thus far:
> >
> > 1 Xeon processor @ 3.0 GHz, 2 MB Cache, 800 MHz FSB
> > 2 GB memory DDR2 @ 400 MHz
> > CERC SATA RAID controller (RAID 0)
> > 2 160 GB SATA hard drives
> >
> > Any suggestions would be greatly appreciated.
>
> I would encourage you to mirror the drives instead of striping.
>
> Also, if you're thinking of a distribution other than Redhat. There sometimes
> can be issues with drivers and non-redhat distros.. Dell only certifies their
> systems with RedHat.
>

Depending on how much you care about data integrity, things get more
complicated.  SATA disks use write-back cache in order to provide
performance that is competitive with SCSI disks in write-through mode.
 Unfortunately, the sata protocol state machine assumes write-back is
acceptable, and thus does not implement the scsi tcq asynchronous
callback model.  The net effect is that transactional systems, such as
journalling filesystems and databases, will not operate correctly on
sata disks, unless those transactional layers have special sata
extensions.  Recent 2.6 kernels support journalling on sata through
their write barriers interface, which is just a cache flush command on
the backend.  So, if you care about integrity, your options are to
turn off disk write caches (which makes performance abysmal due to
sata's poorly designed state machine), use a very recent 2.6 kernel,
or use a distro that has write barriers back-ported into their custom
kernel.  Furthermore, you need to be sure that you get the midrange
sata disks, and not the desktop-oriented disks, because the MTBFs are
very different.

--
Tom Keiser
[EMAIL PROTECTED]

--
To unsubscribe, send mailto:[EMAIL PROTECTED]
  No subject or message text is required.
For human assistance, mailto:[EMAIL PROTECTED]

--- End Message ---


pgpNrIptMG5AX.pgp
Description: PGP signature

Re: Required firewall support

[Steve Greenland]

On 21-Mar-05, 12:39 (CST), David Weinehall <[EMAIL PROTECTED]> wrote: 
> On Sun, Mar 20, 2005 at 11:22:48AM -0600, Steve Greenland wrote:
> >
> > And that's what we do. But some other OSs (Solaris) do support strict
> > multihoming with a config parameter, it would be nice if Linux did.
> 
> netdev@oss.sgi.com <--- patches goes that way.
> linux-kernel@vger.kernel.org <--- or possibly that way.

It's been discussed and rejected in the past. The multi-homing RFC (I
forget which one) has unclear[1] wording on which behaviour is proper.

Steve

[1] Well, *I* (and others) don't think it's unclear. The trouble is
that many others also don't think it's unclear, but come to an opposite
conclusion.

-- 
Steve Greenland
The irony is that Bill Gates claims to be making a stable operating
system and Linus Torvalds claims to be trying to take over the
world.   -- seen on the net


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bits (Nybbles?) from the Vancouver release team meeting

[Steve Greenland]

On 21-Mar-05, 14:45 (CST), Adrian Bunk <[EMAIL PROTECTED]> wrote: 
> HP still produces both workstations and servers with PA-RISK processors.
  

Yeah, we had one of those. I'm surprised they're still making them; the
PA-RISC series is lot more reliable...

Steve

-- 
Steve Greenland
The irony is that Bill Gates claims to be making a stable operating
system and Linus Torvalds claims to be trying to take over the
world.   -- seen on the net


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#301410: ITP: confluence -- language for synchronous reactive hardware system design

[Wesley J. Landaker]

Package: wnpp
Severity: wishlist
Owner: "Wesley J. Landaker" <[EMAIL PROTECTED]>

* Package name: confluence
  Version : 0.10.4
  Upstream Author : Tom Hawkins <[EMAIL PROTECTED]>
* URL : http://www.confluent.org/
* License : GPL
  Description : language for synchronous reactive hardware system design

>From the upstream website :

  A Confluence program can generate digital logic for an FPGA or ASIC
  platform, or C code for hard real-time software.

  Confluence combines the component-based methodologies of Verilog and
  VHDL with the expressiveness of higher order functional programming.

  In comparison to Verilog, VHDL, and C, systems designed in Confluence
  result in 2X to 10X code reduction, making the source easier to manage
  and reuse. And because Confluence relies on a correct-by-construction
  compiler, bugs are reduced--some are prevented altogether--thus
  reducing the overall verification effort.

Essentially it's a high-level HDL that can generate VHDL, Verilog, JHDL,
C, etc, from a functional-style description. Quite a few open hardware
cores are written using this language, and it's growing in popularity in
industry as well.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Idea: about package installation under chroot.

[Wouter Verhelst]

Op do, 24-03-2005 te 20:01 +0100, schreef Daniel Baumann:
> Josselin Mouette wrote:
> > I don't know whether we have ports without /proc,
> 
> the Hurd has no /proc.

Additionally, other kernels (such as the FreeBSD kernel) that do have
a /proc do not have it functionally overloaded like the Linux one.

e.g., FreeBSD's /proc only contains process directories; it does not
contain sysctl stuff, or other things like /proc/mounts.

-- 
 EARTH
 smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
 WATER
 -- with thanks to fortune


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Let's stop feeding the NVidia cuckoo

[Paul Hedderly]

On Thu, Mar 24, 2005 at 05:33:50PM +, Henning Makholm wrote:
> Scripsit Paul Hedderly <[EMAIL PROTECTED]>
> 
> > What we have is source code (yes code that can be compiled) which is
> > unencumbered, we can modify,compile, distribute etc... whether it is
> > _harder_ to modify or not because of choices the _owner/author_ has
> > made or not... is nothing to do with freedom.
> 
> What you are showing here is that "code that can be compiled" is not a
> working defintion of "source code".

It not only works, but has been used for a long time.

What you are showing is that you have a dislike for source that is hard
to modify (fair enough) and would like for it not to be called 'source
code' if you feel it is hard to read/modify.

'source code' does not mean 'code that came from the original source
untouched' (lets face it, define 'original source' when there is more
than one person working on code with different trees, working machines
etc...) it literally means code that can be used to generate a binary.

So please stop making weird claims about the meaning of words and
definitions and state plainly that you don't like hard to read/modify
(ugly?) source code and would like Debian to ban using such. We can
argue and vote on that...

--
Paul


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: discrepancies between uploaded and source-built .deb

[Michelle Konzack]

Am 2005-03-24 01:33:37, schrieb Jeroen van Wolffelaar:

> Common problem unfortunately in the open source/Debian world... not that
> $what_you_want doesn't exist, but that you just don't know it exists nor
> where to find it :(.

Realy good spoken...

> --Jeroen

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Re: update-menus runs in the background?

[Alban Browaeys]

Le Thu, 24 Mar 2005 21:08:10 -0500, Justin Pryzby a écrit :

> It seems that /usr/bin/update-menus now runs in the background.  I ran
> sudo apt-et install glade, and after it finished, I ran ps -ef |tail
> -5, and the last commands running were update-menus.real, and
> install-menu.
> 
> Is it supposed to be a background job, and, if so, why?

yes. I don't know why but i guess it is so as when one update multiple
packages calling update-menu, update-menu is only run once after all
packages are upgraded (weel update-menu check if dpkg is running and wait
if so).

Alban


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: update-menus runs in the background?

[Josselin Mouette]

Le jeudi 24 mars 2005 à 21:08 -0500, Justin Pryzby a écrit :
> It seems that /usr/bin/update-menus now runs in the background.  I ran
> sudo apt-et install glade, and after it finished, I ran ps -ef |tail
> -5, and the last commands running were update-menus.real, and
> install-menu.
> 
> Is it supposed to be a background job, and, if so, why?

This is because most packages launch update-menus, which is quite
time-consuming. It pus itself in the background, and waits for dpkg to
release its lock before beginning.
-- 
 .''`.   Josselin Mouette/\./\
: :' :   [EMAIL PROTECTED]
`. `'[EMAIL PROTECTED]
   `-  Debian GNU/Linux -- The power of freedom

Re: update-menus runs in the background?

[Colin Watson]

On Thu, Mar 24, 2005 at 09:08:10PM -0500, Justin Pryzby wrote:
> It seems that /usr/bin/update-menus now runs in the background.  I ran
> sudo apt-et install glade, and after it finished, I ran ps -ef |tail
> -5, and the last commands running were update-menus.real, and
> install-menu.
> 
> Is it supposed to be a background job, and, if so, why?

It's always done this, as far as I know (FSVO "always"). It's a very old
hack to speed up upgrades by making update-menus only run once at the
end of the whole upgrade run, by checking for the dpkg lock and
backgrounding itself if it's there and if there isn't already an
update-menus process waiting.

It could be an apt DPkg::Post-Invoke hook, but this is no good for
people running 'dpkg -i' directly; really, it's an ideal use case for
the as-yet-unimplemented dpkg trigger mechanism, which I believe Scott
plans on implementing.

-- 
Colin Watson   [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

ITP: antennavis -- antenna visualization software (please advise on togl license)

[Joop Stakenborg]

Package: wnpp
Owner: Joop Stakenborg <[EMAIL PROTECTED]>
Severity: wishlist

* Package name: antennavis
  Version : 0.2
  Upstream Author : Ken Harker <[EMAIL PROTECTED]>
* URL : http://n5xu.ae.utexas.edu/antennavis
* License : GPL
  Description : antenna visualization software

Antennavis is a visualization toolkit designed to aid the user in better
understanding the data output by the NEC2 antenna modelling software.

nec2 is already part of debian.

The antennavis source includes a copy of togl.c and togl.h, which are
both part of the Togl library, an OpenGL TK widget hosted on
sourceforge. Here is the full Togl license. Any advise on whether this
is DFSG free? Looks okay to me
-
This software is copyrighted by Brian Paul ([EMAIL PROTECTED])
and Benjamin Bederson ([EMAIL PROTECTED]).  The following terms apply
to all files associated with the software unless explicitly disclaimed
in individual files.

The authors hereby grant permission to use, copy, modify, distribute,
and license this software and its documentation for any purpose,
provided that existing copyright notices are retained in all copies and
that this notice is included verbatim in any distributions. No written
agreement, license, or royalty fee is required for any of the authorized
uses. Modifications to this software may be copyrighted by their authors
and need not follow the licensing terms described here, provided that
the new terms are clearly indicated on the first page of each file where
they apply.

IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND
DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT,
UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
-

I am not subscribed to debian-legal, please cc to me.

Regards,
Joop [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]