Linux-Misc Digest #115, Volume #26               Sun, 22 Oct 00 22:13:03 EDT

Contents:
  Re: Which Gcc version to compile Linux Kernel ? (Timothy Murphy)
  Re: Kernel woes (Timothy Murphy)
  Re: RH7 Kernel Compiling Problem (Timothy Murphy)
  Re: End-User Alternative to Windows (Charlie Ebert)
  bash question (Robert Schweikert)
  Re: Which Gcc version to compile Linux Kernel ? (Jim Broughton)
  Re: Diabolical plot uncovered... (Jerry L Kreps)
  Re: End-User Alternative to Windows (Jerry L Kreps)
  Re: Help me choose the best fileserver OS for a Compaq proliant server. (Jerry L 
Kreps)
  Re: Stock Red Hat 7 kernel compile fails. ([EMAIL PROTECTED])
  Re: mount/umount LS-120 floppydrive? (Dances With Crows)
  Re: Diabolical plot uncovered... (Dances With Crows)
  Re: GPL questions? (John Hasler)
  Re: bash question (ljb)
  Re: Diabolical plot uncovered... (jeff)
  Re: RH7 Kernel Compiling Problem (Hal Burgiss)

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

From: [EMAIL PROTECTED] (Timothy Murphy)
Crossposted-To: comp.os.linux.development.system,alt.os.linux
Subject: Re: Which Gcc version to compile Linux Kernel ?
Date: 23 Oct 2000 01:12:58 +0100

[EMAIL PROTECTED] (Paul Kimoto) writes:

>: This code is intended to build with gcc 2.7.2 and egcs 1.1.2. Patches for
>: building with gcc 2.95 are merged but less tested than other compilers.

I went over to kgcc for compiling kernel-2.4.0-test9 under RedHat-7.0 
(following advice in this newsgroup).

This got rid of the compilation errors,
but threw up a lot of assembly warnings about not being able
to modify .modinfo ,
which seemed to result in no modules being installed
by "make modules_install".

Any advice or suggestions gratefully received.

Incidentally the kernel that came with RedHat-7.0
did not run on my all-SCSI machine.
(Fortunately I had 2.4.0-test2 installed as well.)


-- 
Timothy Murphy  
e-mail: [EMAIL PROTECTED]
tel: 086-233 6090
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

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

From: [EMAIL PROTECTED] (Timothy Murphy)
Subject: Re: Kernel woes
Date: 23 Oct 2000 01:21:56 +0100

Robert Jones <[EMAIL PROTECTED]> writes:

>I was also sent advice to forget Kppp and follow
>the instructions at http://axion.physics.ubc.ca/ppp-linux.html

I agree completely with this.
kppp is meant to make ppp simpler,
but in fact it is far more difficult that pppd to set up.

-- 
Timothy Murphy  
e-mail: [EMAIL PROTECTED]
tel: 086-233 6090
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

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

From: [EMAIL PROTECTED] (Timothy Murphy)
Subject: Re: RH7 Kernel Compiling Problem
Date: 23 Oct 2000 01:17:12 +0100

[EMAIL PROTECTED] () writes:

>>However, with RH7 RedHat wants you to use the provided kgcc
>>~ egcs/gcc 2.71 (I think) instead of gcc, for kernel compiles.

>Yes, that is why kgcc is there.

If kgcc = egcs why don't they call it that?

-- 
Timothy Murphy  
e-mail: [EMAIL PROTECTED]
tel: 086-233 6090
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

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

From: Charlie Ebert <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.advocacy
Subject: Re: End-User Alternative to Windows
Date: Mon, 23 Oct 2000 00:34:47 GMT

"Colin R. Day" wrote:

> Andy Newman wrote:
>
> > Colin R. Day wrote:
> > >Of course, trying to run UNIX on such computers as were used for
> > >XENIX would be like trying to drive a Lamborghini in rush-hour
> > >traffic.
> >
> > I used SCO Xenix on a PDP-11.  Seemed fine.  As fast a V7 on
> > similar h/w.
>
> I had read that Microsoft's version of Xenix ran on a computer with a
> 20-meg hard drive. The article said that the OS could barely get out
> of its own way.
>
> Colin Day

As I recal, and it's been some time,  YES THAT IS XENIX.

Ha.

Charlie



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

From: Robert Schweikert <[EMAIL PROTECTED]>
Subject: bash question
Date: Sun, 22 Oct 2000 20:43:55 -0400

How do I run a csh script from within my /etc/profile and get the
environment variables that will be set up in the csh script into my bash
environment?

Converting the csh script is not an option, it gets updated, out of my
control and I am not interested in keeping a duplicate in Bash format
and then keep running after any changes.

I made the csh script executable and added #! /bin/csh as the first line
in the script. Then I provided the fully qualified path to the script in
/etc/profile but I am not sure if the script is running or if the
environment variables it sets are not available in the bash environment.

Any help is appreciated.

Thanks,
Robert

--
Robert Schweikert                      MAY THE SOURCE BE WITH YOU
[EMAIL PROTECTED]                         LINUX




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

From: Jim Broughton <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.development.system,alt.os.linux
Subject: Re: Which Gcc version to compile Linux Kernel ?
Date: Mon, 23 Oct 2000 00:44:00 GMT

Paul Kimoto wrote:
> 
> In article <8ss8js$m1p$[EMAIL PROTECTED]>, T.R. Donahue wrote:
> > There is conflicting information available to which gcc version
> > should preferably be used to compile the linux kernel v2.2.16. There seem to
> > be people who claim that the kernel should preferably be compiled with Gcc
> > 2.72.x instead of Gcc 2.95.x, due to some issues with 2.95.x, and the fact
> > that Linus himself still exclusively uses (and therefore tests) the kernel
> > with 2.72.x.
> 
> (At some point I think that it turned out that Linus and Alan Cox both used
> egcs-1.1.*.)
> 
> Alan Cox now maintains 2.2.*, and in some recent release notes (see
> http://www.linux.org.uk/) he writes:
> 
> : This code is intended to build with gcc 2.7.2 and egcs 1.1.2. Patches for
> : building with gcc 2.95 are merged but less tested than other compilers.
> : Caution is recommended when using gcc 2.95 and feedback is sought.
> 
> --
> Paul Kimoto
> This message was originally posted on Usenet in plain text.  Any images,
> hyperlinks, or the like shown here have been added without my consent,
> and may be a violation of international copyright law.

  I have used the 2.91.66 gcc (also used in egcs 1.1.2) For a LONG time
now. Maybe around 50 kernel compiles and not a failed attempt in the
lot because of an internal compiler error.

-- 
Jim Broughton
(The Amiga OS! Now there was an OS)
If Sense were common everyone would have it!
Following Air and Water the third most abundant
thing on the planet is Human Stupidity.

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

From: Jerry L Kreps <[EMAIL PROTECTED]>
Subject: Re: Diabolical plot uncovered...
Date: Sun, 22 Oct 2000 19:51:42 -0500

On Sun, 22 Oct 2000, jeff wrote:
>Sheesh...  I spent much of the last month trying to get my otherwise
>fine-and-dandy Debian Potato to recognize my serial ports.  Along the way
>I... lost sleep, fried a motherboard, doubted my sanity, seriously
>considered writing Linus out of my will, and, in general, fumed and pouted. 
>But WAIT!  I JUST FOUND THE PROBLEM...
>
>I was trying to use ttys0, and I _should_ have used ttyS0!!!
>
>How has everyone else in the world avoided this diabolical plot?
>
>-jeff

Of course!  Didn't you know that the ttyS0 ---> ttys0 conversion was the major
scientific achievment to come out of Area 51 ?

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

From: Jerry L Kreps <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.advocacy
Subject: Re: End-User Alternative to Windows
Date: Sun, 22 Oct 2000 19:53:58 -0500

On Sun, 22 Oct 2000, Colin R. Day wrote:
>Andy Newman wrote:
>
>> Colin R. Day wrote:
>> >Of course, trying to run UNIX on such computers as were used for
>> >XENIX would be like trying to drive a Lamborghini in rush-hour
>> >traffic.
>>
>> I used SCO Xenix on a PDP-11.  Seemed fine.  As fast a V7 on
>> similar h/w.
>
>I had read that Microsoft's version of Xenix ran on a computer with a
>20-meg hard drive. The article said that the OS could barely get out
>of its own way.
>
>Colin Day

mmm... I donno.   I used a XENIX dev tool called DataAce (it was Forth based)
to write an auto parts store  system back in the VERY early 80s.  Didn't seem
to slow or shabby then, compared to other systems existant at the time.
But, Forth has a tendency to create the fastest code available, short of
assembly, on any PC, being a threaded and extensible langage.

 JLK

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

From: Jerry L Kreps <[EMAIL PROTECTED]>
Crossposted-To: 
comp.unix.bsd.freebsd.misc,comp.unix.bsd.netbsd.misc,comp.unix.bsd.openbsd.misc
Subject: Re: Help me choose the best fileserver OS for a Compaq proliant server.
Date: Sun, 22 Oct 2000 19:57:25 -0500

Why not SuSE 7.0 and the ReiserFS journaling system?  ReiserFS will allow files
sizes > 2GB when the 2.4 kernel comes out.
JLK

On Sun, 22 Oct 2000, Dustin Puryear wrote:
>On Sat, 21 Oct 2000 03:12:20 GMT, dcs <[EMAIL PROTECTED]> wrote:
>>I would appreciate any input anyone can offer. I don't have the bandwidth to
>>benchmark all these OSs, so I hope the net.community can help me narrow down
>>my choices. Here are my choices:
>>
>>FreeBSD
>>NetBSD
>>OpenBSD
>>Linux (RedHat or TurboLinux Server 6.x)
>>Windows 2000
>
>As others have mentioned, your list of *BSD choices is pretty much out. 
>That only leaves you with Linux or Windows 2000. Is it at all possible
>for you to run at least limited trials using both? That is always a
>good way to go.
>
>Also, I have heard that there is a distributed file system ala Beowulf
>that works well in high-load environments on Linux. I'm not sure if what 
>I heard is about a project still in alpha or in production. I can look 
>around my stack of papers if you want.
>
>FYI, Samba performs very well, but you will *definately* need to tweak
>it for a high-load/performance environment. One of the biggest issues
>will be how your applications access the data (large chunks vs small
>chunks).
>
>-- 
>Dustin Puryear <$email = "dpuryear"."@usa.net";>
>Integrate Linux Solutions into Your Windows Network
>- http://www.prima-tech.com/integrate-linux

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

From: [EMAIL PROTECTED]
Subject: Re: Stock Red Hat 7 kernel compile fails.
Date: Mon, 23 Oct 2000 00:50:44 GMT

I'm having the exact same problem.  I've switched
to kgcc, but there seems to be another problem
with the include files.  Anyone fix this yet?

-EK

In article
<[EMAIL PROTECTED]>,
  Jeff Workman <[EMAIL PROTECTED]> wrote:
> All,
>
> OK, I have read the gotchas and caveats about RH
7 and it's "kgcc" but it
> still doesn't help the problem I'm having.
>
> This is the errors I am getting on 2 different
boxes.  One of these is a
> RH 6.2 server install upgraded to RH 7 and the
other is a clean RH 7
> workstation class install.  No modification to
the kernel configuration
> has been made or anything, just a simple "make
menuconfig" then immediate
> save, then a "make dep; make clean; make
bzImage" which gives the
> following compile errors on both machines.  Can
somebody tell me what the
> fix is for this?
>
> TIA,
> Jeff
>
> kgcc -D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer
-fno-strict-aliasing -pipe -fno-strength-reduce
-m386 -DCPU=386 -DUTS_MACHINE='"i386"' -c -o
init/version.o init/version.c
> make -C  kernel
> make[1]: Entering directory
`/usr/src/linux-2.2.16/kernel'
> make all_targets
> make[2]: Entering directory
`/usr/src/linux-2.2.16/kernel'
> kgcc -D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer
-fno-strict-aliasing -pipe -fno-strength-reduce
-m386 -DCPU=386   -DEXPORT_SYMTAB -c ksyms.c
> In file included from
/usr/src/linux/include/linux/modversions.h:50,
>                  from
/usr/src/linux/include/linux/module.h:19,
>                  from ksyms.c:14:
>
/usr/src/linux/include/linux/modules/i386_ksyms.ver:6:
warning: `cpu_data' redefined
> /usr/src/linux/include/asm/processor.h:96:
warning: this is the location of the previous
definition
>
/usr/src/linux/include/linux/modules/i386_ksyms.ver:28:
warning: `smp_num_cpus' redefined
> /usr/src/linux/include/linux/smp.h:77: warning:
this is the location of the previous definition
>
/usr/src/linux/include/linux/modules/i386_ksyms.ver:118:
warning: `smp_call_function' redefined
> /usr/src/linux/include/linux/smp.h:83: warning:
this is the location of the previous definition
> In file included from
/usr/src/linux/include/linux/interrupt.h:51,
>                  from ksyms.c:21:
> /usr/src/linux/include/asm/hardirq.h:23:
warning: `synchronize_irq' redefined
>
/usr/src/linux/include/linux/modules/i386_ksyms.ver:138:
warning: this is the location of the previous
definition
> In file included from
/usr/src/linux/include/linux/interrupt.h:52,
>                  from ksyms.c:21:
> /usr/src/linux/include/asm/softirq.h:75:
warning: `synchronize_bh' redefined
>
/usr/src/linux/include/linux/modules/i386_ksyms.ver:142:
warning: this is the location of the previous
definition
> /usr/src/linux/include/linux/kernel_stat.h: In
function `kstat_irqs':
> In file included from ksyms.c:17:
> /usr/src/linux/include/linux/kernel_stat.h:47:
`smp_num_cpus' undeclared (first use in this
function)
> /usr/src/linux/include/linux/kernel_stat.h:47:
(Each undeclared identifier is reported only once
> /usr/src/linux/include/linux/kernel_stat.h:47:
for each function it appears in.)
> make[2]: *** [ksyms.o] Error 1
> make[2]: Leaving directory
`/usr/src/linux-2.2.16/kernel'
> make[1]: *** [first_rule] Error 2
> make[1]: Leaving directory
`/usr/src/linux-2.2.16/kernel'
> make: *** [_dir_kernel] Error 2
>
> --
> "For competitive reasons we can't tell you the
location of our fiber."
>       -- An anonymous representative of a very large
telco
> "For competitive reasons we can't tell you the
location of our backhoe."
>       -- An anonymous representative of a contractor.
>
>



Sent via Deja.com http://www.deja.com/
Before you buy.

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

From: [EMAIL PROTECTED] (Dances With Crows)
Crossposted-To: comp.os.linux.hardware
Subject: Re: mount/umount LS-120 floppydrive?
Date: 23 Oct 2000 01:04:12 GMT
Reply-To: [EMAIL PROTECTED]

On Sun, 22 Oct 2000 22:47:06 GMT, Bo Berglund wrote:
>Then I can read the contents of the disk.  But to get the disk out I 
>have to
>umount /mnt/LS-120
>
>As soon as the disk is out my Linux box starts to click terribly on
>the hard disk until I reinsert and mount the disk again.
>In the /var/log/messages file I find this (entries are on one line
>following the date):
>Oct 22 22:41:00 bbfirewall kernel: hdc: The drive reports both
>126222336 and 0 bytes as its capacity 
>Oct 22 22:41:00 bbfirewall kernel: ide-floppy: hdc: I/O error, pc =
>0, key =  2, asc = 3a, ascq =  0 
>These three lines are repeated several times per second for the entire
>time that the disk is outside the drive!

Disable whatever's trying to auto-mount the drive?  There's an applet
that ships with stock RH installs which tries to auto-mount CDs and may
be trying to get at your LS-120.  There's also a kernel option for
automounter support; you might have to disable that.

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /  Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com     /   Workin' in a code mine, whoops!
=============================/    I hit a seg fault....

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

From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Diabolical plot uncovered...
Date: 23 Oct 2000 01:04:13 GMT
Reply-To: [EMAIL PROTECTED]

On Sun, 22 Oct 2000 16:45:14 +0600, James Blanford wrote:
>In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] 
>wrote:
>> I was trying to use ttys0, and I _should_ have used ttyS0!!!
>> How has everyone else in the world avoided this diabolical plot?
>
>I got a good chuckle out of this one.  I can never remember.  Is it Suse
>SuSe or SuSE?  Being case sensitive adds versatility, but most of the
>time it ends up causing needless confusion.  I just went through a similar
>problem with whitespace and the use of brackets in bash, or is it basH?
>
>The principle that applies here is that of minimum surprise.  Things are
>easier to learn and work with if they present themselves in a familiar
>manner.  Those of us educated to read when we were young learned that
>capital letters came at the beginning of the word.  For the rest of our
>lives that's where we will expect them to be.

And then there's the iMac and eBusiness.  Blame Apple; they invented
PostScript and then people started using StudlyCaps when they weren't
needed....

>I've noticed that a lot of experienced Linux users resist the idea that
>Linux could be made easier to learn and use.

Eh?  Well, there are a few people like that, but I've noticed time and
again that when you try to make things simpler, often you end up making
simple things simple and complex things impossible.  Case in point:
Linuxconf.  Great idea, but it keeps breaking things in interesting and
slightly unpredictable ways if the NG reports I've read are to be
believed.

And what about Eazel?

[snipp]
>Give people a simple example.
>Here's a quote from an example file that SuSE includes with it's
>distribution:
> This is a worthless, nonrunnable example of a named.conf file
> that has * every conceivable syntax element in use.  We use it
> to test the parser.  * It could also be used as a conceptual
> template for users of new features
>The guy who wrote this did it for a good reason.  Whoever included it in
>the distribution obviously resents the idea that ordinary people should
>ever use Linux.

...or wanted to include a template for advanced users.  Oddly enough,
I'm running SuSE 6.4, and /etc/named.conf is 119 lines long, reasonably
normal, and doesn't contain the lines you mention.  Anyway, there are
times when having a config file with every possible option included
along with comments specifying use/syntax is Very Useful(tm).
httpd.conf in a default Apache install is a reasonable example of what
I'm talking about.

>What brought me to Linux was that it is free and open (mostly).  thanKs
>fOr LIsteniNG tO mY tirAde.  simPliCTY IS worTh tHe efFort.

Yep.  BTW, /dev/ttys0 *does* exist, or did exist a couple of years back.
Before the /dev/pts/ system for assigning pseudo-terminals was in wide
use, there were a set of pseudo-terminals called tty[p-s][0-f].  Back
then, serial ports were often called /dev/cu[a-d][0-9].  Things were
changed for the sake of simplicity :-)

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /  Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com     /   Workin' in a code mine, whoops!
=============================/    I hit a seg fault....

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

From: John Hasler <[EMAIL PROTECTED]>
Subject: Re: GPL questions?
Date: Mon, 23 Oct 2000 00:17:57 GMT

Neil Cherry writes:
> if I assign my Copyrights over to the FSF how do they know that they have
> them? Don't you have to tell them they have Copyrights on this code?

I think you are a bit confused.  Notice the 'if' in your step 3.  Assigning
copyright to the FSF is not a necessary (or usual) part of releasing a
program under the terms of the GPL.

When you release a program under the terms of the GPL, _you_ are licensing
it to the recipients under _your_ license, which happens to be identical to
the GPL.  The FSF is not involved except as author of the document you
modeled your license on.

If you really do want to assign your copyright to the FSF, I think you will
find complete instructions at www.gnu.org.  I don't think that's what you
want to do, though.
-- 
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisconsin

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

From: [EMAIL PROTECTED] (ljb)
Subject: Re: bash question
Date: 23 Oct 2000 01:24:39 GMT

[EMAIL PROTECTED] wrote:
>How do I run a csh script from within my /etc/profile and get the
>environment variables that will be set up in the csh script into my bash
>environment?
>
>Converting the csh script is not an option, it gets updated, out of my
>control and I am not interested in keeping a duplicate in Bash format
>and then keep running after any changes.
>
>I made the csh script executable and added #! /bin/csh as the first line
>in the script. Then I provided the fully qualified path to the script in
>/etc/profile but I am not sure if the script is running or if the
>environment variables it sets are not available in the bash environment.
>
>Any help is appreciated.

First, what you tried won't work... bash/profile will run the script with
csh as you asked, but it runs in a subprocess, so environment variables
it changes will have no effect in the parent bash process.

You might be able to do this by having an intermediate csh script,
let's call it "cenv", which "sources" the csh script you want to
run, then outputs its environment as a series of lines like:
    echo export VAR="$VAR"
Then, from profile, you do something like: eval $(cenv)
which makes bash evaluate the output of the middle script, and
brings those variables into its environment. (Might work, probably
someone else will come up with something much simpler.)

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

From: [EMAIL PROTECTED] (jeff)
Subject: Re: Diabolical plot uncovered...
Date: 23 Oct 2000 01:33:56 GMT
Reply-To: [EMAIL PROTECTED]

> ...
> Yep.  BTW, /dev/ttys0 *does* exist, or did exist a couple of years back.
> Before the /dev/pts/ system for assigning pseudo-terminals was in wide
> use, there were a set of pseudo-terminals called tty[p-s][0-f].  Back
> then, serial ports were often called /dev/cu[a-d][0-9].  Things were
> changed for the sake of simplicity :-)


/dev/ttys_ Still exists - that's what my problem was.  If /dev/ttys0 had not
existed, I believe (hope :) that I would have solved my problem in seconds,
instead of weeks.  The fact is that, when you do "setserial" with
"/dev/ttys0", you _always_ get "Input/output error," which I _assumed_ meant
that my first serial port was returning an Input/output error!

BTW, In my SuSE days, I never had a problem, since I always used /dev/cua_.
When /dev/ttys_ showed no signs of working with Debian, I (re)installed SuSE
on a spare harddisk to ensure that Linux could still handle my serial
hardware. It did, when addressed with cua_.  It did not, with ttys_.  This
was my first clue...

-jeff

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

From: [EMAIL PROTECTED] (Hal Burgiss)
Subject: Re: RH7 Kernel Compiling Problem
Reply-To: Hal Burgiss <[EMAIL PROTECTED]>
Date: Mon, 23 Oct 2000 02:07:15 GMT

On 23 Oct 2000 01:17:12 +0100, Timothy Murphy <[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] () writes:
>
>>>However, with RH7 RedHat wants you to use the provided kgcc
>>>~ egcs/gcc 2.71 (I think) instead of gcc, for kernel compiles.
>
>>Yes, that is why kgcc is there.
>
>If kgcc = egcs why don't they call it that?

I guess because the executable is kgcc:

[hal@feenix hal]$ which kgcc
/usr/bin/kgcc

So to re-inforce the idea that it is for kernel compiling. Other than
that, maybe 'just because' <g>.

-- 
Hal B
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]
--

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


** 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