Mailinglist Archive: opensuse (2372 mails)
| < Previous | Next > |
Re: [SLE] goodbye YaST?
- From: Cliff Sarginson <cliff@xxxxxxxxxxxxxxx>
- Date: Mon, 8 Jan 2001 14:10:41 GMT
- Message-id: <E14Fd0T-00075d-00@xxxxxxxxxxxxxxxxxxxxxx>
> YaST - i won't even touch YaST2 here - is nice for the beginner and
> the person who wants to use a functional system without worrying too
> much. but YaST is a nightmare for the established linux expert (i am
> blushing just a litte - but please don't consider me arrogant). it's
> the windows syndrome - make administration easier at the cost of
> complicating things and hiding important details. for instance,
> configuring my PCMCIA eth0 device is not something to be done in any
> other location than /etc/pcmcia/network.opts.
>
> but hey, i am an established redhat/debian Linux user and new to suse,
> so i shall not rave and drool about things that i don't really have
> experience with right here.
>
> i do have a question: what if i decided to abandon YaST, to uninstall
> it (YaST2 is already gone anyway), to move all YaST config stuff to
> something like /var/adm/backup or ~root/backup, to create my own
> scripts, and to use suse as a linux system and not as a suse system
> with YaST? sure, i'd loose installation support, but i don't really
> want that anyway. are there other consequences?
Well. I have two reactions to this.
Firstly I think it may be a huge amount of work, and probably bothersome
work, because yast does look after most of the dependencies for you.
You should consider rc.config as being the cornerstone here - an the
sub-scripts (so to speak) that it calls. In principle this is good system,
certainly better than linuxconf, which is a real nightmare. I would be
worried that you would be chasing your tail so-to-speak for quite a while.
But if you have the time.
My second reactions (I have asked Suse for an official statement on Yast1
but they are unlikely to give one) - is that if you do a good job of it
and package the stuff together a bit you may become famous and all
the pissed-off Suse people will knock at your door :)
Personally I think my days using Suse are numbered anyway, the direction
they are going in, and their complete lack of interest in their
small-time users is starting to grate on me. They never listen or respond to
suggestions or criticism. They are just trying to out-redhat redhat now.
Ah well.
Shame really, it is a pretty neat distribution.
Good luck with your venture !
Cliff
> what about certifications? as i understand, suse uses LPI certs - so
> knowledge of YaST should not be required. am i right?
>
> is anyone of you running suse without YaST? experiences?
>
> thanks,
> martin
>
> [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net
> --
> nobody expects the spanish inquisition.
>
> --
> To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
> For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the FAQ at http://www.suse.com/support/faq
>
> the person who wants to use a functional system without worrying too
> much. but YaST is a nightmare for the established linux expert (i am
> blushing just a litte - but please don't consider me arrogant). it's
> the windows syndrome - make administration easier at the cost of
> complicating things and hiding important details. for instance,
> configuring my PCMCIA eth0 device is not something to be done in any
> other location than /etc/pcmcia/network.opts.
>
> but hey, i am an established redhat/debian Linux user and new to suse,
> so i shall not rave and drool about things that i don't really have
> experience with right here.
>
> i do have a question: what if i decided to abandon YaST, to uninstall
> it (YaST2 is already gone anyway), to move all YaST config stuff to
> something like /var/adm/backup or ~root/backup, to create my own
> scripts, and to use suse as a linux system and not as a suse system
> with YaST? sure, i'd loose installation support, but i don't really
> want that anyway. are there other consequences?
Well. I have two reactions to this.
Firstly I think it may be a huge amount of work, and probably bothersome
work, because yast does look after most of the dependencies for you.
You should consider rc.config as being the cornerstone here - an the
sub-scripts (so to speak) that it calls. In principle this is good system,
certainly better than linuxconf, which is a real nightmare. I would be
worried that you would be chasing your tail so-to-speak for quite a while.
But if you have the time.
My second reactions (I have asked Suse for an official statement on Yast1
but they are unlikely to give one) - is that if you do a good job of it
and package the stuff together a bit you may become famous and all
the pissed-off Suse people will knock at your door :)
Personally I think my days using Suse are numbered anyway, the direction
they are going in, and their complete lack of interest in their
small-time users is starting to grate on me. They never listen or respond to
suggestions or criticism. They are just trying to out-redhat redhat now.
Ah well.
Shame really, it is a pretty neat distribution.
Good luck with your venture !
Cliff
> what about certifications? as i understand, suse uses LPI certs - so
> knowledge of YaST should not be required. am i right?
>
> is anyone of you running suse without YaST? experiences?
>
> thanks,
> martin
>
> [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net
> --
> nobody expects the spanish inquisition.
>
> --
> To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
> For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the FAQ at http://www.suse.com/support/faq
>
| < Previous | Next > |