From: heze54 (heze54_at_hezesoft.org)
Date: Sat Oct 07 2006 - 12:16:50 CEST
Date: Sat, 07 Oct 2006 12:16:50 +0200 From: heze54 <heze54@hezesoft.org> Message-ID: <op.tg1qucocg9uou4@pec54.serced.net> Subject: Re: [suse-sles-e] if-up and route add -net command
And now.. if I need to run a vncserver :2 -name heze54 -depth 24 -geometry
1024x768 command every time the machine starts or re-starts?
Where do I need to put into?
best regards
heze54
On Fri, 06 Oct 2006 19:36:07 +0200, Alexei_Roudnev
<Alexei_Roudnev@exigengroup.com> wrote:
> Hmm, I am not against using routes files IF you need many many routes
> and IF
> you know, how it all works.
> I just asked, why don't use standard tool (YaST2) when you need to add 1
> route abnd never did it before.
> As usual:
> - do something once / 2 years and never did it before - use YaST2;
> - do something daily - learn how it works and do manually.
>
>
> ifup script dont work because it (sometimes) is called from hot plugin
> daemon in random sequence, and
> so it works too early.
>
> Through I can't agree - if you have more than 2 - 3 routes in the
> file,then
> your design is wrong and you better use dynamic routing (ocfs for
> example)
> instead. Static route is a BIG EVIL -:). (Exception - some systems with
> load
> balancers).
>
>
> ----- Original Message -----
> From: "Heiko Helmle" <heiko.helmle@head.de>
> To: <suse-sles-e@suse.com>
> Sent: Thursday, October 05, 2006 11:41 PM
> Subject: Re: [suse-sles-e] if-up and route add -net command
>
>
>> Alexei_Roudnev schrieb:
>> >
>> >
>> > Of course - and it is EXACTLY what YaST2 is doing! Why to use 'vi'
>> when
>> > system have standard tool for this thing?
>> > (Except if you use some automation, of course - unfortunately YaST2
>> have
> not
>> > command line interface so we can't use it
>> > for automation).
>>
>> a) because YaST kills the comments out of the routes file and depending
>> on the count of your routes you might want to have some comments in
>> there (and keep them).
>> b) the routes file can do some more things than YaST exports to the
>> user. Try looking at the manpage.
>>
>> > SuSe is not one of _old dumb linux, with 'vi' as the only
>> administrative
>> > command_. Doing things manually can break it, exactly as doing things
>> by
>> > 'regedit' in windows. Use YaST2 when it is possible, and 'vi' only in
> 'hard
>> > cases' or if you are doing something very complicated.
>>
>> Depends on your needs. After configuring your routes with YaST it pulls
>> all your network interfaces down and up again. There are some particular
>> cases where you really do not want that only for some new host route.
>> And if you know where stuff is in /etc, you'll probably find your way
>> easily in most other linux flavours (be it RHEL or Ubuntu LTS or
>> whatever) as most files there are quite easy to understand (except
>> /etc/sudoers i guess).
>>
>> Kind Regards
>> Heiko
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
>> For additional commands, e-mail: suse-sles-e-help@suse.com
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
> For additional commands, e-mail: suse-sles-e-help@suse.com
>
-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ Antes de imprimir piensa en tu responsabilidad y compromiso con el MEDIO AMBIENTE --------------------------------------------------------------------- To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Sat Oct 07 2006 - 12:17:35 CEST