RE: [SLE] Please oh please don't ko yast1!!!!!!!
Hi, I fully agree with keeping Yast. I'm not using X-windows, because my linux box is only running as a router, mailserver, etc in a network. It doesn't even have a keyboard and monitor connected to it. So I prefer using a terminal emulator to maintain that machine. Best regards, Geert-Jan de Laat
-----Original Message----- From: joe lerch [mailto:jel2@earthlink.net] Sent: donderdag 15 maart 2001 5:17 To: suse-linux-e@suse.com Subject: Re: [SLE] Please oh please don't ko yast1!!!!!!!
On Thursday 15 March 2001 00:00, you wrote:
While YaST2 is prettier, and there are some newer tasks that only YaST2 can do, like ALSA sound setup, YaST1 is still more flexable and powerful, along with being easier to use, believe it or not. It's also faster. SuSE, KEEP IT!
I want to echo these thoughts. The worst part of my upgrade to SuSE 7.1 was using Yast2. The people at SuSE appear to be making the move to YaST 2, which is ok for new users but for people that have learned linux using SuSE ( started with 5.3) and YaST, the people at SuSE should keep YaST. Give the people a choice, it's that freedom to choose that makes Linux far better than a proprietary system that forces you to take certain options.
joe
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Disclaimer 1. This e-mail is for the intended recipient only. If you have received it by mistake please let us know by reply and then delete it from your system; access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. 2. If you as intended recipient have received this e-mail incorrectly, please notify the sender (via e-mail) immediately. This e-mail is confidential and may be legally privileged. DSM does not guarantee that the information sent and/or received by or with this e-mail is correct and does not accept any liability for damages related thereto.
On Thursday 15 March 2001 04:48, Laat-de, Geert-Jan wrote:
Hi,
I fully agree with keeping Yast. I'm not using X-windows, because my linux box is only running as a router, mailserver, etc in a network. It doesn't even have a keyboard and monitor connected to it. So I prefer using a terminal emulator to maintain that machine.
Best regards,
I guess I'm finding this whole thread a bit surprizing. People are talking about problems with both YaST 1 and YaST2 that I have not encountered. There *is* a console mode for YaST2. I don't believe YaST2 covers all the functionality of YaST1, but it is a newer product, and is not mature yet. I believe SuSE should consolodate YaST into one product with both a GUI and console mode of operation. What we should push for in the consolodated YaST is to perserve all the features we like in YaST1, and to improve the functionality of YaST2. I find YaST2's console UI a bit unintuitive. I can figure it out, but I find myself trying the "natural" key strokes before I realize they don't work. As far as the problems others said they have with YaST1 or YaST2, neither one has been perfect for me, but they have both performed adequately. I very rarely have an actual "malfunction". Steve
On Thu, 15 Mar 2001, Steven T. Hatton wrote:
I guess I'm finding this whole thread a bit surprizing. People are talking about problems with both YaST 1 and YaST2 that I have not encountered. There *is* a console mode for YaST2.
I was about to mention that :)
I don't believe YaST2 covers all the functionality of YaST1, but it is a newer product, and is not mature yet. I believe SuSE should consolodate YaST into one product with both a GUI and console mode of operation. What we should push for in the consolodated YaST is to perserve all the features we like in YaST1, and to improve the functionality of YaST2. I find YaST2's console UI a bit unintuitive. I can figure it out, but I find myself trying the "natural" key strokes before I realize they don't work.
The ncurses interface is still under heavy development. And YaST1 will stay, as long as YaST2 does not have all the features that YaST1 offers. But in the long run I expect YaST1 to vanish - it is a maintenance nightmare to maintain both of them in parallel. LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany There is always a mistake just waiting for you to make.
On Thu, 15 Mar 2001, Lenz Grimmer said:
On Thu, 15 Mar 2001, Steven T. Hatton wrote:
I guess I'm finding this whole thread a bit surprizing. People are talking about problems with both YaST 1 and YaST2 that I have not encountered. There *is* a console mode for YaST2.
I was about to mention that :)
I don't yet have 7.1, so I don't know if some of the following comments about anomalies have been addressed in 7.1 ... If they're going to be merged, then I would suggest maybe having two builds (two separate binaries): one smaller text only for memory limited machines, and the other full blown w/ GUI. Also I would like to see a prompting menu come *before* it goes into graphics mode, so that problems with a fresh install can be more readily avoided. Having to type 'manual' to do this is fine for experience SuSE people, but it has eluded a lot of people new (and not so new!) to SuSE. It would also be nice if this menu had some text explaining that if there were problems encountered with the GUI mode to choose the text mode. And while we're on the YaST subject, I've also encountered many comments from others about how they had problems trying to do a minimal install. In the past YaST1 has had a peculiarity where after choosing a configuration (e.g., minimal install cfg), one must choose the "Replace" option at the bottom of the menu screen in order to have yast internally deselect all packages which are selected for the default configuration. If this isn't done, then whatever pkgs are part of the newly chosen cfg are *added* to the preselected ones, and the person ends up being quite puzzled about why it happened. Many think it's not possible to do a minimal install using YaST for this reason. I think a better approach would be to not have YaST come up with this default cfg pre-selected but force the user to make a selection, and only then have YaST do the selection of the pkgs which apply to the apply to the particular cfg which has been selected. Likewise when the user modifies a cfg selection on this screen, somehow have YaST do the appropriate pkg selections without requiring the user to "click" the 'Replace' option at the bottom of the screen. ---------------------------------------------------------------------- John Karns jkarns@csd.net
participants (4)
-
John Karns -
Laat-de, Geert-Jan -
Lenz Grimmer -
Steven T. Hatton