Horrible console fonts in 11.0 stable

2017-03-11 Thread Lars Eighner
What is with the horrible console fonts in 11.0 stable? I have tried them 
all and they are each more hiddeous than the other.


Is there anyway to get the VGA fonts back. I never want any characters 
outside of Latin I.


Text programs are the only reason I use FreeBSD (it sure is not for the 
pathetic X.org). How can anyone work with the horrible text fonts which I 
suspect are some horrible raster fonts which reset video every time I 
switch virtual terms?




--
Lars Eighner
stableu...@larseighner.com
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Can I get an ISO-8859-1 system back

2016-01-05 Thread Lars Eighner
I upgraded from 9.? to 10.2. I used a custom kernel to avoid vt and raster 
fonts in sc. I updated as many ports as would build.


Now I cannot find an editor that will display my files with accent 
characters correctly. I know the files are still iso-8859-1 because they 
are the same size they were and when I cat them, they have the right 
characters in them. This also shows that my term (cons25l1) can display 
the characters correctly. But joe, joe2, ee, and pico-alpine seem to 
convert them to some kind of UTF mess, with two bytes which display as grey 
blocks.


I have tried using LC_ALL and LANG as en_US.iso-8859-1 in .login_conf, and 
unsetting them, I have tried several screen maps.



How far back do I have to downgrade to eliminate UTF from my system 
entirely? I don't care if I can't run a gui. I just want an editor that 
will open iso-8859-1 as iso-8859-1 and not any 2-byte whatever, and will 
display accented characters correctly, as cat does.


I will never want to use sanskrit or Chinese characters. I just want 
Western European characters and I do not want to waste two bytes on them.
I want to use the VGA characters, which the experiment with cat 
demonstrates are on my video card and do work. I do not want unreadable

raster fonts.


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: Why Are You Using FreeBSD?

2012-05-30 Thread Lars Eighner

On Wed, 30 May 2012, David Chisnall wrote:


Hi Everyone,



I came to FreeBSD nearly 20 years ago because it had text-mode (aka command
line, console, etc.) apps and I wanted to avoid GUIs for applications that
are not essentially graphic in nature.  The ability to switch for
applications essentially graphic (paint, image manipulation, etc.) and back
for everything else (writing) without rebooting was very attractive.

There is not any graphics font that can put 2000 characters (80x25) on one
screen legibly - and that has not changed.  The native editors on BSD (vi,
emacs) are pretty horrible -- imagine the Frankenstein that thought I'll
just write an editor in Lisp!  But once I discovered Joe, it was smooth
sailing.  There is no GUI file manager as good as lynx ./ .

This is still why I use FreeBSD.  I tried linuxes, but found keyboard
mapping really opaque.  Now, I won't use linuxes because they have abandoned
text-mode for rasterized text -- which is just as horrible as GUIs -- and
the linux distributions just assume you are trying to run Gnome, completely
ignoring formerly text-mode, now rasterized applications.

Unfortunately FreeBSD seems to be headed this way and I will have to hop off
the upgrade cycle at some version and hope that I die before it becomes
orphaned.

--
Lars Eighner
http://www.larseighner.com/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Bring sio up to 8+

2011-05-22 Thread Lars Eighner


It seems increasing unlikely that uart will ever support the only internal
hardware modem recently available in the US (PR kern/155196), so what are
the chances of sio (which works in 7.x reasonably well and better with a
one-line hack) being brought forward?



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Why is sio.c still broken?

2009-06-29 Thread Lars Eighner

I was about to trash a modem because the HDLC and buffer overflows were
grinding it to halt --- or just about.  I switch slots, changed the modem
out with and old 28.8, and so forth.


Eventually I discovered some really old stuff about sio.c which
suggested this:

cp4ticks = speed / 10 / hz * 4;

be changed to this.

cp4ticks = speed / 10 / hz * 40;

and everything worked like a charm

So I am wondering why this hasn't been changed since it seems to be
necessary for proper operation of just about the only non-winmodem
available.



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Why is sio.c still broken?

2009-06-29 Thread Lars Eighner

On Mon, 29 Jun 2009, Kevin Oberman wrote:


Date: Mon, 29 Jun 2009 06:12:43 -0500 (CDT)
From: Lars Eighner stableu...@larseighner.com
Sender: owner-freebsd-sta...@freebsd.org

I was about to trash a modem because the HDLC and buffer overflows were
grinding it to halt --- or just about.  I switch slots, changed the modem
out with and old 28.8, and so forth.


Eventually I discovered some really old stuff about sio.c which
suggested this:

cp4ticks = speed / 10 / hz * 4;

be changed to this.

cp4ticks = speed / 10 / hz * 40;

and everything worked like a charm

So I am wondering why this hasn't been changed since it seems to be
necessary for proper operation of just about the only non-winmodem
available.


Probably because sio is about to be dropped and no one has given it much
attention of late.

It's probably best to convert to use of uart which is the new serial
port driver and will be the only one in V8 which is in code freeze and
should be out in two or three months.

Let the I coulda had a V8 puns and bad jokes begin!



Any idea where there is info on how to do this?  Nothing in man uart is
helpful to me, and if it is the handbook, I can't find it.  I found a few
things about modems and ttys, but I want it for ppp.

Since it seems to work now, perhaps I better stop upgrading.

After all, umass upgrades may my camera useless (except as a way to panic
the system.  Some upgrade or another made the scanner and card-reading
functions on my printer useless.  I can't afford to up to the point that my
modem doesn't work.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5

2007-10-14 Thread Lars Eighner

On Sun, 14 Oct 2007, d_elbracht wrote:


we are trying to diagnose errors seen on 6.2, SMP, amd64, cvsup'ed of
2007-10-09

Mainboard is a Tyan Thunder h2000M (S3992-E) with 16 GB RAM and 2 x Opteron
2216, da3 is on a 3ware 9550-12

we are seeing this error:
g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5
on a 12 GB Hyperdrive


I trashed a perfectly disk drive before learning that there is a serious bug
in g_vfs.  Apparently it is one of those things which shows up in some
configurations and not others.  Although I am told they are unable to
isolate the problem, all the reports I've seen were from people using AMD
systems.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: File system is Full

2007-10-03 Thread Lars Eighner

On Wed, 3 Oct 2007, Khaled Moussa wrote:


My / slice
got full and I wonder if there might be any way increasing size
through free space on HD?


Yes, there is, and I see that someone has already replied calling your
attention to growfs.  However, there is almost certainly something wrong if
/ gets full.  You should find out what is filling / before you undertake any
remedy.

Some possible causes:

(Recently discussed) dumping to a mount point when in fact the dump device
is not mounted.

/tmp not a separate file system and something using too much /tmp

Running as root, instead of as an ordinary user, or not purging root's old
mail (much of which are routine reports which are seldom good for anything
after a day or two)

In freebsd /home should be a symbolic link to /usr/home.  User directories
should be in /usr/home.

There just should not be much in / to get bigger except /root, and you
should not be keeping much of anything in /root.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Changing Console Resolution - Vidcontrol

2007-04-02 Thread Lars Eighner

On Mon, 2 Apr 2007, Schiz0 wrote:


Hey,

I'm wondering how you can increase the resolution of the console in
FreeBSD stable. I have read the man page on vidcontrol and googled around
a bit, but I'm still confused about what to do. I'm currently running
FreeBSD in VMWare on a windows machine (But that'll change as soon as I
learn enough to put it up my server, which currently runs linux). I'd like
to have something like 1024x768 resolution or so. Also, the man pages
mention something about VESA modules. What exactly is this, and do I need
it? My kernel is currently compiled without support for it. Would I need
to recompile my kernel again?



You're question does not quite make sense.  Console is more or less the
FreeBSD word for boss text-mode terminal. It has nothing to do with what a
terminal window might look like in a GUI such as Windows or X.  The first
question is what *text* modes does your hardware support.  I don't know of
video hardware that supports 1024x768 raster text.  If your hardware
supports it and you want the VESA modes, you can compile VESA support
into the kernel (which you should do if you use it just about all the time)
or it can be load dynamically (see man 4 vga).  Ditto for 90 column VGA.
Most of the console modes are regular vga text modes and they are usually
expressed in terms of lines(high) x columns(wide), for example the standard
25x80.

I suspect you do not really want a console resolution of 1024x768 (px).
I suspect you want 1024x758 in a GUI, in which case you need to be
researching X as vidcontrol has nothing to do with that.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Is Makefile.inc1 in 6 wrong?

2006-04-04 Thread Lars Eighner

It appears to me that either I have a wrong version of awk or
this Makefile.inc1 is wrong:

#
# $FreeBSD: src/Makefile.inc1,v 1.499.2.11 2006/04/04 14:24:03 glebius Exp $
#

Snippage

MAKEOBJDIRPREFIX?=  /usr/obj
.if !defined(OSRELDATE)
.if exists(/usr/include/osreldate.h)
OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print $$3 }' \
/usr/include/osreldate.h
.else
OSRELDATE=  0


In particular with the double dollar sign in the awk statement,
I get no return, therefore OSRELDATE gets set to 0.  The awk
statement also fails from the command line.  But if I use only
one $, the awk statement succeeds.

Is there a reason for the double dollar sign?  Is something
wrong with my awk?  Or is the Makefile.inc1 wrong?  I can't seem
to find a switch to get awk to return its version number.


Here is /usr/include/osreldate.h

/*-
 * Copyright (c) 1992-2006 The FreeBSD Project.
 * All rights reserved.
 *
snippage
 * SUCH DAMAGE.
 *
 */

#ifdef _KERNEL
#error osreldate.h cannot be used in the kernel, use sys/param.h
#else
#undef __FreeBSD_version
#define __FreeBSD_version 504105
#endif

Here are the two awk statements run in an editor shell:

Tue Apr 04 16:09:48 bash3.1:ttyp0:eighner
goodwill~$awk '/^\#define __FreeBSD_version/ {print $$3}' 
/usr/include/osne __FreeBSD_version/ {print $$3}' /usr/include/osreldate.h

Tue Apr 04 16:11:08 bash3.1:ttyp0:eighner
goodwill~$awk '/^\#define __FreeBSD_version/ {print $3}' 
/usr/include/osrne __FreeBSD_version/ {print $3}' /usr/include/osreldate.h
504105
Tue Apr 04 16:12:12 bash3.1:ttyp0:eighner
goodwill~$exit
exit

In otherwords, $$= no return, $= right answer.

Should I upgrade my awk in some way?  Or should I hope the
maintainer will fix the Makefile?


--
Lars Eighner
[EMAIL PROTECTED]  [EMAIL PROTECTED]
http://www.larseighner.com/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Is Makefile.inc1 in 6 wrong?

2006-04-04 Thread Lars Eighner

On Tue, 4 Apr 2006, Jung-uk Kim wrote:


On Tuesday 04 April 2006 05:14 pm, Lars Eighner wrote:

It appears to me that either I have a wrong version of awk or
this Makefile.inc1 is wrong:

#
# $FreeBSD: src/Makefile.inc1,v 1.499.2.11 2006/04/04 14:24:03
glebius Exp $ #

Snippage

MAKEOBJDIRPREFIX?=  /usr/obj
.if !defined(OSRELDATE)
.if exists(/usr/include/osreldate.h)
OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print
$$3 }' \ /usr/include/osreldate.h
.else
OSRELDATE=  0


In particular with the double dollar sign in the awk statement,
I get no return, therefore OSRELDATE gets set to 0.  The awk
statement also fails from the command line.  But if I use only
one $, the awk statement succeeds.

Is there a reason for the double dollar sign?


Yes.  See make(1):

   $   A single dollar sign `$', i.e. `$$' expands to a single dollar
   sign.


Then why does it get the wrong answer?   Also is there a
difference when the accent mark is used in front instead of a
real single quote?


--
Lars Eighner
[EMAIL PROTECTED]  [EMAIL PROTECTED]
http://www.larseighner.com/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Is Makefile.inc1 in 6 wrong?

2006-04-04 Thread Lars Eighner

On Tue, 4 Apr 2006, Jung-uk Kim wrote:


On Tuesday 04 April 2006 05:32 pm, Lars Eighner wrote:

On Tue, 4 Apr 2006, Jung-uk Kim wrote:

On Tuesday 04 April 2006 05:14 pm, Lars Eighner wrote:

It appears to me that either I have a wrong version of awk or
this Makefile.inc1 is wrong:

#
# $FreeBSD: src/Makefile.inc1,v 1.499.2.11 2006/04/04 14:24:03
glebius Exp $ #

Snippage

MAKEOBJDIRPREFIX?=  /usr/obj
.if !defined(OSRELDATE)
.if exists(/usr/include/osreldate.h)
OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ {
print $$3 }' \ /usr/include/osreldate.h
.else
OSRELDATE=  0


In particular with the double dollar sign in the awk statement,
I get no return, therefore OSRELDATE gets set to 0.  The awk
statement also fails from the command line.  But if I use only
one $, the awk statement succeeds.

Is there a reason for the double dollar sign?


Yes.  See make(1):

   $   A single dollar sign `$', i.e. `$$' expands to a single
dollar sign.


I think this is wrong for a SINGLE QUOTED argument to be passed
to awk.  The Makefile is wrong.  I am right.



Then why does it get the wrong answer?


Because you ran it from command line. ;-)  You can copy and paste the
same lines to *Makefile* like this:


.if !defined(OSRELDATE)
.if exists(/usr/include/osreldate.h)
OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print $$3 }' \
/usr/include/osreldate.h
.else
OSRELDATE=  0
.endif
.endif

all:
@echo reldate = ${OSRELDATE}


and run make.  You will see something like this (depending on your
header file):

%make
reldate = 600034


But it doesn't

Tue Apr 04 17:11:38 bash3.1:ttyp0:eighner
goodwill~$make -V OSRELDATE -f /usr/src/Makefile.inc1
0
Tue Apr 04 17:12:25 bash3.1:ttyp0:eighner
goodwill~$exit
exit

where /usr/include/osreldate.h =

/*-
 * Copyright (c) 1992-2006 The FreeBSD Project.
 * All rights reserved.

snippage
 * SUCH DAMAGE.
 *
 */

#ifdef _KERNEL
#error osreldate.h cannot be used in the kernel, use sys/param.h
#else
#undef __FreeBSD_version
#define __FreeBSD_version 504105
#endif






Also is there a difference when the accent mark is used in front
instead of a real single quote?


Where do you see it?


Where you wrote:

   $   A single dollar sign `$', i.e. `$$' expands to a single
dollar sign.


And also in man make.  The ` is an accent key, not a quote key. 
Yes, they are aka backticks and do mean something when they are

paired, but `something' is nonsense so far as I can tell.

Why would make tamper with anything in single quotes that is
passed to a command?  How do you write an argument for a command
so that make won't tamper with it?  What would double quoting
the argument be for?


--
Lars Eighner
[EMAIL PROTECTED]  [EMAIL PROTECTED]
http://www.larseighner.com/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Unkillable zombie sshd-s?

2004-12-02 Thread Lars Eighner
On Thu, 2 Dec 2004, Ivan Voras wrote:
Mark Andrews wrote:
Is there a way to find out what has happened and why does the situation 
occur? (I can't reboot the server for testing)
You can't kill them because they are already dead.  They
are just holding state so that the parent process can know
how they died.  Once the parent process wait()'s on them
(or the parent dies) they will disappear.
I knew that (except the bit that they're ukillable by design :) ), but I was 
hoping it's a known ssh problem - this is the first time I saw sshd processes 
as zombies (and it seems they've been zombies for a long time, so parents are 
probably in error).

Can I find out what their parent processes are? (something like tree-shaped 
ps?)
No tree, but try ps -axl.
PPID = parent process ID
--
Lars Eighner
[EMAIL PROTECTED] -finger for geek code-
http://www.io.com/~eighner/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Can't build STABLE from 5.2.1

2004-11-17 Thread Lars Eighner
 /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386  INSTALL=sh 
/usr/src/tools/install.sh  
PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  WORLDTMP=/usr/obj/usr/src/i386  MAKEFLAGS=-m /usr/src/tools/build/mk  -m 
/usr/src/share/mk /usr/obj/usr/src/make.i386/make -f Makefile.inc1  DESTDIR=  
BOOTSTRAPPING=0  -DNOHTML -DNOINFO -DNOLINT -DNOMAN -DNOPIC -DNOPROFILE  
-DNOSHARED -DNO_CPU_CFLAGS -DNO_WARNS bootstrap-tools
=== games/fortune/strfile
/usr/obj/usr/src/i386/usr/src/games/fortune/strfile created for 
/usr/src/games/fortune/strfile
rm -f .depend
mkdep -f .depend -a-D__FBSDID=__RCSID 
-I/usr/obj/usr/src/i386/legacy/usr/include 
/usr/src/games/fortune/strfile/strfile.c
echo strfile: /usr/lib/libc.a /usr/obj/usr/src/i386/legacy/usr/lib/libegacy.a 
 .depend
cc -O -pipe  -D__FBSDID=__RCSID -I/usr/obj/usr/src/i386/legacy/usr/include -c 
/usr/src/games/fortune/strfile/strfile.c
cc -O -pipe  -D__FBSDID=__RCSID -I/usr/obj/usr/src/i386/legacy/usr/include  
-static -L/usr/obj/usr/src/i386/legacy/usr/lib -o strfile strfile.o -legacy
/usr/lib/crt1.o: In function `_start':
/usr/lib/crt1.o(.text+0x64): undefined reference to `_init_tls'
*** Error code 1

Stop in /usr/src/games/fortune/strfile.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


-- 
Lars Eighner
[EMAIL PROTECTED] -finger for geek code-
http://www.io.com/~eighner/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Opera for FreeBSD

2002-11-01 Thread Lars Eighner
On Fri, 1 Nov 2002, Scott Lambert wrote:

 It has a lot of bugs.  I registered it anyway.  Opera will fix the bugs
 if they make money.  We need to vote with our wallets.  I'm sick and
 tired of these 40MB gzipped source downloads for a fricking web browser.

 What Opera did you install?  The one in ports is a piece of
 bloatware that loads slower than Netscape.


-- 
Lars Eighner
[EMAIL PROTECTED] -finger for geek code-
http://www.io.com/~eighner/index.html
600 E 53RD ST APT 119  AUSTIN TX 78751



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: Installworld fails: unknown groups games

2002-06-23 Thread Lars Eighner

On Sun, 23 Jun 2002, Scott Mitchell wrote:

 On Sat, Jun 22, 2002 at 10:08:14PM -0500, David W. Chapman Jr. wrote:

 I searched UPDATING for games but found no hint of this.
 Although the makefile says to run mergemaster -p
 befor installing world, mergemaster denied all knowledge of
 a -p switch.


Did it mention something about compiling and installing mergemaster
first?
   
your version is prob ably old and doesn't know about p, so you'll
have to find mergemaster in /usr/src and run make  make install
then you should be able to use -p if you don't have a new
mergemastger already.
  
 DON'T FOLLOW THIS ADVICE.
  
 Follow the more precise instuctions in UPDATING.
  
  
 
  It wasn't meant as precise advice, just something else to find in
  updating!

 From /usr/src/UPDATING:

 20020404:
 Due to the import of sendmail 8.12.2 (see 20020325 entry), a new
 user and group are required in order for sendmail to run as a
 set-group-ID binary.  A 'make installworld' will use the new user
 and group to set the owner and group of /var/spool/clientmqueue
 and will fail if the new user and group do not exist.  The 'smmsp'
 user and group must be merged from src/etc/group and
 src/etc/master.passwd before using 'make installworld'.
 'mergemaster -p' will do this.  You may need to install
 mergemaster before this will work if you are updating from a
 very old version of stable.  This can be done with:
 cd /usr/src/usr.sbin/mergemaster; make all install [clean]

 So David's advice looks about right to me.

 Lars, were you _really_ updating from 3.3 straight to 4.6?

No.  It was a typo.  4.4 - 4.6.  I wouldn't dream of updating
across a major version number without sacrificing a goat first.

 That's got to
 be asking for trouble.  I'd have spent about a day going through UPDATING
 and the list archives before embarking on anything like that, and probably
 done it in at least two steps 3.3 - 4.0 - 4.6.  You're a brave man...I'm
 quite surprised this was the only problem you had!

 BTW, the third step in the make world procedure described in the Handbook
 explicitly tells you to check the contents of etc/group, and how to use
 mergemaster -p from an older version.

That's another thing.  I can't get the handbook to make.  I upgraded
all kinds of text handling ports to get the handbook to make for
4.4, but evidently that is all broken now.

-- 
Lars Eighner
[EMAIL PROTECTED] -finger for geek code-
http://www.io.com/~eighner/index.html
600 E 53RD ST APT 119  AUSTIN TX 78751



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: We are exporting quality Hanger for cloth, pants

2001-01-15 Thread Lars Eighner

In our last episode,  [EMAIL PROTECTED],
the lovely and talented Josef Karthauser

 On Mon, Jan 15, 2001 at 09:37:40PM +1000, xlr82xs wrote:
  umm wtf is this doing on the freebsd-stable mailing list ?
 
 sorry for the implied language, and lack of written manner, but
 this came in and confused the hell out of me..

 It's been widespread spammed across a whole chunk of the net - it's
 not just _ALL_ the freebsd lists it's gone to :).


Okay, who sold spamming technology to the Red Chinese?  I think the FBI
needs to lock up Mr. Steve in Phoenix until this is thoroughly investigated.


-- 
  Lars Eighner   [EMAIL PROTECTED]   http://www.io.com/~eighner/
  Cole's Law: Thinly sliced cabbage.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message