Re: [newbie] shuting down by ord. user..
> > Hmm. Maybe root isn't the only user who wants to shut down the system > > when he presses Ctrl+Alt+Del. Try comparing the $USERNAME against the > > names in shutdown.allow (a la a GAWK script). Would that work, guys? > > > > why not just compare 'id -u' with zero then? id? I haven't seen this before... Maybe I need another book.
RE: [newbie] compiler
Hi, I installed that, but it came back and said makeinfo missing (can't find that anywhere) and compiler can't make execuatable Thanks, Bob On Fri, 30 Jul 1999, you wrote: > Make sure the pgcc package is installed.
Re: [newbie] UNIX INTRO: Shell Processing
> $ cat < abcfile xyzfile > This is the contents of xyzfile > $ > > If anyone has an answer to this, tell us! Try tracing it. > We can use a very important trick to find out: set -x > - - What shells does that work with? UX, I know, but BASH? > $ set -x > $ > > $ cat < abcfile xyzfile > + cat xyzfile > + 0< abcfile > xyz > $ "0<"? > $ set -x > $ echo < xyzfile > + echo > + 0< xyzfile > > $ "0<"? > $ echo x > /dev/null > + echo x > + 1> /dev/null > $ "1>"? I've seen 2> before for redirecting STDERR. So, these streams have numbers... I know that 2 is for STDERR, and I can see (from the above example) that 1 is for STDOUT. 0? Nowhere? The bit bucket?
Re: [newbie] Re: X lockup
> Does your system stay running long enough for the cron jobs to process? I haven't done anything with cron. I have yet to read about what it's for. > You could have a ton of temp files and stuff waiting to be dumped. Should I just rm everything out of the /tmp directory?
Re: [newbie] Slow bandwith
In kppp check your connection speed. Setup -> Device -> Connection Speed Try setting it to 115200 and see if that helps. > mdk6.0 kppp says i am connecting @ 38400 but whenever i pull up a site, > ftp, download, etc., the maximum i pull is between 300- 600 bytes. under > windows i average between 2-3k. I have no idea where to even begin with > settings to fix this. thanks in advance. > > btw: it is a zoltrix 56k flex. not sure the exact model.
Re: [newbie] How to mount ATAPI ZIP Drive in Mandrake 6.0?
Jim, Make a directory in your /mnt/ directory called /zip from root prompt-- cd /mnt/ then mkdir /zip then go to your /etc/fstab file and add this line /dev/hdxx /zipvfatuser,noauto,rw 0 0 hdxx being whatever your zip drive is mine is hdd4 John - Original Message - From: Jim Snyder <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, July 30, 1999 5:58 PM Subject: [newbie] How to mount ATAPI ZIP Drive in Mandrake 6.0? > Hi > > Please help me get my Atapi Zip Drive recognized in Mandrake Linux 6.0. > > Many thanks in advance!!! > > Jim Snyder > [EMAIL PROTECTED] >
RE: [newbie] compiler
Make sure the pgcc package is installed. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Bob Schmidt > Sent: Friday, July 30, 1999 2:21 PM > To: Linux-Mandrake Newbie > Subject: [newbie] compiler > > > Hi All, > > I'm pretty new at this stuff, I'm trying to install kxicq on my > machine. But > it says that I need a compiler, well I looked through my mandrake > 6 box and > installed colorgcc. But when I run ./configure it says that the gcc can't > create an excutable. Any ideas on what I should do? > > Thanks, > Bob >
Re: [newbie] Mylex D960PG problem
Do you check in the Bios of the MylexD960PG... Probably you boot directly on the Raid system. Do you have another hard drive in your box? If you have an hard drive try to boot the rootfs on this drive and then activate and mount your raid system. Hope this help Carl St-Jacques - Original Message - From: Victor Zaitsev <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, July 30, 1999 1:40 PM Subject: [newbie] Mylex D960PG problem > I have some problems with RAID-5 and Mandrake 6.0 > When I install Linux, it find correctly my Mylex D960PG > After finishing installation and the first reboot , > Mandrake can't mount rootfs > > Anybody know what can I do? > >
Re: [newbie] SCSI
Jasontry this URL and see if it helps. http://www.cvlug.org/hp/cfg_401.html Alan -Original Message- From: Jason Cotterell <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Friday, July 30, 1999 12:55 PM Subject: [newbie] SCSI >I have mandrake 5.3 and i can't seem to find any way to make it see my >adaptec scsi controller. i have a 4x6 cd-r and a 9.1 GB quantum scsi >drive hooked to itand i really need to mount it in linux. >also does anyone know any good linux cd-r software. >thanks for alll your help >
[newbie] How to mount ATAPI ZIP Drive in Mandrake 6.0?
Hi Please help me get my Atapi Zip Drive recognized in Mandrake Linux 6.0. Many thanks in advance!!! Jim Snyder [EMAIL PROTECTED]
[newbie] compiler
Hi All, I'm pretty new at this stuff, I'm trying to install kxicq on my machine. But it says that I need a compiler, well I looked through my mandrake 6 box and installed colorgcc. But when I run ./configure it says that the gcc can't create an excutable. Any ideas on what I should do? Thanks, Bob
Re: [newbie] shuting down by ord. user..
Opps i wasn't done, On Fri, 30 Jul 1999, Axalon wrote: > > > On Fri, 30 Jul 1999, Theo Brinkman wrote: > > > Ok, you guys are getting a bit over my head at this point. I'm very > > much a newbie at scripting stuff, so some examples would be nice. > > > > Here's the script as it stands: > > - - > > #!/bin/sh > > # Shutdown on Ctrl+Alt+Delete based on User. > > > > if [ id -u == 0 ]; then #if user is administrator > > halt > > else > > logout > > fi > > - - > > > > I've got a few questions about it. > > > > 1. Might a check against 'id -g' work better? (In case you have more > > than one login in the 'root' group) > > > > 2. I'm not familiar enough with gawk to do any scripting with it yet, > > anybody feel like taking a crack at either of the two gawk related > > suggestions? > > > > > > I love an educational process. Thanks guys. > > > > - Theo > Uhh, no not really. -=-= #!/bin/bash DEBUG=1 if [ "$DEBUG"x = "1"x ]; then TEST="logger -is " else TEST="" fi # Shutdown on Ctrl+Alt+Delete based on UID IAM=`id -u` if [ "$DEBUG"x = "1"x ]; then $TEST "$IAM" $TEST `tty` fi if [ "$IAM"x = "0"x ]; then $TEST "halt " #Is root else $TEST "logout " #Not root fi -=-= > > Axalon wrote: > > > > > > On Fri, 30 Jul 1999, Andy Goth wrote: > > > > > > > > > How about creating a quick script '/etc/threefingersalute', like the one > > > > > > below: > > > > > > - - > > > > > > if [ $USERNAME = "ROOT" ]; then > > > > > > > > > > $USER $USERNAME or $LOGNAME, bash manpages will give you info on what each > > > > > is, the "ROOT" should be "root" it's case sensitive. This might work, but > > > > > without double checking i'm pretty sure it'll be a problem that init runs > > > > > as root and this does not actualy run on the current console when you > > > > > call it with. > > > > > > > > It doesn't have to be root. If you wanted to, you could change root's > > > > name to something else by hacking the /etc/passwd file. The superuser > > > > (usually root) is the one with the user id of 0. You could write a GAWK > > > > program that would scan for the line with the user id of 0 and print the > > > > corresponding username (and you would capture the output and compare it > > > > to $USERNAME). > > > > > > > > Hmm. Maybe root isn't the only user who wants to shut down the system > > > > when he presses Ctrl+Alt+Del. Try comparing the $USERNAME against the > > > > names in shutdown.allow (a la a GAWK script). Would that work, guys? > > > > > > > > > > why not just compare 'id -u' with zero then? > > > >
Re: [newbie] low port privs
On Fri, 30 Jul 1999, David Kammer wrote: > Hi All, > Odd question. It seems as if only root is allowed to start proccesses > with low port numbers like 80 (httpd is not running on my machine). when > non-su's try to do this, the port allocation simply fails. My question is > is there a way to allow a user to start low port proccesses without giving > them full su status? > thanks, > -dave There are various solutions, but this is one I have been given privileges with. Others can provide more complete info... Sudo - a utility to allow restricted root access Sudo (superuser do) allows a system administrator to give certain users (or groups of users) the ability to run some (or all) commands as root while logging all commands and arguments. Sudo operates on a per-command basis, it is not a replacement for the shell. http://www.courtesan.com/sudo/ best wishes, richard myers
Re: [newbie] shuting down by ord. user..
On Fri, 30 Jul 1999, Theo Brinkman wrote: > Ok, you guys are getting a bit over my head at this point. I'm very > much a newbie at scripting stuff, so some examples would be nice. > > Here's the script as it stands: > - - > #!/bin/sh > # Shutdown on Ctrl+Alt+Delete based on User. > > if [ id -u == 0 ]; then #if user is administrator > halt > else > logout > fi > - - > > I've got a few questions about it. > > 1. Might a check against 'id -g' work better? (In case you have more > than one login in the 'root' group) > > 2. I'm not familiar enough with gawk to do any scripting with it yet, > anybody feel like taking a crack at either of the two gawk related > suggestions? > > > I love an educational process. Thanks guys. > > - Theo Uhh, no not really. -=-= #!/bin/bash DEBUG=1 if [ "$DEBUG"x = "1"x ]; then TEST="logger -is " else TEST="" fi # Shutdown on Ctrl+Alt+Delete based on UID IAM=`id -u` if [ "$DEBUG"x = "1"x ]; then $TEST "$IAM" fi if [ "IAM"x = "0"x ]; then $TEST "halt " #Is root else $TEST "logout" #Not root fi > Axalon wrote: > > > > On Fri, 30 Jul 1999, Andy Goth wrote: > > > > > > > How about creating a quick script '/etc/threefingersalute', like the one > > > > > below: > > > > > - - > > > > > if [ $USERNAME = "ROOT" ]; then > > > > > > > > $USER $USERNAME or $LOGNAME, bash manpages will give you info on what each > > > > is, the "ROOT" should be "root" it's case sensitive. This might work, but > > > > without double checking i'm pretty sure it'll be a problem that init runs > > > > as root and this does not actualy run on the current console when you > > > > call it with. > > > > > > It doesn't have to be root. If you wanted to, you could change root's > > > name to something else by hacking the /etc/passwd file. The superuser > > > (usually root) is the one with the user id of 0. You could write a GAWK > > > program that would scan for the line with the user id of 0 and print the > > > corresponding username (and you would capture the output and compare it > > > to $USERNAME). > > > > > > Hmm. Maybe root isn't the only user who wants to shut down the system > > > when he presses Ctrl+Alt+Del. Try comparing the $USERNAME against the > > > names in shutdown.allow (a la a GAWK script). Would that work, guys? > > > > > > > why not just compare 'id -u' with zero then? >
RE: [newbie]Change the command line prompt
On Fri, 30 Jul 1999, Griffin, Michael wrote: > how do i change the command line prompt from ["username"@localdomain > /"directory"]#or$ to something more minimal say just something like > $"/directory"> or #"/directory"> (depending on the user). it is my > perceived understanding that the difference for the "#" sign and the "$" > sign is there to denote whether one is a user or root. > i would like to make this a global change for all users so i am guessing > that a ".rc" file will need to be edited. > all help is greatly appreciated. > thanx, > michael (this is a quickie canned answer-- adapt as needed) Here is some info about your BASH command prompt, and about the startup sequence of your shell. The command prompt is stored in the PS1 variable. You can type "set" and you will see a list of all your current variable settings. The PS1 variable could be set in a number of places-- either a global startup file, or an individual user startup file. One setting for username is: PS1="\u--> " The current directory is: PS1="\w--> " If you combine \u and \w, you get both. The other stuff-- in other words, the --> can be whatever you wish. The trailing space is a nice thing to have, however. S--- you can change easily by modifying a bash startup file. Which file? Well, first go to the command prompt and find out if it is already being set somewhere. First check for the prompt in a global startup file. This may be /etc/profile, or possibly /etc/bashrc. I'm currently using a Sun, but your Linux experience should be similar. We are going to use the grep command: grep PS1 /etc/* ...from a command prompt. Note that where I have just a $, you may have something different: $ grep PS1 /etc/* grep: can't open /etc/initpipe grep: can't open /etc/oshadow /etc/profile:PS1=">>" /etc/profile:PS1=">>#" /etc/profile:export PS1 grep: can't open /etc/shadow grep: can't open /etc/utmppipe $ The first part of the line shows the filename. Ignore the errors. Aha! My PS1 variable is set initially in the /etc/profile file. This means that it is set to this value for everyone on the system, because any file in the /etc directory is likely a global setting. (But each user can set it again to something different.) Notice that the actual, global system code doesn't show up with grep-- we only see lines that include the "PS1" string of characters. If we actually look at (my) /etc/profile file, we see this: PS1=">>" if [ "$LOGNAME" = "root" ] then PS1=">>#" fi export PS1 Well, I spoke too soon. My $ prompt doesn't match this code, so I have to look further. Actually, my PS1 is redefined in my .profile file: $ grep PS1 ~/.* .bash_history:grep PS1 * .profile:PS1="$ " .profile:export PS1 PS2 $ Ignore the .bash_history entry. Note that for the BASH shell, your value for PS1 will be slightly different from my (Sun) prompt. If you are logging in as root, you get the # in your prompt instead of the $ . But all that is needed to set my user prompt would be: PS1= (something) ...and, so that the change is propagated to all shell logins, export PS1 You may wish to check the individual user files too-- each user can customize their own PS1 variable. To see if it is set up in your user startup files, type: cd grep PS1 ~/.* ...where ~/ (if it is set up properly) is your home directory, and .* is a wildcard for searching all filenames that start with a period. The three likely files to set the PS1 variable in your home directory are .bash_profile, .bashrc, and .profile. The difference between .bash_profile and .bashrc? Having two files gives you the flexibility to separate startup commands needed at login time (.bash_profile) from those you might need when you run a subshell (.bashrc). So, I'd change .bash_profile for a user account (although you could have different settings for subshells, too.) Global files in /etc are run first, and then the user files in the home directory are run. The last file to set and export PS1 will rule. I'd try changing PS1 in a user login first, if you haven't had much experience with editing text files in UNIX/Linix. Open your .bash_profile with commands such as: cd pico .bash_profile (substitute your favorite editor for pico, but pico is very easy to use...) Find out where variables are set (if you already have a .bash_profile-- it is possible to use the /etc/profile file for all setup). Change the PS1 variable to what you want. Don't forget to export it! Some other settings for PS1: \d date \H hostname \h abbreviated hostname \n a carriage return and linefeed \T time \t time, another format \@ time, yet another format \u user name \v version of bash \V release version of bash \w current working directory \W abbreviated current working directory \# command number of the current prompt \! command history number
RE: [newbie]Change the command line prompt
You might be interested in the Bash-Prompt-HOWTO. It goes into much more detail than I can/will here, and should be available in /usr/doc/HOWTO or if you didn't install the documentation, at http://metalab.unc.edu/LDP/HOWTO/Bash-Prompt-HOWTO.html Basically, the prompt is stored in the PS1 environment variable. This can include environment variables, and special backslash-escaped variables including the following (`man bash` for an exhaustive list): \h the hostname up to the first `.' \H the hostname \u the username of the current user \w the current working directory \W the basename of the current working directory \$ if the effective UID is 0, a #, otherwise a $ Thus, the default prompt is PS1="[\u@\h \W]\$ ". you can see this by typing `set`, which shows a list of all environment variables. The way to set the prompt on login is to put this command in one of the scripts that bash runs when it starts. According to the bash man page, bash will execute /etc/profile first, then one of ~/.bash_profile, ~/.bash_login, or ~/.profile, whichever comes first. ~/.bash_profile should exist, and should tell bash to run ~/.bashrc if it exists. ~/.bashrc should be telling bash to run /etc/bashrc. Thus, if you put the PS1 command in /etc/bashrc, it will be run for all users, and will overwrite the prompt setting in /etc/profile, but each user still has the option to overwrite your prompt by appending their own PS1 command to ~/.bashrc. In the above paragraph, ~ stands for the user's home directory (same as $HOME). I hope this gives you something to start from. Remember that the HOWTO goes into much more depth on the subject, including colors and running commands inside the prompt! -Matt
Re: [newbie] UNIX INTRO: lessons declared open source
An aside..Or should I say: A peripheral issue.. I don't work with computer technology except to type lesson plans and make instructional materials for ESL classes I teach to adults. So, much of what I study about Unix or Linux is lost through my lack of use of it in my daily work. So, I wonder if there is somewhere a list of problems and solutions for Unix or Linux, a workbook as it were. Something that presents technical problems to the nontechnical user to help us practice what we learn. And I am approaching 60 years of age, so I find this to be even more necessary as my memory and learning capacities begin to slowly shutdown. Does anyone know of such a thing? Is anyone interested in collaborating on creating such a thing? By the way, I use linux as a desktop system, and I like 3% more than Windows. All the stuff about it not being ready for prime time is bullshit. adios, STeve W --- Richard Myers <[EMAIL PROTECTED]> wrote: > > Because: > > o Open source works better than closed source; and > > o The lessons were developed partly using ksh > rather than BASH; and > > o It is entirely possible that there could be > undetected errors; and > > o Additional contributors will make the lessons > better, I hereby > declare: > > ...that everyone is invited and welcome to test the > lessons on their Linux > installations, particularly using the BASH shell, > and to send me any > corrections, suggestions for improvements, > suggestions for new lessons, or > even developed lessons in similar format. > > Maybe we can make something worthwhile out of these > sessions for all new > Linux users. (No, I'm not going to go to all the > trouble of issuing a GPL > at this time... grin...) > > Note: I'm not experienced enough (by a few > lightyears!) to offer similar > material on system admin issues. Well, there is the > Linux Documentation > Project. But that is more task-oriented than > training-oriented. > > There may already be worthwhile efforts of this sort > somewhere in > cyberspace, which could provide cross-fertilization. > Anyone know of any? > > > best wishes, > > richard myers > > _ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com
Re: [newbie] shuting down by ord. user..
Hmm. on 'echo $USERNAME' I get root if I've logged in as root, even while logged in as someone else with 'su', but nothing if I've logged in as anyone else, unless I've done a 'su root' in which case I get 'root. With 'echo $LOGNAME' I get the user currently logged in as, for example, bob if I've typed 'su bob'. I'd like it to catch any case of me being 'root', so I think I'm going to stick with $USERNAME, perhaps later adding in a message to 'root' somehow about such & such a user (determined by $LOGNAME) shutting down as 'root'. - Theo Matt Stegman wrote: > > > How about creating a quick script '/etc/threefingersalute', like the one > > below: > > - - > > if [ $USERNAME = "ROOT" ]; then > > I'd suggest you use $LOGNAME instead of $USERNAME. On my system, `echo > $USERNAME` returns nothing. `echo $LOGNAME` on the other hand, returns > the username of whoever's logged in. It works just fine with `su` too. > Also, "root" should be lowercase. > > > halt > > else > > logout > > fi > > Other than that, it looks good. > > -Matt
RE: [newbie]Change the command line prompt
here is a basic question. how do i change the command line prompt from ["username"@localdomain /"directory"]#or$ to something more minimal say just something like $"/directory"> or #"/directory"> (depending on the user). it is my perceived understanding that the difference for the "#" sign and the "$" sign is there to denote whether one is a user or root. i would like to make this a global change for all users so i am guessing that a ".rc" file will need to be edited. all help is greatly appreciated. thanx, michael
Re: [newbie] Re: X lockup
>> > > Ctrl-Alt-Backspace shuts down X >> > >> > It's supposed to, but it took maybe an hour for it to respond. Usually >> > it's instant, but it wasn't in this case. >> >> A second is more like it. You've got something stealing cycles in a big way! > >The problem is that a _lot_ of different things can cause these >temporary lockups in which the only thing that'll be noticed by the >computer is a power failure (intentional or otherwise). Let's see... I >had this problem while playing with xfontsel under GNUstep and fvwm2 on >a system running Red Hat 5.0. It's probably important that you know >that this is on a 486SX/25MHz machine with 24MB actual RAM. There don't >appear to be any disk accesses or other little noises indicating >anything going under the hood. If any real processing is going on, it's >all in RAM. I noticed a fvwm2 error log file in ~/andy today. I read >it: It was a huge list of /tmp files it tried deleting but couldn't >since I didn't have permission to. I wonder if that has anything to do >with these lockups. Does your system stay running long enough for the cron jobs to process? You could have a ton of temp files and stuff waiting to be dumped. Brian
Re: [newbie] Boot from hard drive
On Thu, 29 Jul 1999, [EMAIL PROTECTED] wrote: > I installed Mandrake Linux 6.0 in my hard drive (linux only). It works > fine when it boot from floppy disk. But I can't boot from hard drive > and error message prompted. > > ERROR LOADING OS > > > How do I get LILO boot from hard drive? > Boot to your Linux (using the floppy) and go to your /etc directory and look at your lilo.conf file to make sure all the options are correct, then run "lilo" at the prompt.
Re: [newbie] ISDN configuration
AS far as I know the gate way is set right. All the windows machines in the office have a gateway of 216.172.53.65. That's what I set my Linux to. Where are the ISDN tools in linux? I am a little lost as I have only had Linux for two weeks now. I would use it alot more if I could switch my e-mail and use the internet on it. Thanks - Original Message - From: Travis Kriza To: [EMAIL PROTECTED] Sent: Thursday, July 29, 1999 8:34 PM Subject: Re: [newbie] ISDN configuration Question, is the isdn line hooked into a router? Or is it going through the linux machine first? If it is going through a router, all you should need to do is set your gateway address to the ip address of the router. Otherwise I am not sure but I believe there are several tools included on the CD that are for ISDN configuration. - Original Message - From: Tom Fisher To: [EMAIL PROTECTED] Sent: Thursday, July 29, 1999 4:04 PM Subject: [newbie] ISDN configuration This is my first start at linux, and I am stuck I installed Mandrake 6.0 from CD. Configured everything to the best of my knowledge (not much) set it for custom not server, but running a network at office (I set the IP address and host name to what is on my Windows OS, it is a dual boot) I want to know how to configure an ISDN line. I can't figure out how to make Linux recognize the ISDN line and not a dial-up. Thanx, Tom
Re: [newbie] Loading modules?
"Dan Brown" <[EMAIL PROTECTED]> writes: > Where do I specify what modules to load at boot time? Currently, > some modules load, while others do not. Particularly, the tulip and sg > modules do not load. I can manually load them as root by typing > /sbin/insmod, but that's a bit of a pain. Thanks for any info! /etc/conf.modules
[newbie] UNIX INTRO: lessons declared open source
Because: o Open source works better than closed source; and o The lessons were developed partly using ksh rather than BASH; and o It is entirely possible that there could be undetected errors; and o Additional contributors will make the lessons better, I hereby declare: ...that everyone is invited and welcome to test the lessons on their Linux installations, particularly using the BASH shell, and to send me any corrections, suggestions for improvements, suggestions for new lessons, or even developed lessons in similar format. Maybe we can make something worthwhile out of these sessions for all new Linux users. (No, I'm not going to go to all the trouble of issuing a GPL at this time... grin...) Note: I'm not experienced enough (by a few lightyears!) to offer similar material on system admin issues. Well, there is the Linux Documentation Project. But that is more task-oriented than training-oriented. There may already be worthwhile efforts of this sort somewhere in cyberspace, which could provide cross-fertilization. Anyone know of any? best wishes, richard myers
[newbie] UNIX INTRO: Shell Processing
If you feel the material I've been sending out has been too advanced, please send me email (it doesn't need to go to the maillist, unless you want it to...) at: [EMAIL PROTECTED] ...to let me know. We can do an intro to the intro. Some of the material in this lesson is *intermediate* level. Don't feel bad if this material seems confusing for beginners. I'm hoping it may be challenging (perhaps even stimulating) for those who've been doing UNIX for a while. -- Shell Processing -- -- Digest -- The kernel is the software "brain" of the computer system. The kernel performs low-level and system-level functions. The kernel communicates in a language that is complex and highly technical. The shell is built around the kernel. The shell is that part of a UNIX/Linux system that protects you, the user, from the complexity of the kernel, and protects the kernel from any inappropriate input by the user. In this lesson we will explore how the shell processes the command line. We have already discussed the ways in which UNIX utilities can be combined to create powerful tools. Such techniques can be applied in scripts, or can be typed in directly at the command line. In fact, the shell processes each line of a script in a very similar fashion to processing the command line. Each command offered to the command prompt is first evaluated by the shell. Some testing occurs, and if all goes well, a (possibly modified) command string is processed, and data is passed to or collected from any utilities which are called. [ Quickie definitions: a command is how you tell the system to do something. Specifically, a command is a series of characters that you type. A command may call a utility, which is simply a program on the system which may be used for a particular purpose. Utility programs are sometimes referred to as tools. A command may also call a script, or execute some other shell function. ] o The shell launches programs, maintains variables, handles redirection and pipes, expands wildcards, and interfaces with the filesystem. o Data may be channeled to or collected from files via redirection. o Utilities operate on data according to their specific function, taking input as command line arguments, or as standard input passed from the shell via pipes. o The shell and the utilities work together to process information. In other words, the shell does some things, and the utilities do some things. By experimentation, it is possible to discover which does what. -- In-depth -- -- Redirection -- Here is a clue to an earlier lesson's mystery: the redirection filename may be anywhere in the argument list. We can echo characters to a file: $ echo xyz > xyzfile $ cat xyzfile xyz $ If we insert a space between the characters, the space is preserved: $ echo x y z > xyzfile $ cat xyzfile x y z $ This is because the x, y, and z become separate arguments, and arguments are separated by a space. If we insert a lot of spaces, they are condensed to one space: $ echo x y z >xyzfile $ cat xyzfile x y z $ Now lets put the redirection before the string to be redirected. First (for test purposes) we will insure that the file is an empty file: $ > xyzfile $ cat xyzfile $ ...and then: $ echo > xyzfile xyz $ cat xyzfile xyz $ ...and the redirection still works. We can even put the redirection in the middle of the string. Zero the file again: $ > xyzfile $ cat xyzfile $ ...and now our test: $ echo x > xyzfile y z $ cat xyzfile x y z $ The redirection command consists of the redirection character, and what it points to. In this case, the redirection command consists of: > xyzfile It doesn't matter where the redirection command is in the argument list. The shell will extract it, and process accordingly. OK, confession time. Zeroing the file really isn't necessary in the above examples. Simple redirection overwrites whatever was in the file. I just wanted to make the point that nothing was left over from before. Introducing standard error, and the difference between echo and cat We have been dealing with output redirection. Now lets take a look at input redirection and standard error as we explore the difference between echo and cat. Standard error is (normally) written to the screen, just like standard output. Study this series of commands for a moment: $ echo This is the contents of xyzfile > xyzfile $ $ cat xyzfile This is the contents of xyzfile $ $ echo < xyzfile x y z x y z $ $ cat < xyzfile This is the contents of xyzfile $ $ cat < xyzfile x y z ksh: cat: x: cannot open [No such file or directory] ksh: cat: y: cannot open [No such file or directory] ks
Re: [newbie] Removing LILO
You remember correctly , And yes , 98 is as rude as 95 . - Original Message - From: Thomas J. Hamman <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, July 29, 1999 6:16 PM Subject: RE: [newbie] Removing LILO > On 29-Jul-99 Dennis Podein wrote: > > Hello , here is my dilemma . I have to clean out this computer > > , remove linux and set it up with windows 98 for my daughter > > for college . Anyway , I MS Fdisked it , then formatted it . > > When it goes to boot , LILO kicks in . I thought that would be > > gone . MS Fdisk doesn't find it , neither does disk druid , or > > linux Fdisk . How do I get LILO out of here ? > > With the DOS/Windows fdisk, type 'fdisk /mbr' to delete LILO from the Master > Boot Record. > > Also if I remember correctly (and if Win98 is as rude as 95), the Windows > installation wipes the MBR without asking for permission anyway. > > > -Tom
Re: Re[2]: [newbie] Boot from hard drive
On Fri, 30 Jul 1999 [EMAIL PROTECTED] wrote: > My Hard drive partition as following: > > mount bootable flag devfs type > -- > / * hda1 linux native >hda2 linux swap > /home hda3 linux native > > I set bootable flag on first partition which contain first sector and MBR, > but still can't boot from hard drive. > Sorry forgot what list i was in, You'll also need to reinstall lilo on the disk, check for a /etc/lilo.conf, verify the paths and such aren't blatantly wrong and run /sbin/lilo > You'll need to set the bootable flag on atleast one partition > > On Fri, 30 Jul 1999 [EMAIL PROTECTED] wrote: > > > I installed Mandrake Linux 6.0 in my hard drive (linux only). It works > > fine when it boot from floppy disk. But I can't boot from hard drive > > and error message prompted. > > > > ERROR LOADING OS > > > > > > How do I get LILO boot from hard drive? > > > > > > > > > >
Re: [newbie] looking at my pc files from Linux
> Why all the fuss? It is possible to mount WIN98 fat32 partitions. Simply > download your stuff on the windows machine and mount the partition the *.gz > files are stored on. I've used it for ages. I know to mount a plain DOS disk with: mount -t msdos /dev/hXX /mnt/Y (hXX is, for example, hda1; Y is, for example; c:--the mount point) mount -t vfat /dev/hXX /mnt/Y will mount a DOS disk "augmented" by Windows to support long file names. What more do you need to know?
Re: [newbie] Past messages file?
They are linked from the main website On Thu, 29 Jul 1999, sledge151 wrote: > Where do I need to go to find a collection of the past newsgroups postings? > I remember somebody awhile back asking but I don't remember the location. > Thanks. > > > NetZero - We believe in a FREE Internet. Shouldn't you? > Get your FREE Internet Access and Email at > http://www.netzero.net/download/index.html >
