Re: [ECOS] ROM File system ?

Re: [ECOS] ROM File system ?

[Gary Thomas]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]

Note: responses directed to Red Hat employees which are not also copied
to the eCos discussion list will be ignored.  This one has been answered
as a favour, once only.

On 02-May-2001 Sebastien ANDRE wrote:
> It's a custom board with an ARM7TDMI
> with a ROM flash (2Mo) and RAM too.
> 

ROM based booting is supported in this environment by default.

> 
> Gary Thomas a écrit :
> 
>> On 02-May-2001 Sebastien ANDRE wrote:
>> > I see in documentation that we can make a simple File System in ROM
>> >  ===> (ROM based file system support has been added, contributed by
>> > Richard Panton)
>> >
>> > But i want know if it's possible to boot directly in ROM ?
>>
>> It depends on the platform, but in general the answer is "yes" (although
>> this does not use the ROM file system).
>>
>> Exactly what were you looking for?  on what platform?

[ECOS] Reply-To the list (was: Re: [ECOS] ROM File system ?)

[Fabrice Gautier]

On Wed, 02 May 2001 07:05:08 -0600 (MDT)
Gary Thomas <gthomas@cambridge.redhat.com> wrote:

> Note: responses directed to Red Hat employees which are not also copied
> to the eCos discussion list will be ignored.  This one has been answered
> as a favour, once only.

Could the list manager add a Reply-To: header set to the list?
This would probably avoid some part of the problem...

Thanks



-- 
Fabrice Gautier <gautier@email.enstfr>

Re: [ECOS] Reply-To the list (was: Re: [ECOS] ROM File system ?)

[elf]

Hear hear.

On Wed, May 02, 2001 at 03:58:04PM +0200, Fabrice Gautier wrote:
> 
> On Wed, 02 May 2001 07:05:08 -0600 (MDT)
> Gary Thomas <gthomas@cambridge.redhat.com> wrote:
> 
> > Note: responses directed to Red Hat employees which are not also copied
> > to the eCos discussion list will be ignored.  This one has been answered
> > as a favour, once only.
> 
> Could the list manager add a Reply-To: header set to the list?
> This would probably avoid some part of the problem...
> 
> Thanks
> 
> 
> 
> -- 
> Fabrice Gautier <gautier@email.enstfr>

Re: [ECOS] Reply-To the list (was: Re: [ECOS] ROM File system ?)

[Jonathan Larmour]

Fabrice Gautier wrote:
> 
> On Wed, 02 May 2001 07:05:08 -0600 (MDT)
> Gary Thomas <gthomas@cambridge.redhat.com> wrote:
> 
> > Note: responses directed to Red Hat employees which are not also copied
> > to the eCos discussion list will be ignored.  This one has been answered
> > as a favour, once only.
> 
> Could the list manager add a Reply-To: header set to the list?
> This would probably avoid some part of the problem...

This can be a matter of religious debate. See:

http://www.unicom.com/pw/reply-to-harmful.html

And my preference is to agree. A small number of the internal lists within
Red Hat set Reply-To and it causes more problems than I believe it
prevents.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: [ECOS] Reply-To the list (was: Re: [ECOS] ROM File system ?)

[Fabrice Gautier]

On Wed, 02 May 2001 19:51:51 +0100
Jonathan Larmour <jlarmour@redhat.com> wrote:

> Fabrice Gautier wrote:
> > 
> > Could the list manager add a Reply-To: header set to the list?
> > This would probably avoid some part of the problem...
> 
> This can be a matter of religious debate. See:
> 
> http://www.unicom.com/pw/reply-to-harmful.html
> 

I tend to agree on some points too but I tend to think that this is
highly list-dependant and MUA dependant.

I could expose plenty of arguments in favor of Reply-To or against the
group-reply.

But, I think that the better solution is probably you (not the list)
setting the Reply-To header when you're replying on the list.

After all if why you are requesting people to reply to the list and not
to you, then set the header accordingly (just like i've done on this
message)

(If there was a Cc-reply-to: this would probably be even better...)

Thanks

-- 
Fabrice Gautier <gautier@email.enstfr>