[ add compatability hacks to libm ]
We tried this at usenix, but it still didn't work. Obviously there is more
going on.
Before anybody goes and bumps libraries etc, it would be useful to know if
running a statically linked jvm will work on -current.
This sounds like a good plan,
You should notice marked interactivity and UI latency improvements with
threaded GUI apps over libc_r because GUI threads will generally no longer
be blocked when disk I/O and blocking I/O occurs. For example,
applications like Open Office, Netscape, et al, really get a lot better
with
evantd Sendmail has not been working on my system for some time now. I
evantd can't say exactly how long, but my guess is that it broke when I
evantd upgraded to RELENG_5_0. This is how sendmail is invoked (by
evantd default) and it's output.
evantd # sendmail -L sm-mta -bd -q30m
evantd Sendmail has not been working on my system for some time now. I
evantd can't say exactly how long, but my guess is that it broke when I
evantd upgraded to RELENG_5_0. This is how sendmail is invoked (by
evantd default) and it's output.
evantd # sendmail -L sm-mta -bd
Has anyone been able to get the Logitech Cordless Elite Duo, or any
cordless kb/mouse combos to work?
I've got the older Logitech 'Natural' wireless keyboard + wireless mouse
working fine. I've had it for almost 3 years now, and aside from having
to change batteries every 4-6 months it's been
Has anyone been able to get the Logitech Cordless Elite Duo, or any
cordless kb/mouse combos to work?
I've got the older Logitech 'Natural' wireless keyboard + wireless mouse
working fine. I've had it for almost 3 years now, and aside from having
to change batteries every 4-6
I just put 5.0-DP2 on my IBM ThinkPad T21 (which I can finaly use, 4.x
was pretty bad since only one of the two pcmcia slots worked, and
numerous other problems, forcing me to use windows) and have been very
very happy with it.
Really? I ran 4.X on my T21 for over a year with no problems
I've recalled that FreeBSD used RTC to determine base memory size in
old days. I've tested this method on my machines and confirmed it's
working well.
If this is done, then FreeBSD won't work on many laptops and other
desktops, which report 640K for memory, but the BIOS actually steals
some
In message [EMAIL PROTECTED], Steve Kargl w
rites:
root[208] cdcontrol play
cdcontrol: no CD device name specified, defaulting to /dev/cd0c
cdcontrol: /dev/cd0cc: No such file or directory
Why is an extra c appended to cd0c?
The first c is part of the standard name for
This is a JFYI that the UCONSOLE kernel option has been phased
out as insecure. Fix your configs.
Umm, it's listed as insecure in the every config file, so you're not
saying anything that wasn't already known.
However, it was required for some X applications to work correctly,
which is why
However, it was required for some X applications to work correctly,
which is why it was still being used.
No, it's just required for them to work when run by unprivileged
users.
Things like xconsole *are* run by unprivileged users.
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
(my company demands
that all software I write, including in my own free time, is copyright by
them)
You need to move to California, where this is against the law.
Every California company I've worked for has made me sign a statement
with the above stipulation. In order to avoid this, I
You are reflecting messages back to a mailing list with
thousands of subscribers.
Cut it out.
-- Terry
Peter has applied the Big Hammer of Death to the problem for now, so
it should be stopping soon if not already.
Thanks Peter
Nate
To Unsubscribe: send mail to [EMAIL
: How many MB does your flash card where you're installing
: FreeBSD have on it?
I've installed a subsetted FreeBSD onto a 8MB CF card. For normal
FreeBSD (as oppsoed to pico), the smallest amount of space you need is
about 6.9M, and that can be stripped down to about 5M with compression
I don't get your point - what is wrong with having it a port?
Well, here's one reason:
1) Remove all the network interfaces from your system (Ethernet,
PPP, SL/IP, etc).
2) cd into /usr/ports and try to build UUCP.
Unless you have a prepopulated /usr/ports/distfiles, it won't
All these solutions assume that everyone is wired up with IP
connectivity. The original questions was who uses UUCP?
Correct.
One answer is: those without IP connectivity.
Do you mean 'full-time IP connectivity', because if you can setup a UUCP
connection, you can just as easily setup a PPP
POP and IMAP (I think) will lose all the envelope information,
You've been listening to Terry too long. It's certainly not the case,
although I've decided to quit arguing with Terry, since it's an
excercise in futility. No matter what you say, he'll either change the
subject or
Interestingly, Microsoft Exchange is one of the few commercial
SMTP servers that can handle more than a few hundred ETRN based
virtual domain instances. Go figure...
Any Q-Mail based solution using the commonly available ETRN patch also
scales well, although you have to 'roll your own'
POP and IMAP (I think) will lose all the envelope information,
You've been listening to Terry too long. It's certainly not the case,
although I've decided to quit arguing with Terry, since it's an
excercise in futility. No matter what you say, he'll either change the
subject or simply
Congratulations Julian, and thanks for all the hard work to you and the
rest of the folks!
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Wow. Why not use xdm? 8)
Too lazy?
Heh. You just uncomment one line in /etc/ttys and HUP init. It's not
compilicated.
Indeed. However, there are some differences in startup of which to be
aware (.xinitrc vs. .xsession).
I just hard-link the two files together. :)
Nate
To
If you ever claimed to hold the copyright to software that has been
released into the public domain, you would be commiting fraud.
Not if I'm the author of the software.
I can release my software under as many licenses as I'd like, including
putting it into the public domain.
However, I
| If you ever claimed to hold the copyright to software that has been
| released into the public domain, you would be commiting fraud.
|
| Not if I'm the author of the software.
|
| I can release my software under as many licenses as I'd like, including
| putting it into the public
I said I'd drop it, but apparently there are people that don't
understand the dinosaur mentality of certain organizations such as
DOD, DISA/DECC, OSD, DARPA, USA, USN, USAF, and USMC.
If it's not in the base setup, on a production box, you can't use it.
*Huh* This policy must have been
# Bash has a license which precludes its inclusion as part
# of the base system.
[Not that I favor more shells on the root file system, but anyway:]
What about gcc and grep? Does the license differ or are these not regarded
being part of the base system?
We would get rid of them
One surprising observation: If I disable APM in /boot/device.hints, my
machine suspends and resumes JUST FINE. The BIOS alone seems to be
able to suspend and awake the hardware behind FreeBSD's back. The
system only hangs if FreeBSD is involved in the process.
Hmm, I might try that.
How it can be possible? ipfw -a l:
07001 401680 deny tcp from any to any 7006
070010 0 deny tcp from any to any 7006
070010 0 deny tcp from any to any 7006
I use equal ipfw add several times from the script, but the rule number
was the
Can we decide this, please - do we want secure startup (which will
take some effort to achieve), or can we say "screw it" and start
insecure like the old system?
Can we have both? Ie; by default we are insecure until some point we
call an ioctl() that says 'no more, you must get real
=== rpcsvc
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h
rpcgen: cannot find any C preprocessor (cpp)
*** Error code 1
Let me start a release. This means rpcgen has been using
/usr/libexec/cpp which is *only* for the compiler's use. rpcgen should
have
U crypto/kerberosIV/appl/bsd/login_fbtab.c
U crypto/kerberosIV/appl/bsd/osfc2.c
U crypto/kerberosIV/appl/bsd/pathnames.h_
U crypto/kerberosIV/appl/bsd/rcmd_util.c
cvs update: warning: unrecognized response ` If there are any IP options on
`sock', die.' from cvs server
cvs
It seems feasable to generate a new binary on a recent or an old patched
FreeBSD version. The question is which is better. I think the newer
the better. Otherwise, who is going to build the 2.2.8-stable box
to make this one binary? I've already built a binary on 4.2-release
that works.
David hands Nate a freshly minted copy of BSD/OS 4.2, where he will see
/usr/contrib/ burned on the CDROM (using an electron microscope of
course :-)).
Even Sun does this with it's 'OS vendor' tools.
Uhm.. not everything. Many optional pieces from Sun installs in /opt.
The SunPro
I'm aware that software was installing itself in /usr/local years
before it was installing in /opt. On the other hand, vendor software
was installing in /opt years before I ever saw it install in
/usr/local.
Most vendor software I know pre-dates /opt, and installed itself in
/usr/local. I'm
Then again, your quoting of "packages" points up something else - I
never saw prepackaged binaries for v6 or v7.
I did on SysIII. As a matter of fact, the entire distribution was
bundled into separate packets (all of them installed in /usr). :(
Or BSD, for that matter. I never encounterd a
I'm aware that software was installing itself in /usr/local years
before it was installing in /opt. On the other hand, vendor software
was installing in /opt years before I ever saw it install in
/usr/local.
Most vendor software I know pre-dates /opt, and installed itself in
I ran mostly DEC boxes until the early 90s, which had all software
installed in /usr/bin or /usr/local/bin.
Well, I ran DEC boxes for Dec (at WSE) back in the late 80s and early
90s, and don't remember anything being in /usr/local that I didn't
drag of the net (or write myself) and
Fixing broken things is a good thing. Your argument about 'moving it
from /usr/local to show how broken' is a good test procedure, but turning
it into policy is something completely different.
I think the 'tradition' of FreeBSD installing packages in /usr/local is
enough to leave
: I know that as recent as 3=4 years ago, Purify installed itself by
: default in /usr/local, on SunOS and Solaris. Lucid did this as well,
: although things start getting pretty fuzzy going back that far. :)
purify and the binary distributions of xemacs installed themselves
into
Apologies upfront if anything I ask/say has already been covered, I'm
somwhat limited in my resources at present.
In my past experience, FreeBSD hasn't agreed very well with IBM
thinkpad laptops, unless you were using the vt0 console driver.
This is *VERY* old information. When
I'll have to look up the CIS_PTR spec. I'm not sure I like hardwiring
things like this.
Where did you get a copy of the pccard spec? Do you have to order
it from the pcmcia SIG?
Mike has my really old copy you can have (if you can get it from him),
and I think FreeBSD Inc. bought Warner
[ OpenSSH failure with particular malloc.conf flags ]
Got it !
See version 1.6 of src/lib/libc/stdlib/setenv.c. This took me all
night - Up for work in two hours !!! :-(
Good catch!
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
Alternatively the sentiment just rose why we couldn't just collapse the
crypt/hash functions of libcrypt into libc.
It would make sense.
It would make even make more sense to convince the other BSD to do the same
(haven't checked recently what they do) and do the merge.
I
It's not just that, if you always have to cover your behind when
doing tsleep you may wind up masking wakeup bugs. Places like
"vfs_bio.c" line 586 of 3182:
bp-b_xflags |= BX_BKGRDWAIT;
tsleep(bp-b_xflags, PRIBIO, "biord", 0);
if (bp-b_xflags
No, I don't mean rodents who've nibbled on chocolate-covered expresso
beans, I mean PS/2 mice which fall victim to this new problem:
May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
I've seen it for the last few weeks and can only think that something
must be stomping
It requires two downloads to get a working JDK system. No other OS
requires multiple packages to work.
People shouldn't have to compile Motif up just to get a non-source
version of the JDK to work. Versioning problems that can be caused by
folks using different include files and/or
I think that you no longer have to include Motif with the JDK.
Just let the distribution of Motif come from freebsd.org , i.e.,
a port or a package.
Too much hassle IMO. I'd *much* rather distribute it as part of the
package, and I'm looking into how feasible it would be to
If this Open Motif can be distributed as a port or package for FreeBSD
itself (and it seems to me that it can), then what hassle is that for
JDK on FreeBSD?
It requires two downloads to get a working JDK system. No other OS
requires multiple packages to work.
As long as
Unlike X (which rarely changes), I suspect the Motif stuff to change
alot.
I'm unclear on what gyrations you are expecting from a mature API
codified in an IEEE standard. As long as you're using the Motif
standard interface in your code you should have nothing to worry about.
Ahh, but
Check it out at:
http://www.opengroup.org/openmotif/
"We want to support the momentum of Open Source operating systems such as
Linux® and FreeBSD by developing an Open Motif® licence for use with
Open Source operating systems."
Also the OpenGroup is looking for sites to mirror their
Please be sure that you build and install libstand before building
a loader! (or use buildworld, that should work)
Good job tracking this one down Peter
Nate
FICL is now active on the Alpha, and actually seems to work. The Alpha
problems have been solved - it was an alignment
Sleepycats license is not FreeBSD compatible :-/
I don't understand. Reading
http://www.sleepycat.com/license.net, it seems to me that FreeBSD
meets all the necessary requirements. Can someone who understands
the details of the licensing issues either explain the situation to
On Mon, 24 Apr 2000, Nate Williams wrote:
I'm violently opposed to removing it completely. The only thing I
wouldn't be violently opposed to would be removing 'Attic' files (truly
unused file), and having them stored away somewhere in the tree for
archival purposes.
You realize
I'd like to add that it can be particularly important when legal
questions arise.
You confuse the argument for SOME complete repositories with
the necessity that ALL (or at each most) repositories be so extensive.
No-one needs to grab a repository, unless they're looking at history.
If that's the _only_ point, then Garrett Wollman's idea should work
perfectly. Stick the files under CVS
No, that was not my proposal. I want to keep them out of CVS
entirely. CVS is Not Good at handling binary files (even if you never
change them). That's why I'd like them in a
I want to bring up a suggestion. I just want a little bit of argument on
it ... and if you're violently opposed, just say so, that's fine.
I want to suggest that, once a year, we go thru the cvs archive, and prune
away all history more than 3 (or maybe 2, maybe 4) years old.
I'm violently
Core should consider reverting the special rules that were originally
created with the expectation of major breakage in 5.x back to
the set of rules we had for 3.x and 4.x.
I have no idea what special rules you are talking about for 4.x/5.x.
4.x-stable is a -stable tree and
: awi.o(.text+0x3b4): undefined reference to `memcmp'
: awi.o(.text+0x3cf): undefined reference to `memset'
What I want to know is why I don't get these with the GENERIC + awi
config file I have :-(
Are you compiling with optimization turned on? I believe mem* are
inlined if optimization
: Are you compiling with optimization turned on? I believe mem* are
: inlined if optimization is enabled.
Don't think so. Both build -O.
Poul's build may not have optimization turned on, since it's controlled
by /etc/make.conf.
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
: : Are you compiling with optimization turned on? I believe mem* are
: : inlined if optimization is enabled.
:
: Don't think so. Both build -O.
:
: Poul's build may not have optimization turned on, since it's controlled
: by /etc/make.conf.
It isn't something specific to Poul's
That's always struck me a bit odd... I thought 'MAKEDEV std' made
the generic set of devices and that 'MAKEDEV all' should make... well..
_ALL_. *shrug*
What do you define as `all'? Say I have a big FTP server with 8 wide
SCSI controllers, each with 15 disks - that's da0..da119. I
What is the proper way for obtaining the signal mask from
within the jmp_buf struct on 4.x or -current? Previously
with the JDK port for 3.x we did something like this:
signalMask = jmpbuf[0]._sjb[6];
This no longer works now that we support 32 signals. Is
there a
: *not* preempted except when being interrupted, so there are no
: 'priorities', per say. Or, rather, the relative priority is strictly
: that the interrupt takes priority over supervisor code except when
: disabled by said supervisor code.
:
:But locks with owners wouldn't
: : *not* preempted except when being interrupted, so there are no
: : 'priorities', per say. Or, rather, the relative priority is strictly
: : that the interrupt takes priority over supervisor code except when
: : disabled by said supervisor code.
: :
: :But locks with
:And would there still be areas of the kernel that disable multiple
:interrupts, perhaps CAM or the network stack for instance? What do
:all the splbio and splnet calls translate into in this new scheme?
:
The entire design of the kernel is currently predicated on the spl*()
When I use reboot(8) to reboot my Vaio z505sx, it waits nicely for
the bufdaeon and the syncer to stop. Then the screen goes blank
and the system completely hangs. Unplugging the battery and power
is the only way to gte it booting again. It used to work fine with a
4.0-current of some 3
[ Moved to chat ]
[Multiple irrelevant mailing-lists snipped.]
On Sat, 8 Jan 2000 18:31:19 -0800, "FreeBSD" [EMAIL PROTECTED] said:
Since when does an E-mail address require a "realname"?
As Sherlock Holmes once said: ``It is always unpleasant dealing with
an alias.''
plonk
This week, I have added chown-like functionality to mknod(8) and restored
chown chgrp back to their previous locations. MAKEDEV has been
updated to use the new functionality of mknod(8).
Thanks for doing this David!
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
One of the things I would do to optimize ipfw is:
- instead of keeping one list with all the rules, split the list (the
internal one) by interface and by direction (one list for ed1 incoming,
one list for ed1 outgoing, etc.).
one skipto rule is enough to switch between two rulesets
PCCARD used to exist separate from GENERIC due to the zp and ze
drivers not being compatible with pccard's pcic driver. These drivers
were removed from the system not too long ago by phk.
The reason I added PCCARD to the system was because in the old code, I
didn't trust the PCCARD
: So, my only comment is that if you believe that the code is stable
: enough to not negatively effect desktop systems, and not too much bloat,
: then have at it. Note, enabling PCCARD functionality w/out APM will be
: a losing situation for many laptops, and adding APM functionality for
:
In message [EMAIL PROTECTED], Kevin Day writes:
Ack, I was using this very same thing for several devices in an isolated
peer-to-peer network to decide who the 'master' was. (Whoever had been up
longest knew more about the state of the network) Having this change could
cause weirdness for
Between the two of us Dave Mills and I have managed to get the
"nanokernel" to act sensibly in the domain inside +/- 1usec which
the old one didn't. (See http://gps.freebsd.dk for what kind of
performance this can result in, given appropriate hardware).
You may not know the answer to this,
: You may not know the answer to this, but it's worth a shot. Wht kind of
: accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
gps receiver + atomic clock on a i486 class machine.
I've got the cheap gps
: If people do a "settimeofday" we change the boot time since the
: amount of time we've been up *IS* known for sure, whereas the boottime
: is only an estimate.
There is one problem with this. The amount of uptime isn't the same
as the amount of time since the machine booted. How can
: : You may not know the answer to this, but it's worth a shot. Wht kind of
: : accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
:
: We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
: gps receiver + atomic clock on a i486 class machine.
:
:
: Cool. I was under the impression that the cheap NMEA signals only gave
: 2-5sec accuracy given the 2400 baud speed issues.
If you have a PPS signal, then you can get fairly close even if the
inforation about the PPS signal comes in at 2400 baud.
Hmm, how do I find out how good it is?
If half as much energy was spent adding the missing bits of
functionality to the new systems as people have been spending
complaining it then we'd be there ages ago.
Not true. It doesn't take a disk expert to complain about a policy,
but it takes one to fix bugs/add features to the
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of shakeout time would be called for. I think that time should
be longer than a few days, and should be in 4.0, and then retired in
What we need here is a commitment to these new initiatives, not a lot of
fence-sitting and clutching our knitting to our chests.
If all our users were developers I would agree. But *most* of our users
are not developers.
Again, I say, think of what we're trying to achieve here.
Good
In message [EMAIL PROTECTED], Nate Williams writes:
What we need here is a commitment to these new initiatives, not a lot of
fence-sitting and clutching our knitting to our chests.
If all our users were developers I would agree. But *most* of our users
are not developers.
-CURRENT
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of shakeout time would be called for. I think that time should
be longer than a few days, and should be in 4.0, and then
What is a killer is if a large number of people on popular hardware can't
even boot, *at all*, in no, way, shape or form. Only that. The only way
to find that out for sure before 4.0 is to push the issue *now*.
I disagree, but I'm not making the decision.
Nate
To Unsubscribe: send mail
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of shakeout time would be called for. I think that time should
be longer than a few days, and should be in 4.0, and then
If half as much energy was spent adding the missing bits of functionality
to the new systems as people have been spending complaining it then we'd be
there ages ago.
Not true. It doesn't take a disk expert to complain about a policy, but
it takes one to fix bugs/add features to the existing
I'm about to import bind 8.2.2.p5 into src/contrib/bind and fix up the
broken parts of the tree as I go. I will disable the named (and associated
tools) build for the duration. If you want to do some make worlds or
releases in the next 8 hours or so, do a cvsup pronto!
Thanks Peter!
Nate
Instead, I have adopted and cleaned up the kernel portions of the patch
and modified nfsd to allow the binding ip/host to be specified on the
command line. Thus nfsd can be run bound to a specific IP address.
This sounds like a great solution, thanks Matt!
Nate
To
I think most if not all the ethernet cards I or my customers
have bought over the last year have sported mighty fine netboot
capabilities.
FWIW, few of the cards I've bought over the years sport netboot. And,
netboot is an impossibility in 'embedded' systems that use things like
"Accidental" removals from the lists are so common that I give up. I no
longer even try to get back on them -- it's been happening for _years_ now,
and I have made multiple complaints about it, and if it's not a problem for
whoever runs the mailing lists, then I just don't care that
[Mayhaps too many Cc:'s kept in order to reach relevant audience]
Thanks, sorry about the X-posting...
On Sun, Oct 10, 1999 at 02:57:55PM -0600, Nate Williams wrote:
I Can't believe this email only produced TWO responses!
I would have thought that this wouldhav brought out the chainsaws
In any case, you should not be doing lots of writes to root, so the
lack of softupdates should not be a problem.
So, are you suggesting make /tmp it's own disk, otherwise anytime you do
development alot of writes are done to /.
And, if you do lots of development, then you'll have the same
1. Should the ucontext_t changes be backed out, or is this the
way we would like to go? (but only it better :-)
We need something. Rather than say 'something better', I'd need to see
what that better things is. However, given Bruce's comments earlier, it
seems like we need to have
I'm trying to digest the recent signal changes and get a handle on
what I need to do to make Modula-3 work. There is code in the runtime
currently which catches SIGBUS and uses the sigcontext's "sc_err"
member to find out the faulting address. That should be replaced
by the siginfo_t's
Mainly historical bugs. Includes are installed too early and they only
match the new syscalls. Tools are built using the new includes, so they
need new libraries to be consistent. Therefore the new libraries are
built before the new tools. These bugs were implemented in FreeBSD-1 by
you don't under stand, we are NOT talking about upgrades, we are talking
about how to make a buildable system on -stable...
There are essentially the same problem. In order to do an upgrade, you
have to be able to build on -stable. :)
=== libgcc
echo '#include i386/xm-i386.h' config.h
P.S. It is really hard for me to not make personal attacks against you
after all of the above and completely ignoring the rest of my message.
No, I didn't. My statement was that your 'confrontational' style of
email wasn't making things any better.
Mellow it out, and instead of attacking
Following up on my previous mail regarding the panic on the Alpha,
I've been looking at the diff for the code in question, in
"src/sys/nfs/nfs_socket.c":
@@ -1501,14 +1502,16 @@
struct nfsreq *rep;
register struct proc *p;
{
+ sigset_t tmpset;
+ tmpset =
I agree.
Your work also has a serious security concern if it allows this you to
directly attatch to it's port 25.
No it doesn't, but you do bring up another good point why not to use the
ISP's mail server. Security. I don't want email to bounce on your box
and potentially
:[Insert semi-nasty message about how people should really be testing
:their changes before they commit, how it is a blatant disregard for
:basic human rigths not to do so etc etc etc]
...
Insert nasty message about how people shouldn't post idiotic comments.
Play nice boys! Remeber
I think that java is still broken by this.
..
java
Segmentation fault (core dumped)
I've just committed the fix in "src/libexec/rtld-elf/rtld.h" revision
1.12. The Java runtime was peeking into some of the dynamic linker's
private data structures. My recent changes added some
Do you know the appropriate channel to contact the XFree86 folks? In the
mean while, I can take Sheldon's advice, submit it to our XFree86 port.
By the way, I've just thought of something you should consider. I think
there's still a problem with xdm, where trying to change vty while it's
1 - 100 of 170 matches
Mail list logo
