Re: Problems with libsdl1.2-dev 1.2.2-3.3 and OpenGL?

[Joseph Carter]

I'm sending this to debian-x on the off chance that the next person to get
bitten by this problem will search the archives and find it.  I'm not on
debian-x, so please Cc replies if appropriate.

On Tue, Jan 15, 2002 at 01:33:00AM +0100, Paul Fleischer wrote:
> > > in some way. When I try to compile any program using SDL and OpenGL, the
> > > window/screen shows the last image, from the OpenGL program which was
> > > previous run.
> 
> I am one of those nvidia-using-guys, sorry. However, I find that when I
> write code against X11, and GL it works just fine - so, I would say SDL
> is somewhat broken (hopefully I am wrong in this)

Actually, the problem here is that Debian does not adhere to the OpenGL
Linux ABI document which requires that libGL be in /usr/lib and only in
/usr/lib, citing this very problem as the reason.  Of course, this goes
against the unix way, so naturally no Linux dist I know of actually obeys
the ABI's requirement.  And just to make life more interesting, several
different ways of disobeying it exist, some of which are just bizarre.

Basically, when you compile, /usr/X11R6/lib ends up getting checked before
/usr/lib for libGL.  To prevent this, the nvidia-glx maintainer diverts
libGL.so*.  He neglected to divert libGL.a, which is getting compiled in
to your program.  If you're impatient, just rm /usr/X11R6/lib/libGL.a and
recompile your program.  You can't use it anyway and I promise you won't
miss it.  ;)

Actually, it's basically never a good idea to link the static libGL, it
might be better to not bother installing it in future builds since the
library is most certainly hardware-specific.  Older 3dfx cards, and all
NVIDIA cards won't work with that lib at all.  The last I've heard from
guys at Matrox was that they too will likely go with a non-Mesa OpenGL,
and possibly ATI will as well.  I'm not sure about 3DLabs, but they're not
much of a player in the consumer hardware market and probably don't even
know we exist.

-- 
Joseph Carter <[EMAIL PROTECTED]>I swear this thing's an AI!
 
 add a GF2/3, a sizable hard drive, and a 15" flat panel and
   you've got a pretty damned portable machine.
 a GeForce Two-Thirds?
 Coderjoe: yes, a GeForce two-thirds, ie, any card from ATI.



pgp4fpT4biWO6.pgp
Description: PGP signature

Re: Please don't do this (code fragment)

[Thomas Bushnell, BSG]

[EMAIL PROTECTED] writes:

> I don't find any such mention in K&R [1978].  There is nothing I can
> see to guarantees that MAX_INT + 1 < 0.

K&R [1978] is not the C standard.

Re: disposition of the diskless package

[Eric Van Buggenhaut]

On Mon, Jan 14, 2002 at 04:26:22PM -0500, Justin Hahn wrote:
> I'm currently a user of the diskless package, and I'd like to ask the
> maintainer a couple questions. The problem is it looks like it's
> unmaintained. According to the README.Debian is used to be brian may but is
> now [EMAIL PROTECTED] - however is homepage claims he's no longer
> maintaining this package (but packages.debian.org lists him as the
> maintainer)
> 
> Anyone know who the active maintainer is (if he/she exists?) 
> 

Have you contacted dancer directly ?


-- 
Eric VAN BUGGENHAUT "Hay tampones y tampones..." (Eva Serrano)
Andago
\_|_/   Av. Santa Engracia, 54
   \/   \/  E-28010 Madrid - tfno:+34(91)2041100
a n d a g o  |--http://www.andago.com
   /\___/\  "Innovando en Internet"
/ | \   [EMAIL PROTECTED]

Re: disposition of the diskless package

[Junichi Uekawa]

Eric Van Buggenhaut <[EMAIL PROTECTED]> cum veritate scripsit:

> > Anyone know who the active maintainer is (if he/she exists?) 
> > 
> 
> Have you contacted dancer directly ?

No he hasn't.

regards,
junichi

-- 
[EMAIL PROTECTED] : Junichi Uekawa   http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423  7447 3059 BF92 CD37 56F4

Re: disposition of the diskless package

[Junichi Uekawa]

Justin Hahn <[EMAIL PROTECTED]> cum veritate scripsit:

> Anyone know who the active maintainer is (if he/she exists?) 

See bug #107808. 

Basically, some people wanted to take over, and didn't.



regards,
junichi

-- 
[EMAIL PROTECTED] : Junichi Uekawa   http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423  7447 3059 BF92 CD37 56F4

Re: Vanishing /usr/doc symlink

[Santiago Vila]

Julian Gilbey wrote:
> I just upgraded my unstable system today.  In the process, my /usr/doc
> -> /usr/share/doc symlink disappeared.  I didn't notice till
> afterwards, but I'm pretty sure that's what did it.  (It was there
> yesterday, and it's unlikely to have been anything else.)
>
> Below is the diff between yesterday and today's dpkg -l \* | grep ^ii
> output; I haven't had a chance to examine all of these packages,
> though.  Anyone have any ideas which package might be guilty for doing
> this?

Every of them. None of them. Most probably, you just happened to
remove or upgrade the last package containing /usr/doc in your system,
and, as a result, dpkg removed it, since it was not a non-empty directory.

Re: Vanishing /usr/doc symlink

[martin f krafft]

also sprach Julian Gilbey <[EMAIL PROTECTED]> [2002.01.15.0413 +0100]:
> I just upgraded my unstable system today.  In the process, my /usr/doc
> -> /usr/share/doc symlink disappeared.  I didn't notice till
> afterwards, but I'm pretty sure that's what did it.  (It was there
> yesterday, and it's unlikely to have been anything else.)

/usr/doc has been deprecated for a long time. and yes, the responsible
package is 'sysutils' i think:

fishbowl:/usr/share/doc/sysutils> dpkg -S /usr/doc
sysutils: /usr/doc

however, there's no info int the changelog (bug #96211 *doesn't* seem to
relate to this actually).

i think /usr/doc isn't necessary, and i haven't seen it on newer woody
systems, but i'd like to know what exactly is causing it to disappear on
existing systems. it's still there on my older woodies, even though they
are upgraded at least weekly.

-- 
martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
  
"no, 'eureka' is greek for 'this bath is too hot.'"
-- dr. who


pgp9jt7wfRZj2.pgp
Description: PGP signature

Re: Problems with libsdl1.2-dev 1.2.2-3.3 and OpenGL?

[Paul Fleischer]

tir, 2002-01-15 kl. 07:21 skrev Joseph Carter:
> I'm sending this to debian-x on the off chance that the next person to get
> bitten by this problem will search the archives and find it.  I'm not on
> debian-x, so please Cc replies if appropriate.
> 

> Actually, the problem here is that Debian does not adhere to the OpenGL
> Linux ABI document which requires that libGL be in /usr/lib and only in
> /usr/lib, citing this very problem as the reason.  Of course, this goes
> against the unix way, so naturally no Linux dist I know of actually obeys
> the ABI's requirement.  And just to make life more interesting, several
> different ways of disobeying it exist, some of which are just bizarre.

 
> Basically, when you compile, /usr/X11R6/lib ends up getting checked before
> /usr/lib for libGL.  To prevent this, the nvidia-glx maintainer diverts
> libGL.so*.  He neglected to divert libGL.a, which is getting compiled in
> to your program.  If you're impatient, just rm /usr/X11R6/lib/libGL.a and
> recompile your program.  You can't use it anyway and I promise you won't
> miss it.  ;)
Interesting - it worked ;) Now I can go hit myself for not checking that
(indeed I find myself removing libGL.a all the time).

Oh well, thanks for the answer and your time. However, I am still
wondering how it can be that the problem does not occur when I write X11
code instead of SDL code. But finally I can get back to OpenGL
development ;) Thanks again!
 
> Actually, it's basically never a good idea to link the static libGL, it
> might be better to not bother installing it in future builds since the
> library is most certainly hardware-specific.  Older 3dfx cards, and all
> NVIDIA cards won't work with that lib at all.  The last I've heard from
> guys at Matrox was that they too will likely go with a non-Mesa OpenGL,
> and possibly ATI will as well.  I'm not sure about 3DLabs, but they're not
> much of a player in the consumer hardware market and probably don't even
> know we exist.
Hmm...

-- 
Paul Fleischer // ProGuy
Registered Linux User #166300
http://counter.li.org

Re: Will woody ever become stable?

[Jules Bean]

On Mon, Jan 14, 2002 at 02:49:00PM +0100, Adrian Bunk wrote:
> I had a longer discussion with our release manager who said in this
> discussion that there's no progress in the freeze of woody. We won't enter
> the next stage of the freeze until the base and standard packages are in a
> releasable state - and the number of RC bugs in these packages is
> increasing (one reason is e.g. that some of these packages like
> boot-floppies break when new upstream versions of other packages they
> depend on are uploaded which may lead to RC bugs like #127405). woody is
> officially frozen for several months but it's still possible for new
> upstream versions of every package to enter testing.

Hmm.

I'll bite.

I would like to ask our release manager for more information.  More
effort is required to herd the kittens.

I really don't feel in-touch with how the freeze is going, and I
imagine that I'm not alone in that. For example, I think I thought
that Adrian is incorrect above, that certain packages are frozen.  I
thought I'd seen notes suggesting that some packages were frozen, in
fact. Base?


I would like to see weekly 'freeze update' reports, sent here, telling
us what goals have been passed, and what the current stopping points
are. Something like the following:


Freeze Update
-

Status

We are *still* trying to freeze standard and the task packages.  This
won't be possible until they are cleared of RC bugs ...

...

Uploads

Maintainers of base packages should only upload security fixes and
fixes for serious bugs.  These should be uploaded to
woody-proposed-updates.

Maintainers of standard and task packages should try to avoid new
code, and work to fix bugs.

Maintainers of (non-task) optional and extra packages should, at the
moment, continue to track new upstream versions, but should also work
to remove RC bugs.

...


Or something like that.  Is the above even a correct depiction? I
don't know... 


Herd us harder! ;-)

Jules

Re: Will woody ever become stable?

[Anthony Towns]

On Tue, Jan 15, 2002 at 11:00:38AM +, Jules Bean wrote:
> I would like to see weekly 'freeze update' reports, sent here, telling
> us what goals have been passed, and what the current stopping points
> are. Something like the following:

Well, the goal that was meant to have passed was "no outstanding RC bugs
in base", but with things like #126441 (outstanding glibc security bug
for around a month, along with some other unfiled RC issues that've
been around longer), and #123345 (security bug in base-passwd, that
seems to have a patch now), we've pretty much regressed back to the
"we're not remotely ready to release" stage. And if we can't manage
to fix security issues in required packages promptly, especially when
patches are available, I don't see much point worrying about all the
other things that need doing.

We have an RC bug list that gets regularly posted to -devel-announce,
and we have base.debian.net and standard.debian.net listing the bugs in
the most important packages.

> Or something like that.  Is the above even a correct depiction? I
> don't know... 

The correct depiction is "fix RC bugs promptly, and other bugs as soon
as you can".

> Herd us harder! ;-)

Unfortunately I'm excuriatingly busy with other things [0] until
mid-February, so I just don't have time to pester three or four
dozen people personally on a daily basis to get the release out. That
*shouldn't* be necessary; just getting rid of the RC bugs that everyone
should already be feeling guilty about would get us right back on track;
but it appears that it is.

Cheers,
aj

[0] http://linux.conf.au/ amongst other things

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

The daffodils are coming. Are you?
  linux.conf.au, February 2002, Brisbane, Australia
--- http://linux.conf.au/


pgpkyP1H5OEna.pgp
Description: PGP signature

pcmcia-modules in woody

[Lauri Tischler]

pcmcia-modules for kernels 2.19 and 2.20 dont exist.
Whats up duck ?

--
Lauri Tischler, Network Admin
Tel:+358-9-47846331*   Mouse movement detected  *
Fax:+358-9-47846500* Reboot Windows to activate changes *
Mobile: +358-40-5569010
EMail:  [EMAIL PROTECTED]

Re: Will woody ever become stable?

[Adrian Bunk]

On Tue, 15 Jan 2002, Jules Bean wrote:

>...
> > officially frozen for several months but it's still possible for new
> > upstream versions of every package to enter testing.
>...
> I really don't feel in-touch with how the freeze is going, and I
> imagine that I'm not alone in that. For example, I think I thought
> that Adrian is incorrect above, that certain packages are frozen.  I
> thought I'd seen notes suggesting that some packages were frozen, in
> fact. Base?
>...

According to update_excuses [1] "a package is frozen" currently means that
the 2/5/10 days delay until a package may enter testing is doubled but new
upstream versions are still allowed to enter testing, e.g. (the only
reason why the new upstream version of modutils isn't already in testing
is a RC bug):

<--  snip  -->

...
 * base-config (1.33.7 to 1.33.9)
  + Maintainer: Joey Hess
  + Package is in freeze, doubling delay
  + Too young, only 7 of 20 days old
...
 * bash (2.05a-3 to 2.05a-4)
  + Maintainer: Matthias Klose
  + Package is in freeze, doubling delay
  + Too young, only 2 of 4 days old
...
 * modutils (2.4.11-1 to 2.4.12-1)
  + Maintainer: Wichert Akkerman
  + Package is in freeze, doubling delay
  + 11 days old (needed 10 days)
...

<--  snip  -->

> Jules

cu
Adrian

[1] http://ftp-master.debian.org/testing/update_excuses.html.gz

Re: Vanishing /usr/doc symlink

[Colin Watson]

On Tue, Jan 15, 2002 at 11:01:35AM +0100, Santiago Vila wrote:
> Julian Gilbey wrote:
> > I just upgraded my unstable system today.  In the process, my /usr/doc
> > -> /usr/share/doc symlink disappeared.  I didn't notice till
> > afterwards, but I'm pretty sure that's what did it.  (It was there
> > yesterday, and it's unlikely to have been anything else.)
> >
> > Below is the diff between yesterday and today's dpkg -l \* | grep ^ii
> > output; I haven't had a chance to examine all of these packages,
> > though.  Anyone have any ideas which package might be guilty for doing
> > this?
> 
> Every of them. None of them. Most probably, you just happened to
> remove or upgrade the last package containing /usr/doc in your system,
> and, as a result, dpkg removed it, since it was not a non-empty directory.

What happened to the transition plan that said we'd ship woody with a
/usr/doc full of symlinks, not no /usr/doc at all?

  http://lists.debian.org/debian-ctte-9908/msg00038.html

-- 
Colin Watson  [EMAIL PROTECTED]

Re: Vanishing /usr/doc symlink

[Colin Watson]

On Tue, Jan 15, 2002 at 11:01:43AM +0100, martin f krafft wrote:
> /usr/doc has been deprecated for a long time.

The original plan said that base-files would still contain it. Otherwise
we're in the situation where upgrades from potato will have /usr/doc but
new installs of woody won't, which in turn means that the script that
will remove symlinks from inside /usr/doc and migrate to a single
/usr/doc -> /usr/share/doc symlink won't be as well tested as it should
be.

> and yes, the responsible package is 'sysutils' i think:
> 
> fishbowl:/usr/share/doc/sysutils> dpkg -S /usr/doc
> sysutils: /usr/doc

I fixed sysutils in unstable recently.

-- 
Colin Watson  [EMAIL PROTECTED]

Re: About sponsoring non-free packages

[Colin Watson]

On Mon, Jan 14, 2002 at 01:04:10PM +0100, J?r?me Marant wrote:
>   I propose that we do not sponsor people for non-free packages.
>   People that we want to join us and seeking sponsors for
>   non-free package are showing that they do not understand
>   our philosophy and dedication to Free Software. 

One of my initial packages was non-free (still is, although I hold out
hope for a licence change at some point). I suggest that a better policy
is closer to this:

  New maintainers applying as packagers should contribute something to
  main as part of their tasks and skills check. This could either be new
  packages or adopting existing ones. They may submit work they've done
  in contrib or non-free, which may help the AM judge their packaging
  abilities, but this work should not be considered sufficient to pass
  the check.

I wouldn't have objected to this when I was applying - I had packages in
main too.

-- 
Colin Watson  [EMAIL PROTECTED]

J.T. Sterlings Daily Special - January 15, 2002

[listadmin]

Title: Welcome to J.T. Sterlings








  
J.T. Sterlings Daily Specials - January 15, 2002Our Daily Specials change once every day at Midnight, Eastern Time.

You are subscribed to J.T. Sterlings Daily Special mailings.


Visit us at www.jtsterlings.com or click below to place your order.



  



  
  Item
21531
Rose bush with a butterfly that flutters by. Tune: "Rose Garden." 12" high. $21.95 Regular Price.
Regular Price $21.95
Sale Price $16.02
Today's Special Price $14.42
You save 10%

Click
Here To Order!
 


  

  



  
  Item
21564
Delicate pink shell vase with flowers and parrot are the designs on this lacquered wood screen. 9 3/4" x 1" x 28" high. $29.95 Regular Price.
Regular Price $29.95
Sale Price $21.86
Today's Special Price $19.67
You save 10%

Click
Here To Order!
 


  

  



  
  Item
21565
Lacquered wood screen with peach and blue birds with yellow and green shell leaves and flowers. 9 3/4" x 1" x 28" high. $29.95 Regular Price.
Regular Price $29.95
Sale Price $21.86
Today's Special Price $19.67
You save 10%

Click
Here To Order!
 


  

  



  
  Item
21566
Blue, yellow and pink birds with pink and green leaves and flowers bedeck this lacquered wood screen. 9 3/4" x 1" x 28" high. $29.95 Regular Price.
Regular Price $29.95
Sale Price $21.86
Today's Special Price $19.67
You save 10%

Click
Here To Order!
 


  

  



  





You are receiving this special offer because you have provided permission to receive third party email communications regarding special online promotions or offers.  Any third-party offers contained in this email are the sole responsibility of the offer originator. 
Copyright © 2001 J.T. Sterlings - 5700 Memorial Highway Suite 206, Tampa FL 33615. All Rights Reserved.
J.T. Sterlings does not condone the use of unsolicited email (spam).  If you do not wish to receive any further messages from J.T. Sterlings, please follow the instructions below to unsubscribe.  


---
You are currently subscribed to dailyspecial as: debian-devel@lists.debian.org
To unsubscribe send a blank email to:
 [EMAIL PROTECTED]

Re: Vanishing /usr/doc symlink

[Julian Gilbey]

On Tue, Jan 15, 2002 at 11:01:35AM +0100, Santiago Vila wrote:
> Julian Gilbey wrote:
> > I just upgraded my unstable system today.  In the process, my /usr/doc
> > -> /usr/share/doc symlink disappeared.  I didn't notice till
> > afterwards, but I'm pretty sure that's what did it.  (It was there
> > yesterday, and it's unlikely to have been anything else.)
> >
> > Below is the diff between yesterday and today's dpkg -l \* | grep ^ii
> > output; I haven't had a chance to examine all of these packages,
> > though.  Anyone have any ideas which package might be guilty for doing
> > this?
> 
> Every of them. None of them. Most probably, you just happened to
> remove or upgrade the last package containing /usr/doc in your system,
> and, as a result, dpkg removed it, since it was not a non-empty directory.

That's possible, I guess.  Shame I didn't think to keep a copy of
yesterday's dlocate database to check this hypothesis.

   Julian

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

 Julian Gilbey, Dept of Maths, Debian GNU/Linux Developer
  Queen Mary, Univ. of London see http://people.debian.org/~jdg/
   http://www.maths.qmul.ac.uk/~jdg/   or http://www.debian.org/
Visit http://www.thehungersite.com/ to help feed the hungry

Re: pcmcia-modules in woody

[martin f krafft]

also sprach Lauri Tischler <[EMAIL PROTECTED]> [2002.01.15.1240 +0100]:
> pcmcia-modules for kernels 2.19 and 2.20 dont exist.
> Whats up duck ?
   
are you talking to me?

pcmcia-modules have, AFAIK, been discontinued. these days, you have to
get pcmcia-source and kernel-source, and compile them yourself. it's
actually a real pain, but with the variety and sheer number of
kernel-images, it would be impossible to keep up to date on all
*-modules packages. it seems that alsa-modules is still doing that
though.

maybe someone else has more information.

-- 
martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
  
1-800-psych
hello, welcome to the psychiatric hotline.
if you are co-dependent, please ask someone to press 2.


pgp1gtfRiPLrj.pgp
Description: PGP signature

Re: Vanishing /usr/doc symlink

[martin f krafft]

also sprach Colin Watson <[EMAIL PROTECTED]> [2002.01.15.1301 +0100]:
> The original plan said that base-files would still contain it. Otherwise
> we're in the situation where upgrades from potato will have /usr/doc but
> new installs of woody won't,

which is exactly what i deem the current situation to be! on all
upgraded systems, /usr/doc continues to exist, on new woody systems, it
isn't there.

-- 
martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
  
the web site you seek
cannot be located but
endless others exist.


pgpxpxnJ9AEBt.pgp
Description: PGP signature

MusixTex for arm and sh architecture

[Tille, Andreas]

Hello,

second call for help to compile MusixTex on all architectures:

auric:~> madison musixtex
  musixtex |   1:0.98-1 |stable | source, alpha, arm, i386, m68k, 
powerpc, sparc
  musixtex |   1:0.99-1 |   testing | source, arm, ia64, m68k, powerpc, 
sparc
  musixtex |   1:0.99-1 |  unstable | arm, sh
  musixtex |  1:0.102-1 |  unstable | source, alpha, hppa, i386, ia64, 
m68k, powerpc, s390, sparc

Please could someone compile musixtex on arm and sh.

Kind regards

Andreas.

Re: Will woody ever become stable?

[Tille, Andreas]

On Tue, 15 Jan 2002, Anthony Towns wrote:

> Unfortunately I'm excuriatingly busy with other things [0] until
> mid-February, so I just don't have time to pester three or four
> dozen people personally on a daily basis to get the release out. That
> *shouldn't* be necessary; just getting rid of the RC bugs that everyone
> should already be feeling guilty about would get us right back on track;
> but it appears that it is.
Perhaps a statement:

   #define NUM_DAYS 150  /* or some better value */
   #define TIME_TO_FIX   30  /* ditto */

   The following packages will not go into woody because they have
   RC bugs for > NUM_DAYS days if they will not be fixed after
   TIME_TO_FIX days.

Kind regards

 Andreas.

Re: Will woody ever become stable?

[Mark Brown]

On Tue, Jan 15, 2002 at 11:00:38AM +, Jules Bean wrote:

> I would like to ask our release manager for more information.  More
> effort is required to herd the kittens.

I agree wholeheartedly with this.  With previous freezes things like the
release critical bugs list have provided a pretty clear and direct
indication of the progress of the freeze.  At the present moment the
information about what's going on tends to take the form of announcments
that things are going to happen followed by no visible indication that
anything has happened either way on the dates mentioned.

Regular "this is the state of play, this is what needs to happen for
things to proceed" messages would help a lot.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."


pgpby8dfYkr89.pgp
Description: PGP signature

Re: MusixTex for arm and sh architecture

[Adrian Bunk]

On Tue, 15 Jan 2002, Tille, Andreas wrote:

> Hello,

Hi Andreas,

> second call for help to compile MusixTex on all architectures:
>
> auric:~> madison musixtex
>   musixtex |   1:0.98-1 |stable | source, alpha, arm, i386, m68k, 
> powerpc, sparc
>   musixtex |   1:0.99-1 |   testing | source, arm, ia64, m68k, powerpc, 
> sparc
>   musixtex |   1:0.99-1 |  unstable | arm, sh
>   musixtex |  1:0.102-1 |  unstable | source, alpha, hppa, i386, ia64, 
> m68k, powerpc, s390, sparc
>
> Please could someone compile musixtex on arm and sh.

a small comment on this:

sh is not needed to get the musixtex into testing.

> Kind regards
>
> Andreas.

cu
Adrian

debian-devel@lists.debian.org

[Anton Feldmann]

Sehr geehrte Programm bereitsteller,

mein Name ist Anton Feldmann. Ich hätte gerne von ihnen gewust wann woody 
frozen ist.

Gruß

Herr Anton Feldmann
Hauptstrasse 102
59302 Oelde
___
1.000.000 DM gewinnen - kostenlos tippen - http://millionenklick.web.de
[EMAIL PROTECTED], 8MB Speicher, Verschluesselung - http://freemail.web.de
___
Das WEB.DE Zertifikat zur Pruefung digitaler Unterschriften gibts bei: 
http://trust.web.de/root.sql


smime.p7s
Description: S/MIME Cryptographic Signature

Digital unterschriebene E-Mail von FreeMail / Digitally signed email from FreeMail

[supamann]

(english version see below)

Sie erhalten in den naechsten Minuten eine digital unterschriebene E-Mail
von einem Freemail-Anwender. Damit Ihr E-Mail-Programm den Ausweis
ueberpruefen kann, muss das "Root-Zertifikat" von WEB.DE installiert sein.
Klicken Sie dazu bitte auf:

http://trust.web.de/root.sql

Auf dieser Web-Seite finden Sie eine genaue Anleitung zur Installation des
Zertifikats von WEB.DE in Ihr E-Mail-Programm.

Im Detail:
--

FreeMail, der kostenlose web-basierte E-Mail Dienst von WEB.DE
(http://web.de) bietet die Moeglichkeit, elektronische Post digital zu
unterschreiben und zu  verschluesseln. Sie koennen digital unterschriebene
Mails, die von einem FreeMail-Benutzer an Sie verschickt werden, aber nur
dann ueberpruefen lassen, wenn Ihr Mail-Programm diese Mails "akzeptiert".

Zu Verifizierung der Ausweise muss das "WEB.DE-Root-Zertifikat" in Ihr
E-Mail-Programm installiert werden. Das brauchen Sie nur ein einziges Mal zu
erledigen. Die Technik, die hinter diesem Verfahren steht, beruht auf dem
S/MIME-Standard. Dieser Standard ist in die gaengigen Browser und
E-Mail-Programme integriert.

Der Aussteller fuer alle Ausweise von FreeMail-Benutzern ist:

WEB.DE AG
Amalienbadstr. 41
76227 Karlsruhe

Um das Zertifikat zur Ueberpruefung der digitalen Unterschrift in die Liste
der Aussteller einzufuegen, klicken sie bitte: http://trust.web.de/root.sql
oder geben Sie diese Adresse ins Adressfenster Ihres Browsers ein.

Folgen Sie dann Schritt fuer Schritt den Anleitungen im Browserfenster.

Weitere Hinweise und Tips
=

Das Root-Zertifikat ist installiert:


Ist das Zertifkat in Ihr E-Mail-Programm installiert, wird die Unterschrift
ueberprueft. Die digitale Unterschrift verraet Ihnen folgendes:

- Den genauen Absender
- Prueft ob der Inhalt nach dem Absenden veraendert wurde
- Die Gueltigkeit des Zertifikats

Was koennen Sie mit der digitalen Unterschrift anfangen?


Die digitale Unterschrift verifiziert nicht nur den Absender. Sie als
Empfaenger haben jetzt die Moeglichkeit, Antworten an den Absender
verschluesselt ueber das Internet zu uebermitteln.

Bitte beachten:
---

Bevor Sie verschluesselt antworten koennen, muss die E-Mail-Adresse des
FreeMail-Anwenders in Ihr Adressbuch aufgenommen werden. Erst dann wird die
digitale Unterschrift lokal auf Ihrer Festplatte gespeichert und kann fuer
eine Verschluesselung herangezogen werden. Wenn Sie das genaue Verfahren
interessiert, koennen Sie das in der umfangreichen Hilfe bei
http://freemail.web.de nachlesen.

Verschluesselt antworten mit Netscape:
--

Ist die Adresse ins Adressbuch aufgenommen, klicken Sie bei der Antwort oder
beim neu schreiben einer Nachricht an den FreeMail-Anwender auf den
Menuepunkt Sicherheit, bzw. auf das grafische Symbol des Schlosses in der
Menueleiste. Waehlen Sie hier "Diese Nachricht verschluesseln".

Verschluesselt antworten mit Outlook Express:
-

Ist die Adresse in Ihrem Adressbuch gespeichert, finden Sie beim antworten
bzw. neu schreiben einer Mail an diesen FreeMail-Anwender in der Menueleiste
von Outlook Express ein neues Symbol - das Schloss. Ein Klick aufs Schloss
verschluesselt die Nachricht. Bitte beachten Sie den naechsten Hinweis:
Verschluesselte Mails koennen nur noch vom richtigen Empfaenger gelesen
werden - in Ihrem Ordner "gesendete Mails" kann diese Nachricht dann nicht
mehr gelesen werden.

Andere E-Mail-Programme:


Grundsaetzlich funktioniert dieses System bei allen S/MIME faehigen
E-Mail-Programmen. Die digitale Unterschrift kann nicht benutzt werden, wenn
Sie Ihre E-Mails mit dem in den T-Online-Decoder eingebauten E-Mail-Programm
abrufen. T-Online bietet Ihnen allerdings die Moeglichkeit, E-Mails aus dem
Internet ueber PoP3 abzurufen - ein Standardverfahren im Internet. Naehere
Informationen dazu entnehmen Sie den Hilfefunktiionen von T-Online.

Bei AOL funktioniert das S/MIME Protokoll leider gar nicht. Dieses Problem
laesst sich auch nicht ueber den Umweg PoP3 umgehen. AOL-Anwender koennen
von daher keine digital unterschriebene E-Mail aus dem Internet empfangen.

Mit freundlichen Gruessen,

Ihr WEB.DE Team.


-

In the next few minutes you are going to receive a digitally signed email
from a FreeMail-user. To enable your email-program to verify the identity of
this user, you have to install the "root-certificate" of WEB.DE.
Therefore please click on:

http://trust.web.de/root.sql

On this web-site you will find detailed instructions for installing the
certificate of WEB.DE into your email-program.

The details:

FreeMail, the free of charge web-based email-service of WEB.DE
(http://web.de), offers the possibility of sending digitally signed and
encrypted messages. If a FreeMail-user sends 

Build problem on sparc [ogle, assembler error]

[Mikael Hedin]

Hi again!

[Thanks for the help, ia64 now builds fine] 

This time it's sparc that don't build.  See the build log for details,
http://buildd.debian.org/fetch.php?&pkg=ogle&ver=0.8.2-4&arch=sparc&stamp=1011076373&file=log&as=raw,
 

And a snip:

gcc -DPACKAGE=\"ogle\" -DVERSION=\"0.8.2\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DWORDS_BIGENDIAN=1 -DHAVE_BYTESWAP_H=1 
-DHAVE_XSHM=1 -DHAVE_XV=1 -DHAVE_CLOCK_GETTIME=1 -DHAVE_MADVISE=1 -DLIBAO_OSS= 
-DHAVE_XML=1 -DHAVE_XF86VIDMODE=1 -DCONFIG_FILE=\"/usr/share/ogle/oglerc\" 
-DUSE_SPARCASM=1 -I. -I. -I. -I.. -I../include -g -O2 -Wall -mcpu=ultrasparc 
-mvis -c msgevents.c -Wp,-MD,.deps/msgevents.TPlo  -fPIC -DPIC -o 
.libs/msgevents.o
/tmp/ccMkcRE8.s: Assembler messages:
/tmp/ccMkcRE8.s:605: Error: Architecture mismatch on "bne,pt %icc,.LL130".
/tmp/ccMkcRE8.s:605:  (Requires v9|v9a|v9b; requested architecture is 
sparclite.)
/tmp/ccMkc

Is this a problem with gcc?  There is no assembly in msgevents.c.

/Micce

-- 
Mikael Hedin, MSc   +46 (0)980 79176
Swedish Institute of Space Physics  +46 (0)8 344979 (home)
Box 812, S-981 28 KIRUNA, Sweden+46 (0)70 5891533 (mobile)
[gpg key fingerprint = 387F A8DB DC2A 50E3 FE26  30C4 5793 29D3 C01B 2A22]

Re: pcmcia-modules in woody

[Tomas Pospisek's Mailing Lists]

On Tue, 15 Jan 2002, martin f krafft wrote:

> also sprach Lauri Tischler <[EMAIL PROTECTED]> [2002.01.15.1240 +0100]:
> > pcmcia-modules for kernels 2.19 and 2.20 dont exist.
> > Whats up duck ?
>
> pcmcia-modules have, AFAIK, been discontinued.

There's been a pcmcia-modules release for 2.4.17 though.
*t


 Tomas Pospisek
 SourcePole   -  Linux & Open Source Solutions
 http://sourcepole.ch
 Elestastrasse 18, 7310 Bad Ragaz, Switzerland
 Tel: +41 (81) 330 77 11

Re: Build problem on sparc [ogle, assembler error]

[Allan Sandfeld Jensen]

On Tuesday 15 January 2002 14:14, Mikael Hedin wrote:
> Hi again!
>
> [Thanks for the help, ia64 now builds fine]
>
> This time it's sparc that don't build.  See the build log for details,
> http://buildd.debian.org/fetch.php?&pkg=ogle&ver=0.8.2-4&arch=sparc&stamp=1
>011076373&file=log&as=raw,
>
> And a snip:
>
> gcc -DPACKAGE=\"ogle\" -DVERSION=\"0.8.2\" -DSTDC_HEADERS=1
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1
> -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1
> -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DWORDS_BIGENDIAN=1
> -DHAVE_BYTESWAP_H=1 -DHAVE_XSHM=1 -DHAVE_XV=1 -DHAVE_CLOCK_GETTIME=1
> -DHAVE_MADVISE=1 -DLIBAO_OSS= -DHAVE_XML=1 -DHAVE_XF86VIDMODE=1
> -DCONFIG_FILE=\"/usr/share/ogle/oglerc\" -DUSE_SPARCASM=1 -I. -I. -I. -I..
> -I../include -g -O2 -Wall -mcpu=ultrasparc -mvis -c msgevents.c
> -Wp,-MD,.deps/msgevents.TPlo  -fPIC -DPIC -o .libs/msgevents.o
> /tmp/ccMkcRE8.s: Assembler messages:
> /tmp/ccMkcRE8.s:605: Error: Architecture mismatch on "bne,pt %icc,.LL130".
> /tmp/ccMkcRE8.s:605:  (Requires v9|v9a|v9b; requested architecture is
> sparclite.) /tmp/ccMkc
>
> Is this a problem with gcc?  There is no assembly in msgevents.c.

Gcc is really broken for -mcpu on sparcs.. What you need to do here is either 
drop ultrasparc optimizations or manually propagate the arch parameter to the 
assembler.  The last is done with -Wa,-xarch=v8plusa

-Allan

Re:

[Jules Bean]

On Tue, Jan 15, 2002 at 01:56:39PM +0100, Anton Feldmann wrote:
> Sehr geehrte Programm bereitsteller,
> 

> mein Name ist Anton Feldmann. Ich hätte gerne von ihnen gewust wann
> woody frozen ist.

Guten Tag.  This is an english-language mailing list; please post in
English here.

The woody freeze has started, but progress is currently slow.  I would
be inclined to estimate that it won't be ready for Easter, but might
be for summer.

Jules

Re:

[martin f krafft]

hallo supamann,

also sprach Anton Feldmann <[EMAIL PROTECTED]> [2002.01.15.1356 +0100]:
> Sehr geehrte Programm bereitsteller,
^
wunderschoen. beautiful word. available-maker. tztztz

> mein Name ist Anton Feldmann. Ich hätte gerne von ihnen gewust wann
> woody frozen ist.

wenn's fertig ist. ganz einfach. genaueres koennen wir nicht sagen, denn
dann wuerden wir uns unter zeitdruck stellen, und im endeffekt genauso
muell wie andere namenhafte hersteller rausgeben. wir haben woody ja
absichtlich nicht Debian 2001 genannt ;)

woody will be frozen when it's done. we can't be more exact, or we'll
submit ourselves to time pressure, and then end up producing trash like
other distributors. there's a reason why woody isn't called Debian 2001
;)

-- 
martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
  
micros~1: for when quality, reliability, and security
  just aren't that important!


pgpvQBWBzTg5F.pgp
Description: PGP signature

WELCOME to divx@lists.divx.com

[divx-help]

===
THIS EMAIL CONIFIRMS YOUR SUBSCRIPTION TO THE DIVX NEWS
NEWSLETTER. PLEASE READ IT FOR IMPORTANT INFORMATION.
===

Welcome and thank you for subscribing to the DivX News. We
have received a request to subscribe the following email
address to our newsletter:

   debian-devel@lists.debian.org

(If you think you have been subscribed to this newsletter
in error, please follow the unsubscribe instructions at
the end of this message.)

The DivX News is a low-traffic announcement list and is
usually sent about once a week. Every issue will bring you
information about the latest DivX(tm) software releases
and other DivX(tm)-related news, downloads, and videos.

In between issues, you can always find up-to-date
information at DivX.com:

* Newest software: 
* Cool videos: 
* Latest news: 
* Conversation and community: 
* Help and tech support: 

We hope you find the newsletter useful and enjoyable, but
if you ever decide you don't want to continue to receive
it (or if you feel like this confirmation email was sent
in error), you can unsubscribe by following the
instructions at the end of this message.

Thanks again for subscribing.

Cheers.

The DivX Team

---
YOUR PRIVACY
---
Our DivX.com privacy policy forbids us from divulging your
personal information without your express permission, so
there's never a need to worry.

---
UNSUBSCRIBING
--- 
If you do not wish to receive future emails at 
   debian-devel@lists.debian.org
just visit this web page to unsubscribe: 
. Alternately, 
you can send an email message to <[EMAIL PROTECTED]>.

---
MORE QUESTIONS?
--- 
If you have any questions or comments, or would like more
information, please email us at <[EMAIL PROTECTED]>.

Visit DivX.com: The Home of DivX(tm) Video Technology

Copyright (c) 2001 DivXNetworks, Inc. 
DivX is a trademark of DivXNetworks, Inc.


Included below you will find a copy of your subscription 
request. If you didn't subscribe for this newsletter, 
and you suspect someone may be misusing your account, we 
will need the information below to make sure it doesn't 
happen again.



Return-Path: 
Received: (qmail 20842 invoked from network); 15 Jan 2002 08:46:07 -
Received: from ns1.divxnetworks.com (HELO ns1.bur.divxlibrary.com) 
(66.77.127.85)
  by mranderson.divxnetworks.com with SMTP; 15 Jan 2002 08:46:07 -
Received: (qmail 8146 invoked from network); 15 Jan 2002 14:02:05 -
Received: from fp1-024i.bur.divxlibrary.com (HELO divxnetworks.com) (10.2.1.24)
  by ns1i.bur.divxlibrary.com with SMTP; 15 Jan 2002 14:02:05 -
Received: (qmail 31811 invoked by uid 33); 15 Jan 2002 14:02:11 -
Date: 15 Jan 2002 14:02:11 -
Message-ID: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
Cc: recipient list not shown: ;

GOODBYE from divx@lists.divx.com

[divx-help]

===
THIS EMAIL CONIFIRMS YOUR REMOVAL FROM THE DIVX NEWS
NEWSLETTER. PLEASE READ IT FOR IMPORTANT INFORMATION.
===

We have received your request to unsubscribe the following
email address from the DivX News newsletter:

   debian-devel@lists.debian.org

We're sorry to see you go, but everyone (including us)
gets too much email these days, so we understand if you
want to receive one fewer message.

But if there is something specific that you didn't like
about the newsletter and that caused you to unsubscribe,
please let us know about it at <[EMAIL PROTECTED]>.
Your feedback will help us to improve.

If you ever decide that you want to receive the DivX News
again, or if you feel like this message was sent in error
and you were removed accidentally, you can re-subscribe to
the newsletter by following the instructions at the end of
this message.

Take care, and we hope to see you again soon.

The DivX Team

---
YOUR PRIVACY
---
Even though you've left our newsletter, rest assured that
your personal information is still safe. Our DivX.com
privacy policy forbids us from divulging your personal
information without your express permission.

---
SUBSCRIBING
--- 
If you would like to continue to receive the DivX News
newsletter, you can send an email message to 
<[EMAIL PROTECTED]>.

---
MORE QUESTIONS?
--- 
If you have any questions or comments, or would like more
information, please email us at <[EMAIL PROTECTED]>.

Visit DivX.com: The Home of DivX(tm) Video Technology

Copyright (c) 2001 DivXNetworks, Inc. 
DivX is a trademark of DivXNetworks, Inc.



Return-Path: 
Received: (qmail 21780 invoked from network); 15 Jan 2002 08:55:35 -
Received: from ns1.divxnetworks.com (HELO ns1.bur.divxlibrary.com) 
(66.77.127.85)
  by mranderson.divxnetworks.com with SMTP; 15 Jan 2002 08:55:35 -
Received: (qmail 9497 invoked from network); 15 Jan 2002 14:11:34 -
Received: from fp1-027i.bur.divxlibrary.com (HELO divxnetworks.com) (10.2.1.27)
  by ns1i.bur.divxlibrary.com with SMTP; 15 Jan 2002 14:11:34 -
Received: (qmail 20370 invoked by uid 33); 15 Jan 2002 14:11:40 -
Date: 15 Jan 2002 14:11:40 -
Message-ID: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
Cc: recipient list not shown: ;

Re: About sponsoring non-free packages

[Steve Langasek]

On Tue, Jan 15, 2002 at 06:06:50AM -0600, Colin Watson wrote:
> On Mon, Jan 14, 2002 at 01:04:10PM +0100, J?r?me Marant wrote:
> >   I propose that we do not sponsor people for non-free packages.
> >   People that we want to join us and seeking sponsors for
> >   non-free package are showing that they do not understand
> >   our philosophy and dedication to Free Software. 

> One of my initial packages was non-free (still is, although I hold out
> hope for a licence change at some point). I suggest that a better policy
> is closer to this:

>   New maintainers applying as packagers should contribute something to
>   main as part of their tasks and skills check. This could either be new
>   packages or adopting existing ones. They may submit work they've done
>   in contrib or non-free, which may help the AM judge their packaging
>   abilities, but this work should not be considered sufficient to pass
>   the check.

> I wouldn't have objected to this when I was applying - I had packages in
> main too.

Perhaps to ensure that the tasks & skills check still means something, 
there should be some quantifying of just how bad an existing package has 
to be to qualify -- e.g., a given number of policy violations in the 
packaging, a standards version below such and such a version.

Other than that, I certainly agree.  Fixing a piece of unmaintained free
software is usually more important to the quality of the distro than 
introducing another piece of non-free software, or even introducing 
another piece of /free/ software that will be used by few people.  While 
there's merit in requiring NMs to create packages from scratch because 
it means understanding the process from start to finish, there's lots of 
work to be done in Debian -- such as QA -- that doesn't involve creating 
new packages.

Steve Langasek
postmodern programmer


pgpJSE0PUMxfK.pgp
Description: PGP signature

Re: MusixTex for arm and sh architecture

[Martin Schulze]

Tille, Andreas wrote:
> Hello,
> 
> second call for help to compile MusixTex on all architectures:
> 
> auric:~> madison musixtex
>   musixtex |   1:0.98-1 |stable | source, alpha, arm, i386, m68k, 
> powerpc, sparc
>   musixtex |   1:0.99-1 |   testing | source, arm, ia64, m68k, powerpc, 
> sparc
>   musixtex |   1:0.99-1 |  unstable | arm, sh
>   musixtex |  1:0.102-1 |  unstable | source, alpha, hppa, i386, ia64, 
> m68k, powerpc, s390, sparc
> 
> Please could someone compile musixtex on arm and sh.

sh is somewhat deprecated at the moment due to a required
decision wrt. sh3/sh4 and big/little endianess.  No buildd
is currently running for binary-sh because of this.  Just
stay tuned, the port will eventually continue.

Regards,

Joey

-- 
The MS-DOS filesystem is nice for removable media.  -- H. Peter Anvin

Please always Cc to me when replying to me on the lists.

Re: MusixTex for arm and sh architecture

[Tille, Andreas]

On Tue, 15 Jan 2002, Martin Schulze wrote:

> sh is somewhat deprecated at the moment due to a required
> decision wrt. sh3/sh4 and big/little endianess.  No buildd
> is currently running for binary-sh because of this.  Just
> stay tuned, the port will eventually continue.
I really do not care about sh.  I'm just hoping that somebody will
build MusixTex for arm and that MusixTex would go into testing then.

Kind regards

Andreas.

Re: mindi fails on Linux Debian system

[Wichert Akkerman]

Lets take [EMAIL PROTECTED] of the cc list, this is not an abuse
complaint. Lets add debian-devel since this actually is a normal
technical question.


Previously Kenneth H. Carpenter wrote:
> I have been using the Debian distribution since it first came out, and
> I appreciate the effort that has been made to make it robust and keep it
> "free."  But I think it would be helpful if Debian did not change the
> entry points for standard utilities so that ones wanting to add software
> not in Debian would not have to be aware of these changes.

In this case it seems a wrapper was added to work around some devfs
issues, but it calls the actual lilo with the exact options you gave
it. Can you explain how exactly that broke mindi? Once we know
exactly what the problems is we can look at fixing it.

Wichert.

-- 
  _
 /[EMAIL PROTECTED] This space intentionally left occupied \
| [EMAIL PROTECTED]http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |

Re: About sponsoring non-free packages

[Jérôme Marant]

Colin Watson <[EMAIL PROTECTED]> writes:

> One of my initial packages was non-free (still is, although I hold out
> hope for a licence change at some point). I suggest that a better policy
> is closer to this:
> 
>   New maintainers applying as packagers should contribute something to
>   main as part of their tasks and skills check. This could either be new
>   packages or adopting existing ones. They may submit work they've done
>   in contrib or non-free, which may help the AM judge their packaging
>   abilities, but this work should not be considered sufficient to pass
>   the check.

  I second this. You perfectly expressed what I had in mind.

  Cheers,

-- 
Jérôme Marant

Re: Please don't do this (code fragment)

[elf]

Good grief.  Can you be more constructive?  Do you have a reference
that supports the claim?

On Tue, Jan 15, 2002 at 12:11:35AM -0800, Thomas Bushnell, BSG wrote:
> [EMAIL PROTECTED] writes:
> 
> > I don't find any such mention in K&R [1978].  There is nothing I can
> > see to guarantees that MAX_INT + 1 < 0.
> 
> K&R [1978] is not the C standard.

[±¤°í] 1/4 ½ÇÁ÷ÀÚ ¹«·áIT±³À°

[ITÀü¹®Çб³]

Title: ::: The 2002 1/4 IT Specialist Course :::









































▒ 국내 최고의 CIW 국제공인 전문가들이 전수하는 생생한 실무 교육
▒ 실무 Process를 총망라하여 체계적으로 접근
▒ 다양한 Case Study와 현장 실습 등을 통한 실용적 학습 체제
▒ 6개월 간의 전문가 양성교육 










노동부
지원의 고학력 미취업자 대상의 실무위주 교육















◈인터넷 비지니스 프로그래밍 교육 과정
포토샵,드림위버,JSP,ASP/MS-SQL,WIN NT서버구축,CIW BASIC/ADVANCE,CIW INTERNET,NETWORKING,LINUX,자바스크립트,JAVA,C언어,일러스트,운영체계,인터넷/네트워크개론,WIN98활용,플래쉬,HTML/DHTML
◈웹 디자인 교육 과정
디자인일반/마케팅,색채 및 도법.디자인 재료,컴퓨터 그래픽스,HTML,GIF,ANIMATRO,포토샵,인터넷
활용/정보검색,드림위버,플래시,자바스크립트,3DMAX,이미지레디,일러스트,페이지메이커













1. 교육기간
◈인터넷 비지니스 프로그래밍 교육 과정
- 2002년 2월 18일(월) ~ 2003년 2월 17일(월) (1년)
- 월, 화, 수, 목, 금 09:00 ~ 17:00 (총 2008시간)

◈웹 디자인 교육 과정
- 2002년 1월 23일(수) ~ 2002년 7월 18일(목) (6개월)
- 월, 화, 수, 목, 금 09:00 ~ 17:00 (총 960시간)

2. 교육장소
강북IT전문학교 (1호선 신설동역 3번출구 / 도보 2분거리)

3. 모집인원 및 대상
- 모집인원 : 30명 (선착순 마감)
- 교육대상 : 고졸 및 대졸 미취업자 우선 선발, 단 고용보험 가입자에 한함

4. 교육비
- 무료 , 단 일부 본인 부담금 있음
- 매달 5만원 가량의 훈련수당 지급
  
5. 신청방법
- 원서교부 및 접수처 : 강북IT전문학교 교육사업팀 
- Tel : 02) 922-3445 담당자 : 문찬수
- Fax : 02) 922-3446
- E-mail : [EMAIL PROTECTED]
- 제출서류 : 참가원서 (소정양식), 사진 3매,주민등록등본2통,통장사본

 












▒ 수료후 전원 취업추천
▒ 강북IT전문학교 수료증 수여
▒ 홈페이지에 자격취득자 명단 게재
    (희망자에 한해 간단한 소개 페이지도 제공)
▒ On-line Community를 통한 상시 정보교류 및 네트워킹 지원
▒ Off-line 정기 모임 주선
▒ 관련 세미나 등을 통한 지속적 정보습득의 기회 제공
▒ 교육 시 훈련수당 매달 지금
▒ 교재 무료 지급 

 












- 강북IT전문학교 교육사업팀
- Tel : 02) 922-3445 담당자 : 문찬수
- Fax : 02) 922-3446
- 홈페이지 : http://www.kangbuk.or.kr
- E-mail   : [EMAIL PROTECTED]










본 메일에 대한 수신을 거부하시는 분들은 여기를 클릭하여 주시면 감사하겠습니다.
본 E-mail은 전산망 보급확장과 이용촉진에 관한 법률에 의거하여
수신자가 [수신거부] 의사를 회신으로 밝힌 후에는 다시 보내지 않습니다. 메일주소 외엔 아무런 정보도 가지고 있지 않으며
바쁘신 귀하를 번거롭게 해서 죄송합니다. 좋은하루 되십시요!!






ⓒCopyright
1992-2002 Kangbuk IT Special Professional School. All rights
reserved.
서울특별시 동대문구 신설동 89-79 문성빌딩 
Tel :02-922-3445 Fax :02-922-3446

Re: pcmcia-modules in woody

[Brian Mays]

Lauri Tischler <[EMAIL PROTECTED]> wrote:

> pcmcia-modules for kernels 2.19 and 2.20 dont exist.

A set of pcmcia-modules-2.2.20 packages do exist.  I uploaded a new set
of these packages yesterday to sid.  As for the packages in woody, I
have no control over that.  I wish the archive maintainers would replace
the outdated packages in woody, but they never do.  If you would like to
help, file bugs against "ftp.debian.org" asking them to move the newer
packages into woody.

If anyone knows how to get packages into woody, please let me know.
It's a complete mystery to me.

[EMAIL PROTECTED] (martin f krafft) replied:

> pcmcia-modules have, AFAIK, been discontinued. these days, you have
> to get pcmcia-source and kernel-source, and compile them yourself.
> it's actually a real pain, but with the variety and sheer number
> of kernel-images, it would be impossible to keep up to date on all
> *-modules packages. it seems that alsa-modules is still doing that
> though.

The pcmcia-modules packages have not been discontinued.  I continue to
build packages to accompany the latest kernel-image packages for the
2.2 and 2.4 series kernels.  This means that I have built six packages
for the 2.2.20 kernels and one for the 2.4.17 kernel using the latest
version of pcmcia-cs.

I have neither the time nor the resources, however, to build packages
for all of the kernel-image packages out there (last time I counted
there were 27 of these packages).  Anyone willing to build these
packages is welcome to do so.  I have tried to automate and document the
procedure as much as possible, and I am willing to provide advice and
assistance to anyone willing to try.

Fortunately, some of the maintainers of the kernel-image packages are
nice enough to also build a new pcmcia-modules package to accompany a
new version of their packages.  That certainly helps.

- Brian

[홍보] 네티즌이 만든 검색엔진 아이따따따입니다.

[아이따따따]

Title: 검색엔진 아이따따따





   

 
  
 
  

 
  

 
   

   
 
  
 
   

 
    인터넷에는 많은 정보와 그 정보를 찾아주는 검색엔진이 있습니다.
  하지만 검색엔진들이 너무나 많은 정보를 제공해 주는 결과 오히려 정보를 찾는데 많은 노력과 시간을  
  허비하는 결과를 초래하고 있습니다. 


 
  
  이제는 얻을 수 없는 많은 양의 검색결과보다는 신뢰성 있는 정보를 요구하는 시대가 되었습니다.  
  인터넷에 산재해 있는 사이트 중에는 우리가 꼭 필요한 정보들을 담고 있는 사이트가 많이 있는데,   
  이 사이트 들을 구분하면 포탈,보탈,허브 사이트라고 합니다.  


 
  
  아이따따따는 이런 사이트를 찾아주는 카테고리 및 키워드 검색엔진입니다.  
  각 카테고리 별로 신뢰성 있는 엄선된 사이트만 네티즌의 양심으로
등록관리하는 검색엔진이며
  귀하께서도 카테고리 담당자가 되실 수 있습니다.


  카테고리 담당이 되시면 ㈜아이엔웹의 주식 1주를 무상으로 드리며 pop3 e-mail 계정을 드립니다.  
  ("예" [EMAIL PROTECTED]")   
  또한,그 카테고리를 관리할 수 있는 권한과 해당 카테고리에 담당자 아이디를 등록합니다.   
  (등록신청을 하신후 담당관리자로 login 하시면 카테고리를 직접 관리하실 수 있습니다.)   

  회원가입을 하시고 회원이 되시면 ㈜ 아이엔웹의 주식 1주를 무상으로 드립니다.  
  인터넷은 네티즌이 주인이고 아이따따따는 네티즌의 것이기 때문입니다! 




  
  
  http://iwww.net (아이따따따)로 방문해 주세요

  
  
  아이따따따의 이념은 우리 네티즌이 갖고있는 유익한 정보를 서로 공유하고 새로운 네티즌문화를 
  창출하는것입니다. 귀하께서도 아이따따따의 한 가족이 되어주시길 부탁드립니다.

  늘 건강하시고 행복하세요~~~감사합니다.




  


  
   
 

 
  
  
  
  

 
   
  1일 평균 방문
   
  774,500 hit(2002.01.13)


 
  
  
  
  

 
   
  가입회원
   
  156,550 (2002.01.13)


   
 
  
  
  
  

 
   
  네티즌 담당 카테고리
   
  
785 개


  
  
   
 
  
  직접 방문하셔서 평가해 주십시오! ==>http://iwww.net
유익한 사이트라고 평가되시면 
  주위분들에게 알려주시길바랍니다. ( 아이따따따 = iwww )


  

 
  

  


  
  

  귀하께 불편을 끼쳐 드렸다면 용서를 바랍니다.

  귀하의 메일은 인터넷에서 웹서핑중 취득하였으며 귀하의 어떠한 정보도 갖고있지 않습니다.
  다음부터는 인터넷,정보통신,바이러스백신 등 유익한 정보만을 보내드립니다. 
  아이따따따의 가족이 되시면 전체가족 메일을 통하여 유익한 정보를 받아보실 수 있습니다.
  공지사항을 참고하시면 아이따따따 내부사정을 아실 수 있습니다.
 바로가서 보기
  네티즌의 고견을 수렴하는 공개게시판을 운영중입니다.
바로가서 보기
  
  그래도 수신을 원치 않으실 경우 수신거부를 클릭하십시오!

수신거부 
  

  


  


  

  

Re: Please don't do this (code fragment)

[Olaf Weber]

Thomas Bushnell writes:

> Actually, the C standard does essentially guarantee two's complement
> arithmetic.  It specifies integer overflow behavior and
> signed/unsigned conversion behavior exactly.

It does for unsigned integers, but for signed integers overflow is
undefined behaviour.  The clearest statement of that is 3.4.3, albeit
in an example:

   3.4.3
 1 undefined behavior behavior, upon use of a nonportable or erroneous
   program construct or of erroneous data, for which this International
   Standard imposes no requirements
 2 NOTE Possible undefined behavior ranges from ignoring the situation
   completely with unpredictable results, to behaving during translation
   or program execution in a documented manner characteristic of the
   environment (with or without the issuance of a diagnostic message),
   to terminating a translation or execution (with the issuance of a
   diagnostic message). 
 3 EXAMPLE An example of undefined behavior is the behavior on integer
   overflow.

-- 
Olaf Weber

   (This space left blank for technical reasons.)

Re: Vanishing /usr/doc symlink

[Adam Heath]

On Tue, 15 Jan 2002, Colin Watson wrote:

> On Tue, Jan 15, 2002 at 11:01:35AM +0100, Santiago Vila wrote:
> > Julian Gilbey wrote:
> > > I just upgraded my unstable system today.  In the process, my /usr/doc
> > > -> /usr/share/doc symlink disappeared.  I didn't notice till
> > > afterwards, but I'm pretty sure that's what did it.  (It was there
> > > yesterday, and it's unlikely to have been anything else.)
> > >
> > > Below is the diff between yesterday and today's dpkg -l \* | grep ^ii
> > > output; I haven't had a chance to examine all of these packages,
> > > though.  Anyone have any ideas which package might be guilty for doing
> > > this?
> >
> > Every of them. None of them. Most probably, you just happened to
> > remove or upgrade the last package containing /usr/doc in your system,
> > and, as a result, dpkg removed it, since it was not a non-empty directory.
>
> What happened to the transition plan that said we'd ship woody with a
> /usr/doc full of symlinks, not no /usr/doc at all?

Nothing.  Note that Julian had a /usr/doc -> share/doc symlink.  He didn't
have a /usr/doc directory.

I'm not certain what dpkg would do in this case, when no more packages are in
/usr/doc, and it is a symlink.

Re: potential runtime problem on arm, powerpc and s390 due to incorrect assumption on char signedness

[Colin Walters]

On Mon, 2002-01-14 at 21:41, Peter Cordes wrote:

>  For software with problems like that all over the place, you could use
> gcc -fsigned-char [...]

Nooo!  This is a bad idea, unless you're in a freestanding environment,
and even then it should be avoided.  See the previous thread.

Re: pcmcia-modules in woody

[Adrian Bunk]

On Tue, 15 Jan 2002, Brian Mays wrote:

> Lauri Tischler <[EMAIL PROTECTED]> wrote:
>
> > pcmcia-modules for kernels 2.19 and 2.20 dont exist.
>
> A set of pcmcia-modules-2.2.20 packages do exist.  I uploaded a new set
> of these packages yesterday to sid.  As for the packages in woody, I
> have no control over that.  I wish the archive maintainers would replace
> the outdated packages in woody, but they never do.  If you would like to
> help, file bugs against "ftp.debian.org" asking them to move the newer
> packages into woody.
>
> If anyone knows how to get packages into woody, please let me know.
> It's a complete mystery to me.

It seems there need to happen at least three things until the new pcmcia-*
packages can go into woody:
1. the obsolete packages for older images must be removed by the ftp
   masters from unstable -> you should file a bug against ftp.debian.org
   asking for the removal of these packages from unstable (unfortunately
   this must be done by hand by the ftp admins)
2. the packages in unstable must be built at least on all four
   architectures (alpha, arm, i386, powerpc) they were ever built on -
   including all binary packages that were ever built from this source
   package on these architectures (for binary packages that do no longer
   exist on an architecture see 1.)
3. the two RC bugs (#110719 and #119837) must be fixed


You should perhaps start with fixing the RC bugs instead of bugging the
ftp admins - without them fixed your package will never go into testing...


> The pcmcia-modules packages have not been discontinued.  I continue to
> build packages to accompany the latest kernel-image packages for the
> 2.2 and 2.4 series kernels.  This means that I have built six packages
> for the 2.2.20 kernels and one for the 2.4.17 kernel using the latest
> version of pcmcia-cs.
>
> I have neither the time nor the resources, however, to build packages
> for all of the kernel-image packages out there (last time I counted
> there were 27 of these packages).  Anyone willing to build these
> packages is welcome to do so.  I have tried to automate and document the
> procedure as much as possible, and I am willing to provide advice and
> assistance to anyone willing to try.
>
> Fortunately, some of the maintainers of the kernel-image packages are
> nice enough to also build a new pcmcia-modules package to accompany a
> new version of their packages.  That certainly helps.

BTW: It's _extremely_ ugly to build these binary pacakges in a way that a
 "dpkg-buildpackage -B" doesn't rebuild them all.

> - Brian

cu
Adrian

Re: Build problem on sparc [ogle, assembler error]

[Ben Collins]

On Tue, Jan 15, 2002 at 02:14:07PM +0100, Mikael Hedin wrote:
> Hi again!
> 
> [Thanks for the help, ia64 now builds fine] 
> 
> This time it's sparc that don't build.  See the build log for details,
> http://buildd.debian.org/fetch.php?&pkg=ogle&ver=0.8.2-4&arch=sparc&stamp=1011076373&file=log&as=raw,
>  
> 
> And a snip:
> 
> gcc -DPACKAGE=\"ogle\" -DVERSION=\"0.8.2\" -DSTDC_HEADERS=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DWORDS_BIGENDIAN=1 -DHAVE_BYTESWAP_H=1 
> -DHAVE_XSHM=1 -DHAVE_XV=1 -DHAVE_CLOCK_GETTIME=1 -DHAVE_MADVISE=1 
> -DLIBAO_OSS= -DHAVE_XML=1 -DHAVE_XF86VIDMODE=1 
> -DCONFIG_FILE=\"/usr/share/ogle/oglerc\" -DUSE_SPARCASM=1 -I. -I. -I. -I.. 
> -I../include -g -O2 -Wall -mcpu=ultrasparc -mvis -c msgevents.c 
> -Wp,-MD,.deps/msgevents.TPlo  -fPIC -DPIC -o .libs/msgevents.o
> /tmp/ccMkcRE8.s: Assembler messages:
> /tmp/ccMkcRE8.s:605: Error: Architecture mismatch on "bne,pt %icc,.LL130".
> /tmp/ccMkcRE8.s:605:  (Requires v9|v9a|v9b; requested architecture is 
> sparclite.)
> /tmp/ccMkc

I'll repeat this many times over. DO NOT USE cpu optimizations in Debian
packages! IOW, remove the -mcpu=ultrasparc line. It is not fully
supported in gcc, and not to mention that if it did work, it would break
the package on sparc32 platforms.


Ben

-- 
 .--===-=-==-=---==-=-.
/   Ben Collins--Debian GNU/Linux  \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'

Re: mindi fails on Linux Debian system

[Ben Collins]

On Tue, Jan 15, 2002 at 05:20:14PM +0100, Wichert Akkerman wrote:
> Lets take [EMAIL PROTECTED] of the cc list, this is not an abuse
> complaint. Lets add debian-devel since this actually is a normal
> technical question.
> 
> 
> Previously Kenneth H. Carpenter wrote:
> > I have been using the Debian distribution since it first came out, and
> > I appreciate the effort that has been made to make it robust and keep it
> > "free."  But I think it would be helpful if Debian did not change the
> > entry points for standard utilities so that ones wanting to add software
> > not in Debian would not have to be aware of these changes.
> 
> In this case it seems a wrapper was added to work around some devfs
> issues, but it calls the actual lilo with the exact options you gave
> it. Can you explain how exactly that broke mindi? Once we know
> exactly what the problems is we can look at fixing it.

The problem is that it creates a rootfs (I believe) and copies
/sbin/lilo blindly to the new rootfs. Thus, you just have a broken shell
script.

-- 
 .--===-=-==-=---==-=-.
/   Ben Collins--Debian GNU/Linux  \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'

Re: Build problem on sparc [ogle, assembler error]

[James Troup]

Mikael Hedin <[EMAIL PROTECTED]> writes:

> Is this a problem with gcc?

No, it's a problem with ogle.  -mcpu=ultrasparc is like
unconditionally compiling an i386 binary for Pentium 4's only,
i.e. not a good idea.  The buildd pretends it's not really an
UltraSPARC for exactly this reason.

-- 
James