On Sat, Apr 03, 1999 at 01:14:10PM -0500, Randy Edwards wrote:
no, dont need to load oss driver, just the es1370
That's what I thought after reading the kernel es1370 docs; good. Right
now I've got the driver compiled straight into the kernel (not as a module).
Interesting, how
vi is acting weird, and I just discovered that vi on my system is not really
vim. Isn't vi really just a symlink to vim on most systems?
vim works well, but vi is weird. It acts buggy.
thanks
--
Andrew
[PGP5.0 Key ID 0x5EE61C37]
On Fri, Apr 02, 1999 at 05:14:03PM -1000, Shawn Nguyen wrote:
Hi,
I downloaded imwheel 0.9.5 and ran the make command and got an
error. I was wondering if you knew what I am missing. It looks like
when it's trying to look for some X library and other stuff.
jax.h:6: X11/Xlib.h: No
On Sat, 3 Apr 1999, Jianbo Wang wrote:
When I played with redhat, it has netcfg to create and config a network
interface, does anyone know if there is a software in debian to do the
same thing? Or how can I create a network interface and activate it?
dinstall on the rescue disk does the
On Sat, 3 Apr 1999, Pollywog wrote:
vi is acting weird, and I just discovered that vi on my system is not really
vim. Isn't vi really just a symlink to vim on most systems?
vim works well, but vi is weird. It acts buggy.
/usr/bin/vi is linked to /etc/alternatives/vi; take a look at what
On Sat, 3 Apr 1999, Stefan Langerman wrote:
Ok, I'm installing slink right now, and I'm currently in the part where
you install device drivers. Now, How do you know which are the ones you
need? most of them have only one short line of explaination, (one even
just has a '.'), and several
On 03-Apr-99 thomas lakofski wrote:
On Sat, 3 Apr 1999, Pollywog wrote:
vi is acting weird, and I just discovered that vi on my system is not
really
vim. Isn't vi really just a symlink to vim on most systems?
vim works well, but vi is weird. It acts buggy.
/usr/bin/vi is linked to
On Sat, 3 Apr 1999, Chris Brown wrote:
Our drives have occasionally been going nuts with disk access.
They would for no reason just start reading the disk and go solid for
10 minutes. Is there a utility like top to check for who or what is
accessing the disks?
actually, top will do
On Sat, 3 Apr 1999, Chris Mayes wrote:
This means that the dialout group can read it, right? So, I did this to
the dialout line of /etc/group:
dialout:x:20:cmayes:
close:
dialout:x:20:cmayes
you would separate users by commas if you had more than one in that group.
the 'adduser' command
On Sat, Apr 03, 1999 at 12:46:12PM -0500, [EMAIL PROTECTED] wrote:
of 8hz-mp3, but it takes like 10hrs to rip and encode a cd. I'd prefer
an open source encoder, but am not opposed to a commercial one. I just
want to get one that is fast.
i use cdparanoia for ripping and bladeenc for
On Sat, 3 Apr 1999, Vincent Murphy wrote:
: On Sat, Apr 03, 1999 at 12:46:12PM -0500, [EMAIL PROTECTED] wrote:
: of 8hz-mp3, but it takes like 10hrs to rip and encode a cd. I'd prefer
: an open source encoder, but am not opposed to a commercial one. I just
: want to get one that is fast.
Em sáb, 03 abr 1999, Branden Robinson escreveu:
Make sure you're using the latest version of the slink xlib6g package. The
version number is 3.3.2.3a-11. For a while the locale and NLS data got
caught in limbo, but that problem was solved months ago.
My
Look up the DOMAIN of FRACTIONS---
DOM::FRACTIONS
Mark Phillips wrote:
I do my symbolic math with MuPAD 3.4 instead of MathCad 7.0 but I
must be dilusional there also.
On a total tangent --- have you worked out a way of getting matrices
with floating point arithmetic under MuPAD? I
Hi,
Wouldn't it be nice if POP mail boxes could be set to
automatically bounce messages over a certain size as soon as they arrive at
the ISP :-) I doubt I'd get so many large attchments if I could do that,
actually it's only one person who regularly sends me large attachments and I'm
going to
I am writing a C program to interface with a Weather Station
connected to /dev/ttyS2. I has the program working, to a point, with
kernel 2.2.3 on slink. I was using the following post initialization:
void SetBaudCOM(int new_baud)
{
int baudrate;
switch(new_baud)
{
Pollywog [EMAIL PROTECTED] writes:
Pollywog vi is acting weird, and I just discovered that vi on my
Pollywog system is not really vim. Isn't vi really just a symlink to
Pollywog vim on most systems?
On most Unix systems (including the Suns and SGIs I use on a routine
basis) 'vi' is a pretty
101 - 116 of 116 matches
Mail list logo
