Linux-Misc Digest #643, Volume #27 Wed, 18 Apr 01 21:13:02 EDT
Contents:
Re: Aliases in .bashrc and .tcshrc (Mike Delaney)
Re: About Virtual Hosting, plz HELP ("Natman")
FAQ lacks scanner info (Dan Jacobson)
Re: Aliases in .bashrc and .tcshrc (Bill Unruh)
Is this a bad thing? (patch errors) ("Christopher R. Carlen")
HOTLINE port 5500 and IPCHAINS ("dubcaller")
Re: Which distro for 2.4.x ? (Christian Rose)
Re: Am I ****? HP Photosmart C500 and Win 2000 ("Boyce Endertois")
Re: Which distro for 2.4.x ? (Christian Rose)
Re: Which distro for 2.4.x ? (Christian Rose)
Re: Which distro for 2.4.x ? (Christian Rose)
Re: Ctrl+Alt+F1?? and more (Garry Knight)
Handspring Visor With Korganizer
Re: Which distro for 2.4.x ? (David)
PC NFS server? (* Tong *)
Re: RedHat 7.1 too early ?,... (Christian Rose)
Re: RedHat 7.1 too early ?,... (Christian Rose)
Re: RedHat 7.1 too early ?,... (Christian Rose)
Re: RedHat 7.1 too early ?,... (Christian Rose)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Mike Delaney)
Crossposted-To: comp.unix.shell,poster
Subject: Re: Aliases in .bashrc and .tcshrc
Date: 18 Apr 2001 21:40:42 GMT
On Tue, 17 Apr 2001 10:53:30 +0200 in <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] said something similar to:
:
:
: Alex Vinokur wrote:
:
: > -----------------------------------------------
: > #uname -a
: > Linux gcc 2.2.17-21mdk #1 Thu Oct 5 13:16:08 CEST 2000 i586 unknown
: > -----------------------------------------------
: >
: > I defined the following alias in .tcshrc
: > alias fnd 'find . -name \!* -print'
: > It works, for instance :
: > fnd abcd.
: >
: > I tried to define following aliases in .bashrc
: > alias fnd1='find . -name !* -print'
: > alias fnd2='find . -name \!* -print'
: >
: > It doen't work :
: > [root@gcc /]# fnd1 abc
: > find: paths must precede expression
: > Usage: find [path...] [expression]
: >
: > [root@gcc /]# fnd2 abc
: > find: paths must precede expression
: > Usage: find [path...] [expression]
: >
: > What is wrong?
: > How to define in .bashrc alias fnd identical the same alias in .tcshrc?
:
: We can do it in .bashrc using function :
:
: function fnd
: {
: find / -name "$1" -print
: }
: It works OK.
:
: Can we do it using alias?
No. Aliases in bash (and ksh) can't take arguments. The use of
a shell function as you've done above is the correct way to do
this.
That said, in this particular case, the -print argument to find(1)
is redundant, so you could do:
$ alias fnd='find . -name'
$ fnd abc
--
Mike Delaney <[EMAIL PROTECTED]>
"...Microsoft follows standards. In much the same manner that fish follow
migrating caribou." "Now I have this image in my mind of a fish embracing and
extending a caribou." -- Paul Tomblin and Christian Bauernfeind in the SDM
------------------------------
From: "Natman" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.admin,comp.protocols.dns,comp.unix.admin,japan.www.server.apache
Subject: Re: About Virtual Hosting, plz HELP
Date: Wed, 18 Apr 2001 22:26:41 GMT
> >>>>>>>>
> ServerType standalone
> ServerRoot "/usr/local/apache"
> ServerAdmin [EMAIL PROTECTED]
> ServerName www.hkix.com
> DocumentRoot /home/hkix/htdocs
> ScriptAlias /cgi-bin/ /home/hkix/cgi-bin/
>
> NameVirtualHost 202.66.165.84
>
> <VirtualHost 202.66.165.84>
Should be <VirtualHost www.waptomail.com>
> ServerName www.waptomail.com
> DocumentRoot /home/waptomail/htdocs
> </VirtualHost>
then you should have
<VirtualHost www.hkix.com>
ServerName www.hkix.com
DocumentRoot /home/hkix/htdocs
</VirtualHost>
Note that if a person enters the IP address, apache will use the info
that's not in the <VirtualHost> tags, this also applies for browsers which
do not use HTTP/1.1. I believe this is the way I had mine setup (before I
stopped using virtualhosts).
Natman
------------------------------
From: Dan Jacobson <[EMAIL PROTECTED]>
Subject: FAQ lacks scanner info
Date: 19 Apr 2001 03:51:12 +0800
Linux first impressions for looking for info about how to
use my scanner:
$ grep -i scan /usr/share/doc/FAQ-Linux/*
/usr/share/doc/FAQ-Linux/Linux-FAQ-4.html:about scanning the bus for bootable devices.
apropos scan gave a clue about "sane"...
--
http://www.geocities.com/jidanni Tel886-4-25854780 e-mail:restore .com.
------------------------------
From: [EMAIL PROTECTED] (Bill Unruh)
Crossposted-To: poster
Subject: Re: Aliases in .bashrc and .tcshrc
Date: 18 Apr 2001 22:52:53 GMT
In <9bkvur$1a7ef$[EMAIL PROTECTED]> Ajay Deshpande <[EMAIL PROTECTED]> writes:
>In comp.os.linux.help Alex Vinokur <[EMAIL PROTECTED]> wrote:
>> I tried to define following aliases in .bashrc
>> alias fnd1='find . -name !* -print'
>> alias fnd2='find . -name \!* -print'
?? I do not know what the !* is supposed to do.
See man bash
" There is no mechanism for using arguments in the replace<AD>
ment text. If arguments are needed, a shell function
should be used."
bash is NOT csh.
The two shells have different syntax. You cannot simply use one sytax
for both.
>> How to define in .bashrc alias fnd identical the same alias in .tcshrc?
You cannot. The syntaxes are different.
------------------------------
From: "Christopher R. Carlen" <[EMAIL PROTECTED]>
Subject: Is this a bad thing? (patch errors)
Date: Wed, 18 Apr 2001 15:07:26 -0700
Hi:
I tried to apply the win4lin 2.2.18 kernel patch to the Suse 7.1 kernel
source tree.
I get the following errors:
/download/win4lin # patch -p1 -b -d /usr/src/linux <
Kernel-Win4Lin2_2.2.18-1.patch
patching file arch/i386/boot/setup.S
Hunk #1 succeeded at 883 (offset 62 lines).
Hunk #2 FAILED at 906.
1 out of 2 hunks FAILED -- saving rejects to file
arch/i386/boot/setup.S.rej
patching file arch/i386/config.in
Hunk #1 FAILED at 206.
1 out of 1 hunk FAILED -- saving rejects to file arch/i386/config.in.rej
patching file arch/i386/kernel/apm.c
Hunk #1 succeeded at 133 (offset 2 lines).
Hunk #2 FAILED at 1542.
1 out of 2 hunks FAILED -- saving rejects to file
arch/i386/kernel/apm.c.rej
etc.
I suppose this means there is little point trying to compile and run the
kernel after these patch failures.
Any comments appreciated.
Thanks.
_______________________
Christopher R. Carlen
Sr. Laser/Optical Tech.
Sandia National Labs
------------------------------
From: "dubcaller" <[EMAIL PROTECTED]>
Crossposted-To:
ahn.tech.linux,alt.os.linux,alt.os.linux.best,aus.computers.linux,comp.os.linux.hardware,comp.os.linux.networking,comp.os.linux.portable,comp.os.linux.powerpc,comp.os.linux.questions,comp.os.linux.security,comp.os.linux.setup
Subject: HOTLINE port 5500 and IPCHAINS
Date: Wed, 18 Apr 2001 16:39:24 -0700
HI ALL,
I have a hotline server running behind my IPCHAINS, RED HAT 7.0, router. It
uses port 5500. I've opened the port (in and out) in my rc.firewall and
fowarded the port to my correct internal address. For some reason hotline
clients can't connect. Has anyone been successfull running a Hotline server
behind a simliar setup. Are there modules that I need to install?
------------------------------
From: Christian Rose <[EMAIL PROTECTED]>
Subject: Re: Which distro for 2.4.x ?
Date: Thu, 19 Apr 2001 02:00:18 +0200
Arctic Storm wrote:
> So,... RedHat has included GCC 2.96 with RedHat 7.1, instead of GCC 2.95.
Yes. They did that right. Using gcc 2.95.x would have been going to a
worse compiler.
> Now, the binaries are incompatible.
Why is binary compability important? It's not like you are guaranteed
anyway that moving around a binary on different Linux platforms will
work anyway. You have different glibc, rpm, paths, initscripts, desktop
environment and desktop environment library versions, etc.
Binary compability is a myth. If you're a developer, distribute source.
If you distribute binaries, do it for various platforms. If you're a
user, get the correct package for your platform.
> Can you recommend a disto that has kernel 2.4.x, and produces compatible
> binaries,...
Red Hat 7.1 of course... :-)
It's the first distro built entirely with kernel 2.4, and using 2.4
exclusively. So you know it works with and is properly tested with 2.4.
Christian
------------------------------
Crossposted-To: comp.os.linux.advocacy,rec.photo.digital
Subject: Re: Am I ****? HP Photosmart C500 and Win 2000
From: "Boyce Endertois" <[EMAIL PROTECTED]>
Reply-to: [EMAIL PROTECTED]
Date: Thu, 19 Apr 2001 00:01:07 GMT
1
>
> You're a mighty big fellow behind that keyboard.
And I was able to get a rise out of you without uttering a single curse!
;)
------------------------------
From: Christian Rose <[EMAIL PROTECTED]>
Subject: Re: Which distro for 2.4.x ?
Date: Thu, 19 Apr 2001 02:02:15 +0200
Wong Ching Kuen Frederick wrote:
> suse 7.1 or build ur own gcc in redhat 7.1
SuSE 7.1 doesn't even install kernel 2.4 by default. How could it be the
"best" distro for 2.4?
Christian
------------------------------
From: Christian Rose <[EMAIL PROTECTED]>
Subject: Re: Which distro for 2.4.x ?
Date: Thu, 19 Apr 2001 02:06:04 +0200
Andrew Purugganan wrote:
> Arctic Storm ([EMAIL PROTECTED]) wrote:
> [ So,... RedHat has included GCC 2.96 with RedHat 7.1, instead of GCC 2.95.
> [ Now, the binaries are incompatible.
> [ Can you recommend a disto that has kernel 2.4.x, and produces compatible
> [ binaries,...
>
> For the sake of us less skilled in the black arts :-)
> ...what do you mean incompatible? What would be moticeable?
Nothing. Unless you regulary download binary rpm packages for other
distros to your machine and expect it to work (which is a broken
behavior).
> Upgrading programs?
No.
> Compiling d/loaded tarballs?
No.
> This might help us in our future distro upgrade plans...
Hope this helps.
Christian
------------------------------
From: Christian Rose <[EMAIL PROTECTED]>
Subject: Re: Which distro for 2.4.x ?
Date: Thu, 19 Apr 2001 02:10:27 +0200
[EMAIL PROTECTED] wrote:
> > For the sake of us less skilled in the black arts :-)
> > ....what do you mean incompatible? What would be moticeable? Upgrading
> > programs? Compiling d/loaded tarballs? This might help us in our future
> > distro upgrade plans...
>
> "Incompatible" as in "GCC 2.96 produces binaries that don't
> interoperate with those produced by 2.95 or by future releases."
gcc 2.95 won't produce binaries that will operate well with future
releases either. What's the point?
> As in, you may find that if you try to run programs compiled using
> other versions of GCC, on a system where binaries and libraries were
> compiled using 2.96, that you get a lot of errors resembling:
>
> "Not a binary executable"
> or
> "Can't execute"
>
> Similarly, programs compiled using GCC 2.96 may not work elsewhere
> with much the same results.
>
> The problems are _highly_ likely to arise with C++ code, and rather
> less likely to arise with just plain C.
>
> It's pretty much a given, with C++, that attempts to attain any useful
> degree of binary interoperability are pretty forlorn.
Agreed. So this whole "binary compability with gcc" argument is a moot
point anyway.
Christian
------------------------------
From: Garry Knight <[EMAIL PROTECTED]>
Subject: Re: Ctrl+Alt+F1?? and more
Date: Thu, 19 Apr 2001 00:44:46 +0100
Reply-To: [EMAIL PROTECTED]
On Wed, 18 Apr 2001 21:38:09 +0100 in article
<[EMAIL PROTECTED]>, DMayo
<[EMAIL PROTECTED]> wrote:
> Could someone tell me what the three keys in the subject are for? If
> they are for logging out of the XWindow session..... how do I get back
> to the KDE Desktop?
They're not for logging out. You have one X session and 6 text-based
virtual consoles running unless you've changed the default settings.
Pressing Ctrl+Alt+F1 to F6 switches between the text consoles, and a
different user could login on each of them. Pressing Ctrl+Alt+F7 gets you
back into X. Also, once you're in a text console, pressing Alt+F1 to F6
also switches from one console to the next. And presssing Ctrl+Alt+F12 (on
a RedHat-based system, at least) shows you the boot-up messages. Finally,
you probably already know that pressing Ctr+F1 to F4 switches you between
the 4 KDE desktops.
> Two more questions:
> 1. Could anyone tell me how to activate the backspace and delete keys on
> my keyboard?? I am getting v tired of typing ctrl d and ctrl b all the
> time...
In what? A console or an application?
> 2. I just acquired StarOffice from Sun... well, technically on its
> way... which paritions should I install it in?
Some people will say put it in /opt/office52, others will say
/usr/local/office52, and some people symlink /opt to /usr/local and say put
it wherever you want. If one of those two directories is on a faster
partition (i.e. on a faster hard disk) then put it there.
Note that you'll need to install it with the /net option as root, then
install it locally for each user that's going to use it. If you got the CD,
you'll see a PDF file on it with the details. If you didn't get the CD, you
should find instructions at Sun's website.
--
Garry Knight
[EMAIL PROTECTED]
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Handspring Visor With Korganizer
Date: Thu, 19 Apr 2001 00:30:06 -0000
Hello,
I finally got my Handspring Visor (USB) synching with J-Pilot 0.99. I
have KOrganizer on my computer and I would like to use that as my PIM
instead of J-Pilot because the interface is so much nicer. Any
sugguestions on how I could synch my Visor and Korganizer?
Thanks,
James
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: David <[EMAIL PROTECTED]>
Subject: Re: Which distro for 2.4.x ?
Date: Thu, 19 Apr 2001 00:33:03 GMT
Christian Rose wrote:
>
>
> Red Hat 7.1 of course... :-)
> It's the first distro built entirely with kernel 2.4, and using 2.4
> exclusively. So you know it works with and is properly tested with 2.4.
>From previous experience with RedHat's 5.0, 5.1, 5.2, 6.0, 6.1, 6.2
releases about the time 8.1 or 8.2 is about to be released 7.2 will have
many/most of the bugs worked out and well tested.
Ever wonder what happened to x.3, x.4, x.5, x.6, x.7, x.8, and x.9
versions.
Just my opinion.
--
Confucius say: He who play in root, eventually kill tree.
Registered with the Linux Counter. http://counter.li.org
ID # 123538
Completed more W/U's than 99.166% of seti users. +/- 0.01%
------------------------------
From: * Tong * <[EMAIL PROTECTED]>
Subject: PC NFS server?
Date: 18 Apr 2001 21:47:11 -0300
Hi,
I wish every box is installed Linux. If that can't be satisfied for
any reason, I wish every windoze box has NFS sever installed so that
I can use my Linux to access it.
What is your recommended NFS sever for PC/windoze? Thanks
--
Tong (remove underscore(s) to reply)
*niX Power Tools Project: http://xpt.sourceforge.net/
http://members.xoom.com/suntong001/
- All free contribution & collection
------------------------------
From: Christian Rose <[EMAIL PROTECTED]>
Subject: Re: RedHat 7.1 too early ?,...
Date: Thu, 19 Apr 2001 02:37:14 +0200
"Peter T. Breuer" wrote:
> > mainstream release (What was that, either 5.0 or 6.0). Painful in the short
> > term, but I think most people agree that it benefited the community as a
> > whole in the long run. RedHat suffered a similar rash of villianization
>
> Well, it's hardly the same thing. In that case the change was planned.
> Tho' they did wrong by using the development release 2.0.7
> instead of waiting for the release 2.1.1 (which was incompatible),
> nevertheless, everyone was going that way. It was a matter of judgement
> as to when. In this case, RH took something that wasn't ever intended
> to be released, and based a distro around it. The compiler snapshot was
> promptly disowned by the gcc team, who pointed out that it was
> incompatible with anything currently existing, and it was promised that
> gcc 3.0 would certainly not be compatible with it.
I think it's the exact same thing. A big change is coming and is needed
(in this case gcc), the new technology is late, nobody wants to take the
first step using the new technology and polishing it in a distro, then
Red Hat takes the first step. They take a development version, debunk it
(and send all changes back) and produce something reliable, and builds a
distro around it. The new technology gets heavily tested, the patches
that are sent back helps accelerate development of the "real" release,
and other distros proceed to use it too.
Of course, thanking Red Hat for accelerating the development doesn't
cross many people's minds. Instead they use their flamethrowers all they
can to accuse Red Hat for breaking their self-invented "standards".
Afterwards, when the new technology is used by everyone, the
flamethrowers are still in use.
On the point that binary compability would make this situation
different: It's not. There won't any binary compability between gcc 2.95
and gcc 3.0 either. So the gcc team's statement regarding this is kind
of incompabilities is kind of strange and pointless, I think.
> I see the parallels, but the degree is different. At least I don't
> recall Linus telling them off then!
I believe that even heroes still can be wrong on some topics. I think
Linus' statement regarding gcc 2.96 wasn't the most clever one, and this
also showed in the later posts on the mailing list.
Christian
------------------------------
From: Christian Rose <[EMAIL PROTECTED]>
Subject: Re: RedHat 7.1 too early ?,...
Date: Thu, 19 Apr 2001 02:58:46 +0200
Monte Milanuk wrote:
> Kinda like they did before, pushing glibc out the door (IIRC) into a
> mainstream release (What was that, either 5.0 or 6.0). Painful in the short
> term, but I think most people agree that it benefited the community as a
> whole in the long run. RedHat suffered a similar rash of villianization
> then, but rarely ever gets retro'd any accolades.
Agreed.
> Lest it seem that I think
> RedHat is a saintly organization, I do question the whole RedHat Network
> 'pay-for-updates' thing. It'd be nice if there was some sort of tiered set
> up, where your average Joe could connect and get basic update service for
> free (i.e. Debian) but commercial customers could get enhanced service,
> secure connections, whatever for a fee. I guess they kinda do now, w/ their
> ftp servers and mirrors, but it's not very coherent or organized in the
> sense that most people are looking for, I suppose.
The thing you describe is exactly how it is now. Subscribing to the
mailing list where updates are announced, and getting updates from
ftp.redhat.com and mirrors, is still free of course, but you can use RHN
freely too.
I haven't paid anything for RHN, but I registered for a free account. I
can use up2date on all of my systems to update them (you have to make
up2date know about your free account though) and I can use the web-based
interface to monitor all the machines I have, what packages are
installed, and what erratas are applicable for each of them. The only
thing that costs is the *automatic* update installation and notification
service if you want it for more than one system. But since you can use
it for free on one system, I use it on one and copy the updates from
there to the rest of the machines. Works like a charm.
Christian
------------------------------
From: Christian Rose <[EMAIL PROTECTED]>
Subject: Re: RedHat 7.1 too early ?,...
Date: Thu, 19 Apr 2001 02:59:21 +0200
[EMAIL PROTECTED] wrote:
> > Painful in the short term, but I think most people agree that it
> > benefited the community as a whole in the long run. RedHat suffered
> > a similar rash of villianization then, but rarely ever gets retro'd
> > any accolades.
>
> Creating their own version of GCC (2.96) was fairly worthy of
> "villainization." It's a version producing binaries incompatible with
> those generated by older versions as well as future versions.
*Every* major gcc release produces incompatible binaries. gcc 2.95 will
also be incompatible with gcc 3.0.
> With the ELF change, it was a given that it was a "growing pain."
> Creating a version of GCC that produces incompatible binaries is quite
> a bit more serious.
It's only serious for the people who expect that they can and should be
able to run a single binary on every Linux platform. That's broken.
Christian
------------------------------
From: Christian Rose <[EMAIL PROTECTED]>
Subject: Re: RedHat 7.1 too early ?,...
Date: Thu, 19 Apr 2001 02:59:37 +0200
"Peter T. Breuer" wrote:
> > mainstream release (What was that, either 5.0 or 6.0). Painful in the short
> > term, but I think most people agree that it benefited the community as a
> > whole in the long run. RedHat suffered a similar rash of villianization
>
> Well, it's hardly the same thing. In that case the change was planned.
> Tho' they did wrong by using the development release 2.0.7
> instead of waiting for the release 2.1.1 (which was incompatible),
> nevertheless, everyone was going that way. It was a matter of judgement
> as to when. In this case, RH took something that wasn't ever intended
> to be released, and based a distro around it. The compiler snapshot was
> promptly disowned by the gcc team, who pointed out that it was
> incompatible with anything currently existing, and it was promised that
> gcc 3.0 would certainly not be compatible with it.
I think it's the exact same thing. A big change is coming and is needed
(in this case gcc), the new technology is late, nobody wants to take the
first step using the new technology and polishing it in a distro, then
Red Hat takes the first step. They take a development version, debunk it
(and send all changes back) and produce something reliable, and builds a
distro around it. The new technology gets heavily tested, the patches
that are sent back helps accelerate development of the "real" release,
and other distros proceed to use it too.
Of course, thanking Red Hat for accelerating the development doesn't
cross many people's minds. Instead they use their flamethrowers all they
can to accuse Red Hat for breaking their self-invented "standards".
Afterwards, when the new technology is used by everyone, the
flamethrowers are still in use.
On the point that binary compability would make this situation
different: It's not. There won't any binary compability between gcc 2.95
and gcc 3.0 either. So the gcc team's statement regarding this is kind
of incompabilities is kind of strange and pointless, I think.
> I see the parallels, but the degree is different. At least I don't
> recall Linus telling them off then!
I believe that even heroes still can be wrong on some topics. I think
Linus' statement regarding gcc 2.96 wasn't the most clever one, and this
also showed in the later posts on the mailing list.
Christian
------------------------------
** 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 by posting to comp.os.linux.misc.
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
******************************
