Linux-Misc Digest #114, Volume #19               Sat, 20 Feb 99 17:13:13 EST

Contents:
  tpconfig and gps/X (Bruce Kall)
  kernel compilation problems ("Amelia A. Lewis")
  Re: formation linux!!! (Glen Scurr)
  Bash-2.03 available for FTP (Chet Ramey)
  Re: Putting NT (and Linux) on the Same System? (Wayne Watson)
  Firewall with 1 IP ([EMAIL PROTECTED])
  Cannon BJC-620 printer (Eric Kappotis)
  I like it the hard way 8-/ (2.2.1 on Slackware 3.5) ("A.G.")
  Re: how do I change resolution? (Bill Unruh)
  Re: Always as root - is it dangerous? ("Trevor Poole")
  Adobe with RH5.2 - Error help (Doug Paradis)
  Re: Simple Samba question. . . I hope (David Besse)

----------------------------------------------------------------------------

From: [EMAIL PROTECTED] (Bruce Kall)
Crossposted-To: 
comp.os.linux.hardware,comp.os.linux.development.apps,comp.os.linux.development.system
Subject: tpconfig and gps/X
Date: 19 Feb 1999 19:23:38 GMT
Reply-To: [EMAIL PROTECTED]


I currently support the tpconfig utility (Synaptics
Linux touchpad driver -- www.compass.com/synaptics).  Anyway
I just released the latest version to fix a problem with
the 2.2.X kernel.  The next enhancement I would like to
add is to make it work while either gpm and/or X is
running.  From what I know from the initial author of
tpconfig, the PS/2 port does not support sharing and
this is the reason why tpconfig hasn't support running
itself while gpm and/or X is running.

What I'm looking for is suggestions/pointers on how to
add this functionality to tpconfig (run on top of X).
Any suggestions would be welcome.

Thanks,
Bruce



-- 
====================================================================
Bruce Kall
Mayo Foundation
Rochester, MN

e-mail: [EMAIL PROTECTED]
phone: (507) 255-4768
 
====================================================================




------------------------------

From: "Amelia A. Lewis" <[EMAIL PROTECTED]>
Subject: kernel compilation problems
Date: Sat, 20 Feb 1999 16:16:32 -0500

*sigh*  I feel like a newbie all over again.

I have two immediate problems.  I've finally gotten a system that I hope
to use to replace my lovely and reliable 486/33 Linux box, a K6-2/350.
First problem: I have a DLink DFE530TX.  Fine; found on the net that
Donald Becker's got an experimental via3403.c driver that should run it.
My problem: how do I add the driver to the kernel build?  I'm going to
have to add it into the 2.0.32 that I've got source for, until I can
get the net up and get later kernel source onto the machine.  Any help
with this would be greatly appreciated.

The second problem may well be a FAQ; I haven't figured out a good query
for it, for the usual search engines.  The kernel (both the original
redhat 5 kernel, and the newly-compiled (and *my*, that was *fast*!)
2.0.32 only see <64 Mb of the 128 Mb of installed memory in the machine.
I'm certainly not hurting, at the moment, but I'd rather be able to use
the whole of the DIMM (the hardware is a DFI P5BV3+ 1 Mb L2, 1x128 Mb
DIMM, AMD K6-2/350).  The kernel I compiled, I did as Pentium.  Anyone
happen to know how to unlock the rest of my memory?  Or even have a
guess as to why it's doing this?  (NT sees all of the memory, btw).

Thanks in advance for any help/advice anyone can offer.

Amy!

------------------------------

From: [EMAIL PROTECTED] (Glen Scurr)
Subject: Re: formation linux!!!
Date: Sat, 20 Feb 1999 18:26:01 GMT

Raymond Doetjes <[EMAIL PROTECTED]> wrote:

>You are on the fucking internet hear the language is english and not
>french!

Learn to write it then!  hear != here

*plonk*

glen

------------------------------

From: [EMAIL PROTECTED] (Chet Ramey)
Crossposted-To: comp.unix.shell,comp.unix.questions
Subject: Bash-2.03 available for FTP
Date: 19 Feb 1999 17:57:59 GMT

The first public release of bash-2.03 is now available with the URLs

ftp://ftp.cwru.edu/pub/bash/bash-2.03.tar.gz
ftp://ftp.gnu.org/pub/gnu/bash-2.03.tar.gz

and from the usual GNU mirror sites.

This tar file does not include the formatted documentation
(postscript, dvi, html, and nroffed versions of the manual pages);
that may be retrieved with the URLs

ftp://ftp.cwru.edu/pub/bash/bash-doc-2.03.tar.gz
ftp://ftp.gnu.org/pub/gnu/bash-doc-2.03.tar.gz

When unpacking the documentation, make sure to extract the tar file
in the bash-2.03 source directory.

Diffs from bash-2.02.1 are available with the URLs

ftp://ftp.cwru.edu/pub/bash/bash-2.02.1-2.03.diff.gz
ftp://ftp.gnu.org/pub/gnu/bash-2.02.1-2.03.diff.gz

Make sure to apply the diffs using `patch -p1' from within the
bash-2.02.1 source directory.

Please use `bashbug' to report bugs with this version.  It is built
and installed at the same time as bash.

Installation
============

Please read the README file first.

Installation instructions are provided in the INSTALL file.

Fixes and New Features
======================

This release fixes the relatively few bugs found in bash-2.02.1.
There are a couple of new features in bash, and a large number of
new things in readline.

The changes of most interest in bash-2.03 are:

        o All shells given the --login option at startup read the
          login shell startup files, even non-interactive shells
        o There is a new configuration framework for shared objects,
          so the loadable builtins may be built more easily.  This
          is shared by readline, so building shared versions of the
          readline and history libraries (in the readline distribution)
          is easier.

Changed have been made to the readline library being released at
the same time as bash-2.03, readline-4.0, so that bash can be
linked against an already-installed readline library rather than
the private version in lib/readline.  Only readline-4.0 is able
to provide all of the symbols that bash-2.03 requires; earlier
versions of the readline library will not work correctly.

A complete list of changes between bash-2.02.1 and bash-2.03 is
available in the file CHANGES.

User-Visible Changes
====================

The aforementioned change to the shell's startup behavior when
the `--login' option is supplied is the most important
user-visible difference between bash-2.02.1 and bash-2.03.  There
is also a new `shopt' option, `restricted_shell', that allows
startup files to tell whether or not the shell was started in
restricted mode. 

Some user-visible changes that have caused problems in the past
are listed in the file COMPAT. 

A Peek at the Future
========================

Things under consideration for bash-2.04 (or whatever the next version
is named) are

        o Allowing the shell to open and manipulate TCP and UDP sockets,
          via the redirection operators
        o Associative arrays

Readline
========

Also available is a new release of the standalone readline library,
version 4.0, with its own configuration scripts and Makefiles. 
It can be retrieved with the URLs

ftp://ftp.cwru.edu/pub/bash/readline-4.0.tar.gz
ftp://ftp.gnu.org/pub/gnu/readline-4.0.tar.gz

and from the usual GNU mirror sites.

Diffs from readline-2.2.1 are available with the URLs

ftp://ftp.cwru.edu/pub/bash/readline-2.2.1-4.0.diff
ftp://ftp.gnu.org/pub/gnu/readline-2.2.1-4.0.diff

Make sure to install the patches using `patch -p1 < patch-file' from
within the readline-2.2.1 source directory.

The formatted readline documentation is included in the readline
distribution tar file.

A separate announcement listing the changes in readline is being
distributed.

As always, thanks for your help.

Chet

+========== CHANGES ==========+
This document details the changes between this version, bash-2.03-release,
and the previous version, bash-2.03-beta2.

1.  Changes to Bash

a.  A file descriptor leak in the `fc' builtin was fixed.

b.  A bug was fixed in the `read' builtin that caused occasional spurious
    failures when using `read -e'.

c.  The version code needed to use the value of the cpp variable
    CONF_MACHTYPE rather than MACHTYPE.

d.  A new test was added to exercise the command printing and copying code.

e.  A bug was fixed that caused `time' to be recognized as a reserved word
    if it was the first pattern in a `case' statement pattern list.

==============================================================================
This document details the changes between this version, bash-2.03-beta2,
and the previous version, bash-2.03-beta1.

1.  Changes to Bash

a.  Slight additions to support/shobj-conf, mostly for the benefit of AIX 4.2.

b.  config.{guess,sub} support added for the NEC SX4.

c.  Changed some of the cross-compiling sections of the configure macros in
    aclocal.m4 so that configure won't abort.

d.  Slight changes to how the HTML versions of the bash and readline manuals
    are generated.

e.  Fixed conditional command printing to avoid interpreting printf `%'-escapes
    in arguments to [[.

f.  Don't include the bash malloc on all variants of the alpha processor.

g.  Changes to configure to make --enable-profiling work on Solaris 2.x.

h.  Fixed a bug that manifested itself when shell functions were called
    between calls to `getopts'.

i.  Fixed pattern substitution so that a bare `#'as a pattern causes the
    replacement string to be prefixed to the search string, and a bare
    `%' causes the replacement string to be appended to the search string.

j.  Fixed a bug in the command execution code that caused child processes
    to occasionally have the wrong value for $!.

2.  Changes to Readline

a.  Added code to the history library to catch history substitutions using
    `&' without a previous history substitution or search having been
    performed.

3.  New Features in Bash

4.  New Features in Readline

a.  New bindable variable: `isearch-terminators'.

b.  New bindable function: `forward-backward-delete-char' (unbound by default).

==============================================================================
This document details the changes between this version, bash-2.03-beta1,
and the previous version, bash-2.03-alpha.
    
1.  Changes to Bash

a.  A change was made to the help text for `{...}' to make it clear that a
    semicolon is required before the closing brace.

b.  A fix was made to the `test' builtin so that syntax errors cause test
    to return an exit status > 1.

c.  Globbing is no longer performed on assignment statements that appear as
    arguments to `assignment builtins' such as `export'.

d.  System-specific configuration changes were made for:  Rhapsody,
    AIX 4.2/gcc, BSD/OS 4.0.

e.  New loadable builtins: ln, unlink.

f.  Some fixes were made to the globbing code to handle extended glob patterns
    which immediately follow a `*'.

g.  A fix was made to the command printing code to ensure that redirections
    following compound commands have a space separating them from the rest
    of the command.

h.  The pathname canonicalization code was changed to produce fewer leading
    `//' sequences, since those are interpreted as network file system
    pathnames on some systems.

i.  A fix was made so that loops containing `eval' commands in commands passed
    to `bash -c' would not exit prematurely.

j.  Some changes were made to the job reaping code when the shell is not
    interactive, so the shell will retain exit statuses longer for examination
    by `wait'.

k.  A fix was made so that `jobs | command' works again.

l.  The erroneous compound array assignment var=((...)) is now a syntax error.

m.  A change was made to the dynamic loading code in `enable' to support
    Tenon's MachTen.

n.  A fix was made to the globbing code so that extended globbing patterns
    will correctly match `.' in a bracket expression.

2.  Changes to Readline

a.  A fix was made to the completion code in which a typo caused the wrong
    value to be passed to the function that computed the longest common
    prefix of the list of matches.

b.  The completion code now checks the value of rl_filename_completion_desired,
    which is set by application-supplied completion functions to indicate
    that filename completion is being performed, to decide whether or not to
    call an application-supplied `ignore completions' function.

3.  New Features in Bash

a.  A change was made to the startup file code so that any shell begun with
    the `--login' option, even non-interactive shells, will source the login
    shell startup files.

4.  New Features in Readline

a.  A new variable, rl_erase_empty_line, which, if set by an application using
    readline, will cause readline to erase, prompt and all, lines on which the
    only thing typed was a newline.

==============================================================================
This document details the changes between this version, bash-2.03-alpha,
and the previous version, bash-2.02.1-release.

1.  Changes to Bash

a.  System-specific configuration changes were made for: Irix 6.x, Unixware 7.

b.  The texi2dvi and texi2html scripts were updated to the latest versions
    from the net.

c.  The configure tests that determine which native type is 32 bits were
    changed to not require a compiled program.

d.  Fixed a bug in shell_execve that could cause memory to be freed twice
    after a failed exec.

e.  The `printf' test uses `diff -a' if it's available to prevent confusion
    due to the non-ascii output.

f.  Shared object configuration is now performed by a shell script,
    support/shobj-conf, which generates values to be substituted into
    makefiles by configure.

g.  Some changes were made to `ulimit' to avoid the use of RLIM_INVALID as a
    return value.

h.  Changes were made to `ulimit' to work around HPUX 9.x's peculiar
    handling of RLIMIT_FILESIZE.

i.  Some new loadable builtins were added: id, printenv, sync, whoami, push,
    mkdir.  `pushd', `popd', and `dirs' can now be built as regular or
    loadable builtins from the same source file.

j.  Changes were made to `printf' to handle NUL bytes in the expanded format
    string.

k.  The various `make clean' Makefile targets now descend into lib/sh.

l.  The `type' builtin was changed to use the internal `getopt' so that things
    like `type -ap' work as expected.

m.  There is a new configuration option, --with-installed-readline, to link
    bash with a locally-installed version of readline.  Only readline version
    4.0 and later releases can support this.  Shared and static libraries
    are supported.  The installed include files are used.

n.  There is a new autoconf macro used to find which basic type is 64 bits.

o.  Dynamic linking and loadable builtins should now work on SCO 3.2v5*,
    AIX 4.2 with gcc, Unixware 7, and many other systems using gcc, where
    the `-shared' options works correctly.

p.  A bug was fixed in the bash filename completion code that caused memory to
    be freed twice if a directory name containing an unset variable was
    completed and the -u option was set.

q.  The prompt expansion code now quotes the `$' in the `\$' expansion so it
    is not processed by subsequent parameter expansion.

r.  Fixed a parsing bug that caused a single or double quote after a `$$' to
    trigger ANSI C expansion or locale translation.

s.  Fixed a bug in the globbing code that caused quoted filenames containing
    no globbing characters to sometimes be incorrectly expanded.

t.  Changes to the default prompt strings if prompt string decoding is not
    compiled into the shell.

u.  Added `do', `then', `else', `{', and `(' to the list of keywords that may
    precede the `time' reserved word.

v.  The shell may now be cross-built for BeOS as well as cygwin32.

w.  The conditional command execution code now treats `=' the same as `=='
    for deciding when to perform pattern matching.

x.  The `-e' option no longer causes the shell to exit if a command exits
    with a non-zero status while running the startup files.

y.  The `printf' builtin no longer dumps core if a modifier is supplied in
    the format string without a conversion character (e.g. `%h').

z.  Array assignments of the form a=(...) no longer show up in the history
    list.

aa. The parser was fixed to obey the POSIX.2 rules for finding the closing
    `}' in a ${...} expression.

bb. The history file is now opened with mode 0600 rather than 0666, so bash
    no longer relies on the user's umask being set appropriately.

cc. Setting LANG no longer causes LC_ALL to be assigned a value; bash now
    relies on proper behavior from the C library.

dd. Minor changes were made to allow quoted variable expansions using
    ${...} to be completed correctly if there is no closing `"'.

ee. Changes were made to builtins/Makefile.in so that configuring the shell
    with `--enable-profiling' works right and builtins/mkbuiltins is
    generated.

2.  Changes to Readline

a.  The version number is now 4.0.

b.  There is no longer any #ifdef SHELL code in the source files.

c.  Some changes were made to the key binding code to fix memory leaks and
    better support Win32 systems.

d.  Fixed a silly typo in the paren matching code -- it's microseconds, not
    milliseconds.

e.  The readline library should be compilable by C++ compilers.

f.  The readline.h public header file now includes function prototypes for
    all readline functions, and some changes were made to fix errors in the
    source files uncovered by the use of prototypes.

g.  The maximum numeric argument is now clamped at 1000000.

h.  Fixes to rl_yank_last_arg to make it behave better.

i.  Fixed a bug in the display code that caused core dumps if the prompt
    string length exceeded 1024 characters.

j.  The menu completion code was fixed to properly insert a single completion
    if there is only one match.

k.  A bug was fixed that caused the display code to improperly display tabs
    after newlines.

3.  New Features in Bash

a.  New `shopt' option, `restricted_shell', indicating whether or not the
    shell was started in restricted mode, for use in startup files.

b.  Filename generation is now performed on the words between ( and ) in
    array assignments (which it probably should have done all along).

c.  OLDPWD is now auto-exported, as POSIX.2 seems to require.

d.  ENV and BASH_ENV are read-only variables in a restricted shell.

4.  New Features in Readline

a.  Many changes to the signal handling:
        o Readline now catches SIGQUIT and cleans up the tty before returning;
        o A new variable, rl_catch_signals, is available to application writers 
          to indicate to readline whether or not it should install its own
          signal handlers for SIGINT, SIGTERM, SIGQUIT, SIGALRM, SIGTSTP,
          SIGTTIN, and SIGTTOU;
        o A new variable, rl_catch_sigwinch, is available to application
          writers to indicate to readline whether or not it should install its
          own signal handler for SIGWINCH, which will chain to the calling
          applications's SIGWINCH handler, if one is installed;
        o There is a new function, rl_free_line_state, for application signal
          handlers to call to free up the state associated with the current
          line after receiving a signal;
        o There is a new function, rl_cleanup_after_signal, to clean up the
          display and terminal state after receiving a signal;
        o There is a new function, rl_reset_after_signal, to reinitialize the
          terminal and display state after an application signal handler
          returns and readline continues

b.  There is a new function, rl_resize_terminal, to reset readline's idea of
    the screen size after a SIGWINCH.

c.  New public functions: rl_save_prompt and rl_restore_prompt.  These were
    previously private functions with a `_' prefix.

d.  New function hook: rl_pre_input_hook, called just before readline starts
    reading input, after initialization.

e.  New function hook: rl_display_matches_hook, called when readline would
    display the list of completion matches.  The new function
    rl_display_match_list is what readline uses internally, and is available
    for use by application functions called via this hook.

f.  New bindable function, delete-char-or-list, like tcsh.
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet)

Chet Ramey, Case Western Reserve University     Internet: [EMAIL PROTECTED]

------------------------------

From: Wayne Watson <[EMAIL PROTECTED]>
Subject: Re: Putting NT (and Linux) on the Same System?
Date: Sat, 20 Feb 1999 13:08:38 -0800
Reply-To: [EMAIL PROTECTED]

How?

Well, OK, I'll be expressive. :-) Is there some description somewhere of how this 
might be done, say in a
book, by a distributor of Linux, or the Linux Journal?

Jason Clifford wrote:

> On Sat, 20 Feb 1999, Wayne Watson wrote:
>
> > disks.  NT and associated file systems are on disk 0 presently.  I would like to 
>purchase another disk
> > and put Linux on it, and then be able to boot up in either OS, but I don't want to 
>distrub any of the
> > NT files or partitions.  Is this possible?
>
> Yes.
>
> Jason Clifford
> Definite Linux Systems
> http://definite.ukpost.com/

--
      "If you don't think too good, then don't think too much."  Ted Williams, 
Baseball Great

                                          ========== Wayne T. Watson  ==========
When having fun, which is a lot, you'll find me on the internet pursuing my hobbies of 
 amateur astronomy
and science.  When I get serious, I consult in C, UNIX, C++, Java.  See my web page.

                                           [EMAIL PROTECTED]
                                           Web Page: http://www.sirius.com/~mtn_view 
(Updated 2/15/99)



------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: alt.os.linux,comp.os.linux.networking,comp.os.linux.setup
Subject: Firewall with 1 IP
Date: Sat, 20 Feb 1999 21:07:53 GMT



 - My ISP has asigned me 1 static IP.
 - I have a LAN, and 3 NT Web servers on it that I want to make available to
Inet with 192.168.X.X IPs.

 - I want to put a Linux RedHat 5.2 based firewall before the LAN.

   Would it be possible with just 1 IP, maybe with IP Masquerading or should I
ask for a Class C Network?

============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    

------------------------------

From: Eric Kappotis <[EMAIL PROTECTED]>
Subject: Cannon BJC-620 printer
Date: Fri, 19 Feb 1999 14:49:52 -0500

Hello,

I'm using a Cannon BJC-620 printer.  Under linux there are no drivers
that support my printer so i am unable to use the 720x720 dpi
capability.  Do i have any options so i can enable all the features of
my printer?  I already E-mailed cannon and they said the didn't offer
support for use with linux.

Thanks for your time,
Eric K.


------------------------------

From: "A.G." <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.slackware
Subject: I like it the hard way 8-/ (2.2.1 on Slackware 3.5)
Date: Fri, 19 Feb 1999 16:01:15 -0500

Hi all:

Got a pack of distributions from CheapBytes. Tried RH, and Caldera - Naaah!
not for me. Too easy. ;) They do everything for you, and place scipts in
non-standard places, assuming that the users won't dare to look for them. If
I wanted to rely on interactive utilitites with graphical interface, I
wouln't want to move from WindowsNT. :) (just kidding)

Slackware 3.5 won me in this respect. In two days I managed to upgrade
kernel to 2.0.36, replace egc with newest gcc, install new bash, etc. on
both of my computers (686 and 486). My main goal right now is to move to
2.2.1 since it's out there and my system is not fully configured yet
anyways. Going through the shopping-list, I am upgrading components and
having some problems along the way. For bandwidth conservation I posted
*entire* warning and error messages as text files at:

http://www3.sympatico.ca/genkin/glibc_warning.txt
http://www3.sympatico.ca/genkin/nettools_problems.txt
http://www3.sympatico.ca/genkin/procps_problems.txt

1. libc ./configure won't finish with warnings :

....
*** (g)msgfmt is too old or wrong version (need GNU gettext 0.10 or better).
....
checking installed Linux kernel header files... 2.0.10 or later
*** You should not compile the GNU libc without the `linuxthreads' and
*** `crypt' add-on.  Not using them risks to be incompatible with the
*** libraries of other systems.  Consider getting the add-ons and restart
*** the configuration.
....

2. nettools won't compile:

...
I/usr/src/net-tools-1.50 -idirafter /usr/src/net-tools-1.50/include    -c
interface.c -o interface.o
interface.c:33: linux/if_ec.h: No such file or directory
In file included from interface.c:49:
/usr/src/net-tools-1.50/intl.h:5: libintl.h: No such file or directory
make[1]: *** [interface.o] Error 1
make[1]: Leaving directory `/usr/src/net-tools-1.50/lib'
make: *** [subdirs] Error 2

3. proctools won't compile:

for dir in skill xproc ; do \
  [ -f $dir/Imakefile ] && (cd $dir; xmkmf) ; done
mv -f Makefile Makefile.bak
imake -DUseInstalled -I/usr/X11R6/lib/X11/config
imake: No such file or directory
imake: Cannot exec /lib/cpp.
  Stop.
imake: Exit code 1.
  Stop.
make: *** [config] Error 1

Any input would be very appreciated!

Arcady




------------------------------

From: [EMAIL PROTECTED] (Bill Unruh)
Crossposted-To: 
alt.linux,alt.os.linux,comp.os.linux,comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.questions,comp.os.linux.x,linux.redhat.misc,linux.redhat.rpm
Subject: Re: how do I change resolution?
Date: 20 Feb 1999 21:26:35 GMT

In <[EMAIL PROTECTED]> "TomWolf" <[EMAIL PROTECTED]> writes:

>I have just installed redhat 5.2 but I cant open xwindows because I got the
>wrong resolution. How do I change the resolution?

Do not understand what you mean. What error message do you get when you
try to open Xwindows (eg startx)? The controlling file is
/etc/X11/XF86Config.



------------------------------

Reply-To: "Trevor Poole" <[EMAIL PROTECTED]>
From: "Trevor Poole" <[EMAIL PROTECTED]>
Subject: Re: Always as root - is it dangerous?
Date: Fri, 19 Feb 1999 14:46:01 -0500


Always being root can be various tricky for the new user.  A potentially
better way is to make a user account for yourself and then as root for the
commands that you issue all the time,  i.e. shutdown etc,  set the suid bit
by typing chmod a+S <command> ...  This will allow you to run certain root
commands as yourself.  There is a potential security hole in using suid but
if you are the only user then it is not a big problem

regards,
Trevor



jansens_at_ibm_dot_net (Karel Jansens) wrote in message ...
>On Thu, 18 Feb 1999 13:37:50, Nils Westerlund <[EMAIL PROTECTED]>
>wrote:
>
>> I installed SuSE Linux 5.3 two days ago and I'm really impressed so far.
>> After ten years in MSWindows-environment there are some things that are
>> a bit confusing. Could it be "dangerous" to always log in as root? I
>> don't want to re-login or su everytime I want to mount a zip or
>> something like that, and therefore I always log in as root. How do you
>> guys usually do?
>>
>I usually just open a new console when I need to do root stuff. It's as
>simple as hitting <CTRL>+<ALT>+<F2> (assuming you're running an X-session
>from the first TTY), doing your thing and going back to X.
>
>That said, I have the annoying habit of spending WAY too much time as root.
>But then again, there's nothing critical (yet) on my Linux box.
>
>Karel Jansens
>jansens_at_ibm_dot_net
>
>=======================================================
>"Give a man a fire and he's warm for a day,
>but set fire to him and he's warm
>for the rest of his life."
>
>(Terry Pratchett - Jingo!)
>=======================================================



------------------------------

From: Doug Paradis <[EMAIL PROTECTED]>
Subject: Adobe with RH5.2 - Error help
Date: Sat, 20 Feb 1999 16:30:28 -0500

I get the following error after I installed adobe reader for Linux and I
try to run acroread.

Any help for a newbie?

[root@linux bin]# /main/Acrobat3/Reader/intellinux/bin/acroread: can't
load library 'libXt.so.6'

Thanks
Doug Paradis


------------------------------

From: David Besse <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.networking
Subject: Re: Simple Samba question. . . I hope
Date: Fri, 19 Feb 1999 14:56:56 -0500

I've just been through this problem as well.  In your smb.conf file, make sure
you have:
    security = share

and this will enable you to at least view the resources available.  To connect
to a resource, you may also need to enable plain text passwords in the registry
of your Win machine:

HKEY_LOCAL_MACHINE\System\Current\ControlSet\Services\VxD\VNETSUP\
  then, select Edit->New->DWORD Value from the menu bar.  Rename the entry to
EnablePlainTextPassword, and set its value to 1.

or set up an smbpasswd file, and enable encrypted passwords on your linux
server, as Win98 by default uses encrypted passwords, and samba by default uses
plain text passwords.

Dave

Thom V wrote:

> Hello all,
>
> get the following message...
>
> Enter Network Password
> You must supply a network password to make this connection:
> Resource:  \\LinuxBox\IPC$
> Password:
>
> Doesn't "IPC" stand for something like "Inter Process Communication"?  Why
> do I need a password for this?  Is there a step that I've skipped?  What is
> the simplest way to resolve this and still keep some degree of security?
>
> Thanks,
> Thom Vandenberg


------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.misc) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Misc Digest
******************************

Reply via email to