Linux-Misc Digest #171, Volume #25 Tue, 18 Jul 00 16:13:02 EDT
Contents:
problem with PXE under linux ! HELP. ("Robichaud, Jean-Philippe [BAN:6S33:EXCH]")
Re: mgetty and dial in ("John G. Sandell")
Re: Need Library File (-ljl-)
Re: Another distro question... ("D F")
Re: Prompt for root account: Bash Shell problems ("Chris Pollock")
----------------------------------------------------------------------------
From: "Robichaud, Jean-Philippe [BAN:6S33:EXCH]" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.setup,comp.os.linux.networking,comp.sys.intel,comp.redhat.install,intel.network
Subject: problem with PXE under linux ! HELP.
Date: Tue, 18 Jul 2000 15:21:51 -0400
This is a multi-part message in MIME format.
==============9A41E489BC35AE64628F43F5
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
I try to boot a computer diskless. I have tried many configuration :
dhcp server only wiht bpbatch, dhcpserver on a computer + pxe sever on
another one, both dhcp and pxe servers on the same computer, I just
can't make it work. Here are the files of my actual configuration :
dhcp server and pxe server on the same computer. I have included my
/etc/services, /etc/pxe.conf, /etc/dhcpd.conf files so you can take a
look at it.
i have copied the vmlinuz from the cd to
/tftpboot/X86PX/UNDI/linux-boot/linux.1 and initrd-network.img in
/tftpboot/X86PX/UNDI/linux-install/linux.1
I have read the manuals and the howto, severals times, so don't tell me
to read it unless I have not see something obvious...
Thanks you for your help...
--
Jean-Philippe Robichaud
[EMAIL PROTECTED]
(514) 818-7750
(ESN) 888-7750
St-Laurent, Quebec, Canada
==============9A41E489BC35AE64628F43F5
Content-Type: text/plain; charset=us-ascii;
name="dhcpd.conf"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="dhcpd.conf"
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# Original file from the package
# Altered by JP Robichaud
# option definitions common to all supported networks...
option domain-name "mtlnis.com";
option domain-name-servers ca.nortel.com;
option subnet-mask 255.255.255.0;
default-lease-time 600;
max-lease-time 7200;
subnet 47.115.8.0 netmask 255.255.255.0 {
range 47.115.8.70 47.115.8.78;
option broadcast-address 47.115.8.255;
#default gateway
option routers 47.115.8.1;
next-server 47.115.8.68;
}
==============9A41E489BC35AE64628F43F5
Content-Type: text/plain; charset=us-ascii;
name="pxe.conf"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="pxe.conf"
# ******* PXE CONFIGURATION FILE *******
# Any Line starting with a '#" is treated as a comment line
# and ignored. However, '#' must be the first character on
# a line and no spaces before that are allowed.
# The following entry is the name of the interface on which pxe is going
# to operate. We use this interface to get the ip address automatically.
[Network_Interface_Name]
eth0
# The following entry will be queried if PXE fails to get
# the IP address automatically through 'ifconfig' like code built-in. This
# is only needed if the above interface name is not present in the system
[OurIpAddress]
47.115.8.68
# This entry shows the base directory of the mtftpd. All file names/paths
# will be relative to this directory. This is the same name that should
# be used as the start up argument to the mtftpd daemon.
[Mtftpd_Root_Directory]
/tftpboot
# Set the following entry to 0 if you have a DHCP server running on this
# system.
[UseDHCPPort]
0
# Set the entry below to zero if you don't want this system to act
# as a PXE proxyDHCP
[StartProxy]
1
# Set the entry below to zero if you don't want this system to act as a
# PXE boot server
[startBootService]
1
[MasterProxy]
1
# 0 - broadcast discovery is enabled; 1 - broadcast discovery is disabled
[Discovery_BCast_Disabled]
0
# 0 - multicast discovery is enabled; 1 - multicast discovery is disabled
[Discovery_MCast_Disabled]
0
# Multicast Discovery address. The boot server would listen on this address
# for multicast boot server packets.
[Discovery_MCast_Addr]
224.0.1.2
# Prompt to display on the user screen
# format of this entry: timeout,<string>
[Prompt]
10,Press F8 to view menu ...
# This entry is set to 1 if the client should accept only responses
# from servers in this list
[Discovery_Server_List_Only]
0
# the format of the discovery_list entry is as follows
# type of the server, # of entries, Ip address of each entry
# separated by commas
[Discovery_List]
#3,1,47.115.8.68
#65535,1,47.115.8.68
#3,2,192.215.100.49,192.215.100.99
# In some systems, the all '1' broadcast address 255.255.255.255
# won't work as the system will fail with a network unreachable message.
# In those cases, you can use the 'route add -host 255.255.255.255 eth0'
# command to add a route. Or else, you can define the host portion of the
# address alone as '1' in the following entry. This entry is not
# required if your system is set up to transmit
# broadcast packets on 255.255.255.255
[Broadcast_ip_address]
47.115.8.255
# Architectures supported
# format : <arch-type>,<arch-string>
[PROC_ARCH]
0,X86PC
# Boot server types supported
[Service_Types]
0,BStrap
13,linux-install
14,linux-boot
# Menu string that will be displayed on the client screen
# after F8 is pressed.
[X86PC/UNDI/MENU]
0,Local Boot
13,Remote Install Linux
14,Nothing
# Image file name for Linux install boot server type
# format : <min layer #> <max layer #> <base file name>
[X86PC/UNDI/redhat-install/ImageFile_Name]
0
1
linux
# Image file name for Linux boot server type
# format : <min layer #> <max layer #> <base file name>
[X86PC/UNDI/linux-boot/ImageFile_Name]
0
1
linux
# Image file name for BStrap boot server
# format : <min layer #> <max layer #> <base file name>
[X86PC/UNDI/BStrap/ImageFile_Name]
0
0
bstrap
# List of plug-ins. The PXEClientTester is the plug-in that
# validates received packets for PXE compliance. By default, this
# plug-in is DISBALED. Remove the '#" in front of it, if you want
# packet validation to happen
[Parsers]
PXEClientTester
PxeParser
[Parsers/PxeParser/MainFunction]
PxeParser
[Parsers/PxeParser/DllPath]
/usr/lib/libpxeParser.so
[Parsers/PXEClientTester/MainFunction]
PXEClientTester
[Parsers/PXEClientTester/DllPath]
/usr/lib/libpxeTester.so
# Even if the PXEClientTester is loaded, you still need to
# turn this flag to '1' for packet validation.
[TestOn]
1
# Directory where the results of the packet validation by PXEClientTester
# will be written to. Under this directory, there will be
# sub-directories with the last 8 digits of the MAc address of
# each client.
[TestPath]
/tmp
# Option DLL for BStrap
[X86PC/UNDI/BStrap/Vendor_Dll]
/usr/lib/libBstrapOpts.so
# Fill in a NT server name that will be contacted by the client
# to log back in for APitest
[ServerName]
#vviswana-desk2
# Specify whether the above server is in a domain or a workgroup
[IsDomain]
0
# specify the name of the workgroup or domain of the server
[Domain]
starwars
# All debug related stuff here
# If this entry is set to 1, pxe services will write
# more debug info to the system log using syslog()
[DEBUG/PxeServices_DebugOutToWindow_On]
1
# If this entry is set to 1, pxe parser will write
# more debug info to the system log using syslog()
[DEBUG/PxeParsers_DebugOutToWindow_On]
1
# If this entry is set to 1, pxe services will write
# more debug info to the file mentioned
# under the entry [DEBUG/PxeServices_Debug_FileName]
[DEBUG/PxeServices_DebugOutToFile_On]
1
# If this entry is set to 1, pxe parser will write
# more debug info to the file mentioned
# under the entry [DEBUG/PxeParsers_Debug_FileName]
[DEBUG/PxeParsers_DebugOutToFile_On]
1
[DEBUG/PxeServices_Debug_FileName]
/PxeServiceLog.txt
[DEBUG/PxeParsers_Debug_FileName]
/PxeParserLog.txt
[End]
==============9A41E489BC35AE64628F43F5
Content-Type: text/plain; charset=us-ascii;
name="services"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="services"
# /etc/services:
# $Id: services,v 1.4 1997/05/20 19:41:21 tobias Exp $
#
# Network services, Internet style
#
# Note that it is presently the policy of IANA to assign a single well-known
# port number for both TCP and UDP; hence, most entries here have two entries
# even if the protocol doesn't support UDP operations.
# Updated from RFC 1700, ``Assigned Numbers'' (October 1994). Not all ports
# are included, only the more common ones.
tcpmux 1/tcp # TCP port service multiplexer
echo 7/tcp
echo 7/udp
discard 9/tcp sink null
discard 9/udp sink null
systat 11/tcp users
daytime 13/tcp
daytime 13/udp
netstat 15/tcp
qotd 17/tcp quote
msp 18/tcp # message send protocol
msp 18/udp # message send protocol
chargen 19/tcp ttytst source
chargen 19/udp ttytst source
ftp-data 20/tcp
ftp 21/tcp
fsp 21/udp fspd
ssh 22/tcp # SSH Remote Login Protocol
ssh 22/udp # SSH Remote Login Protocol
telnet 23/tcp
# 24 - private
smtp 25/tcp mail
# 26 - unassigned
time 37/tcp timserver
time 37/udp timserver
rlp 39/udp resource # resource location
nameserver 42/tcp name # IEN 116
whois 43/tcp nicname
re-mail-ck 50/tcp # Remote Mail Checking Protocol
re-mail-ck 50/udp # Remote Mail Checking Protocol
domain 53/tcp nameserver # name-domain server
domain 53/udp nameserver
mtp 57/tcp # deprecated
#bootps 67/tcp # BOOTP server
#bootps 67/udp
#bootpc 68/tcp # BOOTP client
#bootpc 68/udp
pxe 67/udp
tftp 69/udp
#mtftp 1759/udp
gopher 70/tcp # Internet Gopher
gopher 70/udp
rje 77/tcp netrjs
finger 79/tcp
www 80/tcp http # WorldWideWeb HTTP
www 80/udp # HyperText Transfer Protocol
link 87/tcp ttylink
kerberos 88/tcp kerberos5 krb5 # Kerberos v5
kerberos 88/udp kerberos5 krb5 # Kerberos v5
supdup 95/tcp
# 100 - reserved
hostnames 101/tcp hostname # usually from sri-nic
iso-tsap 102/tcp tsap # part of ISODE.
csnet-ns 105/tcp cso-ns # also used by CSO name server
csnet-ns 105/udp cso-ns
# unfortunately the poppassd (Eudora) uses a port which has already
# been assigned to a different service. We list the poppassd as an
# alias here. This should work for programs asking for this service.
# (due to a bug in inetd the 3com-tsmux line is disabled)
#3com-tsmux 106/tcp poppassd
#3com-tsmux 106/udp poppassd
rtelnet 107/tcp # Remote Telnet
rtelnet 107/udp
pop-2 109/tcp postoffice # POP version 2
pop-2 109/udp
pop-3 110/tcp # POP version 3
pop-3 110/udp
sunrpc 111/tcp portmapper # RPC 4.0 portmapper TCP
sunrpc 111/udp portmapper # RPC 4.0 portmapper UDP
auth 113/tcp authentication tap ident
sftp 115/tcp
uucp-path 117/tcp
nntp 119/tcp readnews untp # USENET News Transfer Protocol
ntp 123/tcp
ntp 123/udp # Network Time Protocol
netbios-ns 137/tcp # NETBIOS Name Service
netbios-ns 137/udp
netbios-dgm 138/tcp # NETBIOS Datagram Service
netbios-dgm 138/udp
netbios-ssn 139/tcp # NETBIOS session service
netbios-ssn 139/udp
imap2 143/tcp imap # Interim Mail Access Proto v2
imap2 143/udp imap
snmp 161/udp # Simple Net Mgmt Proto
snmp-trap 162/udp snmptrap # Traps for SNMP
cmip-man 163/tcp # ISO mgmt over IP (CMOT)
cmip-man 163/udp
cmip-agent 164/tcp
cmip-agent 164/udp
xdmcp 177/tcp # X Display Mgr. Control Proto
xdmcp 177/udp
nextstep 178/tcp NeXTStep NextStep # NeXTStep window
nextstep 178/udp NeXTStep NextStep # server
bgp 179/tcp # Border Gateway Proto.
bgp 179/udp
prospero 191/tcp # Cliff Neuman's Prospero
prospero 191/udp
irc 194/tcp # Internet Relay Chat
irc 194/udp
smux 199/tcp # SNMP Unix Multiplexer
smux 199/udp
at-rtmp 201/tcp # AppleTalk routing
at-rtmp 201/udp
at-nbp 202/tcp # AppleTalk name binding
at-nbp 202/udp
at-echo 204/tcp # AppleTalk echo
at-echo 204/udp
at-zis 206/tcp # AppleTalk zone information
at-zis 206/udp
qmtp 209/tcp # The Quick Mail Transfer Protocol
qmtp 209/udp # The Quick Mail Transfer Protocol
z3950 210/tcp wais # NISO Z39.50 database
z3950 210/udp wais
ipx 213/tcp # IPX
ipx 213/udp
imap3 220/tcp # Interactive Mail Access
imap3 220/udp # Protocol v3
rpc2portmap 369/tcp
rpc2portmap 369/udp # Coda portmapper
codaauth2 370/tcp
codaauth2 370/udp # Coda authentication server
ulistserv 372/tcp # UNIX Listserv
ulistserv 372/udp
https 443/tcp # MCom
https 443/udp # MCom
snpp 444/tcp # Simple Network Paging Protocol
snpp 444/udp # Simple Network Paging Protocol
saft 487/tcp # Simple Asynchronous File Transfer
saft 487/udp # Simple Asynchronous File Transfer
npmp-local 610/tcp dqs313_qmaster # npmp-local / DQS
npmp-local 610/udp dqs313_qmaster # npmp-local / DQS
npmp-gui 611/tcp dqs313_execd # npmp-gui / DQS
npmp-gui 611/udp dqs313_execd # npmp-gui / DQS
hmmp-ind 612/tcp dqs313_intercell# HMMP Indication / DQS
hmmp-ind 612/udp dqs313_intercell# HMMP Indication / DQS
#
# UNIX specific services
#
exec 512/tcp
biff 512/udp comsat
login 513/tcp
who 513/udp whod
shell 514/tcp cmd # no passwords used
syslog 514/udp
printer 515/tcp spooler # line printer spooler
talk 517/udp
ntalk 518/udp
route 520/udp router routed # RIP
timed 525/udp timeserver
tempo 526/tcp newdate
courier 530/tcp rpc
conference 531/tcp chat
netnews 532/tcp readnews
netwall 533/udp # -for emergency broadcasts
uucp 540/tcp uucpd # uucp daemon
afpovertcp 548/tcp # AFP over TCP
afpovertcp 548/udp # AFP over TCP
remotefs 556/tcp rfs_server rfs # Brunhoff remote filesystem
klogin 543/tcp # Kerberized `rlogin' (v5)
kshell 544/tcp krcmd # Kerberized `rsh' (v5)
kerberos-adm 749/tcp # Kerberos `kadmin' (v5)
#
webster 765/tcp # Network dictionary
webster 765/udp
#
# From ``Assigned Numbers'':
#
#> The Registered Ports are not controlled by the IANA and on most systems
#> can be used by ordinary user processes or programs executed by ordinary
#> users.
#
#> Ports are used in the TCP [45,106] to name the ends of logical
#> connections which carry long term conversations. For the purpose of
#> providing services to unknown callers, a service contact port is
#> defined. This list specifies the port used by the server process as its
#> contact port. While the IANA can not control uses of these ports it
#> does register or list uses of these ports as a convienence to the
#> community.
#
ingreslock 1524/tcp
ingreslock 1524/udp
prospero-np 1525/tcp # Prospero non-privileged
prospero-np 1525/udp
datametrics 1645/tcp old-radius # datametrics / old radius entry
datametrics 1645/udp old-radius # datametrics / old radius entry
sa-msg-port 1646/tcp old-radacct # sa-msg-port / old radacct entry
sa-msg-port 1646/udp old-radacct # sa-msg-port / old radacct entry
radius 1812/tcp # Radius
radius 1812/udp # Radius
radacct 1813/tcp # Radius Accounting
radacct 1813/udp # Radius Accounting
cvspserver 2401/tcp # CVS client/server operations
cvspserver 2401/udp # CVS client/server operations
venus 2430/tcp # codacon port
venus 2430/udp # Venus callback/wbc interface
venus-se 2431/tcp # tcp side effects
venus-se 2431/udp # udp sftp side effect
codasrv 2432/tcp # not used
codasrv 2432/udp # server port
codasrv-se 2433/tcp # tcp side effects
codasrv-se 2433/udp # udp sftp side effect
mysql 3306/tcp # MySQL
mysql 3306/udp # MySQL
rfe 5002/tcp # Radio Free Ethernet
rfe 5002/udp # Actually uses UDP only
cfengine 5308/tcp # CFengine
cfengine 5308/udp # CFengine
bbs 7000/tcp # BBS service
#
#
# Kerberos (Project Athena/MIT) services
# Note that these are for Kerberos v4, and are unofficial. Sites running
# v4 should uncomment these and comment out the v5 entries above.
#
kerberos4 750/udp kerberos-iv kdc # Kerberos (server) udp
kerberos4 750/tcp kerberos-iv kdc # Kerberos (server) tcp
kerberos_master 751/udp # Kerberos authentication
kerberos_master 751/tcp # Kerberos authentication
passwd_server 752/udp # Kerberos passwd server
krb_prop 754/tcp # Kerberos slave propagation
krbupdate 760/tcp kreg # Kerberos registration
kpasswd 761/tcp kpwd # Kerberos "passwd"
kpop 1109/tcp # Pop with Kerberos
knetd 2053/tcp # Kerberos de-multiplexor
zephyr-srv 2102/udp # Zephyr server
zephyr-clt 2103/udp # Zephyr serv-hm connection
zephyr-hm 2104/udp # Zephyr hostmanager
eklogin 2105/tcp # Kerberos encrypted rlogin
#
# Unofficial but necessary (for NetBSD) services
#
supfilesrv 871/tcp # SUP server
supfiledbg 1127/tcp # SUP debugging
#
# Datagram Delivery Protocol services
#
rtmp 1/ddp # Routing Table Maintenance Protocol
nbp 2/ddp # Name Binding Protocol
echo 4/ddp # AppleTalk Echo Protocol
zip 6/ddp # Zone Information Protocol
#
# Services added for the Debian GNU/Linux distribution
poppassd 106/tcp # Eudora
poppassd 106/udp # Eudora
mailq 174/tcp # Mailer transport queue for Zmailer
mailq 174/tcp # Mailer transport queue for Zmailer
ssmtp 465/tcp # SMTP over SSL
gdomap 538/tcp # GNUstep distributed objects
gdomap 538/udp # GNUstep distributed objects
snews 563/tcp # NNTP over SSL
ssl-ldap 636/tcp # LDAP over SSL
omirr 808/tcp omirrd # online mirror
omirr 808/udp omirrd # online mirror
rsync 873/tcp # rsync
rsync 873/udp # rsync
simap 993/tcp # IMAP over SSL
spop3 995/tcp # POP-3 over SSL
socks 1080/tcp # socks proxy server
socks 1080/udp # socks proxy server
rmtcfg 1236/tcp # Gracilis Packeten remote config
server
xtel 1313/tcp # french minitel
support 1529/tcp # GNATS
cfinger 2003/tcp # GNU Finger
ninstall 2150/tcp # ninstall service
ninstall 2150/udp # ninstall service
afbackup 2988/tcp # Afbackup system
afbackup 2988/udp # Afbackup system
icp 3130/tcp # Internet Cache Protocol (Squid)
icp 3130/udp # Internet Cache Protocol (Squid)
postgres 5432/tcp # POSTGRES
postgres 5432/udp # POSTGRES
fax 4557/tcp # FAX transmission service (old)
pxe 4011/udp # PXE
hylafax 4559/tcp # HylaFAX client-server protocol (new)
noclog 5354/tcp # noclogd with TCP (nocol)
noclog 5354/udp # noclogd with UDP (nocol)
hostmon 5355/tcp # hostmon uses TCP (nocol)
hostmon 5355/udp # hostmon uses TCP (nocol)
ircd 6667/tcp # Internet Relay Chat
ircd 6667/udp # Internet Relay Chat
webcache 8080/tcp # WWW caching service
webcache 8080/udp # WWW caching service
tproxy 8081/tcp # Transparent Proxy
tproxy 8081/udp # Transparent Proxy
mandelspawn 9359/udp mandelbrot # network mandelbrot
amanda 10080/udp # amanda backup services
kamanda 10081/tcp # amanda backup services (Kerberos)
kamanda 10081/udp # amanda backup services (Kerberos)
amandaidx 10082/tcp # amanda backup services
amidxtape 10083/tcp # amanda backup services
isdnlog 20011/tcp # isdn logging system
isdnlog 20011/udp # isdn logging system
vboxd 20012/tcp # voice box system
vboxd 20012/udp # voice box system
binkp 24554/tcp # Binkley
binkp 24554/udp # Binkley
asp 27374/tcp # Address Search Protocol
asp 27374/udp # Address Search Protocol
tfido 60177/tcp # Ifmail
tfido 60177/udp # Ifmail
fido 60179/tcp # Ifmail
fido 60179/udp # Ifmail
# Local services
linuxconf 98/tcp
==============9A41E489BC35AE64628F43F5==
------------------------------
From: "John G. Sandell" <[EMAIL PROTECTED]>
Subject: Re: mgetty and dial in
Date: Tue, 18 Jul 2000 19:26:38 GMT
Bill Unruh wrote:
>
> In <[EMAIL PROTECTED]> "John G. Sandell"
><[EMAIL PROTECTED]> writes:
>
> Sorry to reply again:
> And also the
> data-only y
> option in mgetty.config
I reloaded the mgetty package from the SuSE CD and that got rid of the
fax initialization. Still no answer. Put the modem in AA mode and it
answered,so it wasn't a phoneline problem.
Bought a Hayes 56K fax modem andplugged it in - didn't change any
settings in linux. It worked right off the bat with all default settings
in linux and on the modem.
Bottom line: The USR 56K fax modem (BTW, I have two, and tried both)
doesn't work correctly with minicom. The Hayes does.
Haven't read the docs yet, but the Hayes box says "for Windows 95, 98,
NT4.0 and Linux Desktop Computers."
Thanks for your help.
John Sandell
------------------------------
From: -ljl- <[EMAIL PROTECTED]>
Subject: Re: Need Library File
Date: Tue, 18 Jul 2000 19:16:01 GMT
In article <[EMAIL PROTECTED]>,
Mike Fontenot <[EMAIL PROTECTED]> wrote:
>
> I need to replace a library file,
>
> libasound.so.1
>
> that somehow got deleted from my system. (It's in
> the /usr/lib directory). Can anyone
> tell me how to get a copy somewhere? Everywhere I've
> looked (including on my own SuSE 6.4 cd's), there are
> only packages (bundles of files), not individual files.
Find out what package contains the require file and just
re-install. This can be tricky. I think Yast, SuSE's
package management system, can handle this without problems.
SuSE used to provide a CD with all the packages as if installed.
This allowed one to make a minimum installation and then mount
the CD. They stopped doing that. Don't think you'll find the
individual files.
--
Louis-ljl-{ Louis J. LaBash, Jr. }
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "D F" <[EMAIL PROTECTED]>
Subject: Re: Another distro question...
Date: Tue, 18 Jul 2000 15:56:21 -0400
Mark Sidarous wrote in message ...
>Okay, (for now, only) I've decided to go with a
distribution that runs on
>a windows partition. WinLinux 2000 is attractive because
you can start it
>from within Windows, making it less OS (I know it still is)
like and more
>like a program which I boot up to do stuff. I've also
heard good things
>about PhatLinux. DragonLinux is cool because its small
(20M) and runs on
>a MS partition. Armed Linux is similar, I hear. So has
anyone used any
>(or all) of these distros? Are they crippled? Do they
work well?
>
>Thanks in advance.
>
>--Mark--
>
Well, I used WinLinux 200 for a time. It's a real Linux
distro, except that it runs on a FAT partition. The only
'advantage' I can see to it is that you don't have to
partition you HD to make it run.
I've heard others express the same opinion as you have, that
it's like another Windows program, but I found this not to
be the case. It's more like launching a DOS program from
Windows. You have to restart in MS-DOS mode to run it,
meaning you can't keep other Windows apps running or
anything like that. I'm not sure about how the program is
invoked, but I know the machine reboots into DOS before
opening Linux. I tried WinLinux 2000 as a newbie but I also
had another box on which I'd installed RedHat. I found
WinLinux to be not much different from RedHat (granted, from
a pure newbie perspective), and less secure, since it was
all sitting on the FAT partition and could easily be nuked
at the whims of BSODdom. In the end, I was attracted to a
native, ext2 installation because I liked the idea of having
things on separate partitions, so I could re-install parts
of the system or upgrade and not have to worry about blowing
away months of work.
In retrospect, I'd say that the time I spent tinkering with
WinLinux would have been much better invested in getting a
good Linux native installation up and running, 'cause this
is what I ended up doing anyway! ;-)
Dave Fluri
North Bay, Ontario Canada
------------------------------
Reply-To: "Chris Pollock" <[EMAIL PROTECTED]>
From: "Chris Pollock" <[EMAIL PROTECTED]>
Crossposted-To:
alt.linux,alt.os.linux,comp.os.linux,comp.os.linux.admin,comp.os.linux.help,comp.os.linux.networking,comp.os.linux.setup,linux.redhat.misc
Subject: Re: Prompt for root account: Bash Shell problems
Date: Tue, 18 Jul 2000 15:59:42 -0400
Thanks! Root account was using ash shell and not bash...
--
Chris Pollock
[EMAIL PROTECTED]
*Remove NOSPAM to respond to me via e-mail....*
Andrew E. Schulman <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> > I'm using Redhat 6.1 and I'm having problems getting my prompt to
display
> > correctly for my root account in the bash shell. It works fine under
all
> > other accounts.
> >
> > What's happening is when I either use su from another account or I logon
> > directly at the machine as root, my prompt shows up as \u@\h \W\$>
(under
> > any other account this shows up as username@hostname workingdirectory
$>)
>
> Are you sure that root's shell is bash? Sometimes root uses restricted
> shells such as ash for greater security. These shells have fewer
> features and may not recognize the tokens in your PS1.
------------------------------
** 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
******************************
