July 2002 - openSUSE Users - openSUSE Mailing Lists

Yast 2 SUCKS !!!
by Fábio Rabelo 02 Aug '02

02 Aug '02

I'm Suse user since version 6.1, then migrating from "redhat" like .. After dedicating this weekend to instal at first time Suse 8.0 .. and REALY hate them !!! First of all : instalation ! My test bed is a Pentium 150, motherboard VIA MVP3, 64 RAM . more then enough to run a gateway/firewall to 30 or 40 machines . Suse 7.2 ou 7.3 installs on them smoothly, in 1/2 hour ou less... more 1/2 hour to setup deamons and firewall ... well ... to install suse 8.0 I MUST setup a swap of 40 MB BEFORE anything else ... AND, to select correct set of packages, I spend 3 hours !!! my "DMZ" selection ( from suse7.2/7.3 Yast1 ) are missing, I MUST make a selection by hand and at EACH package that I cut/select this machine "things" for about 1 minute before I can go to the next !! What a hell are Suse developers thinking ?!?!? I dont have time to waste !!! if they have, make Yast 2 USABLE or get back Yast 1 ... or free Yast 1 to comunity proceed with development ! But this is unaceptable !!! And then ...when I will set up the deamons, the rc.config is put away WITHOUT a equivalent replacement !!! If I want to make this setup without tweeking ( the MAJOR reason that I migrate from "red hat" like to Suse ) I MUST use AGAIN this great peace of sheet called Yast2, and, I must remember run levels and other things that I running awy from when migrate to Suse !!! What a hell is this ?!?!? involution ??? steps back ??? If Suse don't release a "Suse 7.4" with kernel 2.4.18 or 2.4.19 or a Suse 8.1 WITH Yast1 or MUCH MUCH more fast and friendly Yast 2 I will stay away from Suse until now !! ( and my clients too !! ) Now I can undestand all msg from this list soon after 8.1 release ! This peaple are right !!! Ssue * and Yast 2 sucks !!! Fábio Rabelo

32 59

RE: [SLE] Ridiculous anti-YaST2 arguments, RE:Yast 2 SUCKS
by Richard Bos 02 Aug '02

02 Aug '02

>===== Original Message From "Berge, Harry ten" <berge(a)hitt.nl> ===== >This thread is going on and on. SuSE delivers a *GREAT* product. But, as >many others, I have some problems with YaST2. But I think the solution to >this (and particulary for SuSE) is very simple. Make YaST1 available to the >community. All those people complaining can then be productive and create a >YaST1 that is compatible with the 'sysconfig' structure which is one of the >major changes between 7.3 and 8.0. > >SuSE happy (because they don't have to change yast2), and everybody else >happy 'cause they can hack away and create a YaST1 XP++++ that will become >the best configuration utility ever!!! the source can be downloaded from ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/7.3-i386/SRPMS.update/yast-1.13.3-5. src.rpm Download gives: yast-1.13.3-5.src.rpm mkdir /usr//tmp/yast cd /usr//tmp/yast rpm2cpio yast-1.13.3-5.src.rpm > yast-1.13.3-5.src.cpio cpio -id < yast-1.13.3-5.src.cpio most relevant packages seem to be: yast-1.13.3.tar.gz yast.fdisk.tar.gz yast.misc.tar.gz Now get the *spec file by installing the srpm. Create a project at sourceforge import the the files delivered by the above tar.gz files and your settled :) Happy hacking :) -- Dit bericht is verzonden met Webmail van Freeler. Ook snel en betrouwbaar toegang tot internet? Meld je aan op http://www.freeler.nl

6 7

Missing the obvious with my scanner?
by Clayton Cornell 02 Aug '02

02 Aug '02

OK, I am trying to get my USB HP scanjet 2200c working with SuSE 8.0. According to the various webpages on scanners in Linux (eg http://www.semeniuk.net/linux/hp2200/ ) I should be able to use the plustek backend to fire up the scanner. Thing is, after a couple hours of reading and trying things it's still not working. I have made some progress, but I seem to be stuck trying to initialize the silly thing. Here's what I have so far...... - I can see the scanner if I open the SuSE hardware-detect applet. - If I run usbview, it takes a while - more than a minute, but the window eventually pops up and hanging off one of the USB root devices is the usbscanner device. - cat /proc/bus/usb/devices gives me (as one of the results): ------------------------------------------------- T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0605 Rev= 1.00 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usbscanner E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl= 16ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms ----------------------------------------------- sane-find-scanner gives me: -------------------------------------------------- sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0605) at device /dev/usb/scanner0 sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0605) at device /dev/usbscanner --------------------------------------------------- so... that seems to be right. I have edited /etc/sane.d/plustek.conf so that it looks like this (edited down to take out the instruction comments to save space in the email): --------------------------------------------------- warmup -1 lOffOnEnd -1 lampOff -1 [usb] 0x03f0 0x0605 option lampOff 180 option lOffOnEnd 1 device /dev/usbscanner ------------------------------------------------------- Now when I try to start a scan manually, nothing happens. For example: ---------------------------------------------------------- scanimage -d plustek:/dev/usb/scanner0 scanimage: open of device plustek:/dev/usb/scanner0 failed: Error during device I/O ---------------------------------------------------------- Permissions on /dev/usbscanner are: crw-rw-rw- 1 ccornell users 180, 48 Mar 23 20:50 usbscanner Permissions on /dev/usb/scanner0 are: crw-rw-rw- 1 ccornell users 180, 48 Mar 23 20:50 scanner0 scanimage --list-devices returns the error that no scanners were identified. xscanimage just hangs there for a while (~2 minutes) and exits with a message that no scanners were identified. Kooka takes about 2 minutes to start up, and cannot find any scanners. xsane is the same... hangs for a while, and then reports back that there are no scanner devices. So, anyone see what I have missed here? Why is this scanner just sitting there so smugly, refusing to startup? C.

3 5

3D in SuSE 8.0
by Jim Rohacek II 02 Aug '02

02 Aug '02

Can anyone tell how I can configure 3D acceleration in SuSE 8.0, without Yast2?. Any help would be appreciated. Thanks, Jim Powered by SuSE 8.0, Kernel 2.4.18

5 5

Fwd: Re: [SLE] Yast 2 SUCKS !!!
by Jul 01 Aug '02

01 Aug '02

---------- Forwarded Message ---------- On Sunday 28 July 2002 19:38, you wrote: > I have to say that SuSE rules... There is no question about it. You will But not YaST2 - it is slow big and does not cover all functionality of YaST [1]. > never find anything better, so go and buy 100 copies, support the SuSE > team. Do not be so fast As soon as they restore respect to long term supporters. Jul -------------------------------------------------------

15 18

RE: [SLE] Shut-Down Problem NOT Solved
by Jostein Berntsen 01 Aug '02

01 Aug '02

Hi, Have you tried these solutions? http://sdb.suse.de/en/sdb/html/pohletz_shutdown_73.html ftp://ftp.suse.com/pub/suse/i386/update/7.3/kernel/2.4.16-20020416/ Regards, Jostein >===== Original Message From gilson redrick <gilsonr(a)cityisp.net> ===== >On Monday, 29 July 2002 14:02, Anders Johansson wrote: >> Maybe, but I could swear that this machine shut down properly when I >> had 7.3 on it. >> >> I'm almost on the verge of reinstalling 7.3 just to prove the point >> >> //Anders > >I've been following this thread with great interest. For the past nine >months or so, I've been using 7.3, installing (and re-installing many >times) fresh. When I had 7.2 (and, before it, 7.1), the computer >shutdown properly (as still does on the rare occasions when I'm forced >to use W98). With 7.3, it doesn't. > No matter what I do, the result is still the same: I have to shut >it down myself. I have had APM, APIC and ACPI off, on and then off, as >appended to the booter and/or modifying the BIOS, with no visible >difference. > Precisely to satisfy my curiosity, I re-installed 7.2 (good thing >I have a large HD!), and I proved to myself that with 7.2 (as it came >from the CD, without any modification on my part) the computer shuts >down, as it does with W98 and Mandrake 8.0. But not with SuSE 7.3! > This is not a laptop, but an eMachines desktop with AMD K6. BTW, I >thought the problem with 7.3 was the 2.4.10 kernel, so I installed the >2.4.18; no difference. > >-- >Regards, >gr, in /usually/ sunny, balmy Florida's Suncoast. > >-- >Check the headers for your unsubscription address >For additional commands send e-mail to suse-linux-e-help(a)suse.com >Also check the archives at http://lists.suse.com

9 12

Re: [SLE] Once again I ask for help. Customer Service? what's that???
by Paul Ryan 01 Aug '02

01 Aug '02

Hi Bob, > > Tried installing Suse 7.3 on P4 machine and the installation > > process > > I'm not sure there's still inst. support available for 7.3 True - there isn't. It has been >60 days since 8.0 was released. > > mount: block device /dev/hdc is write-protected, mount read-only > > mount: The problem is with your cdrom drive - samsung - as it's not atapi compliant so it won't work. Paul

3 2

mk_initrd - failed to mount image (help)
by Darren Harmon 01 Aug '02

01 Aug '02

Hi; I think the subject says it all. After rebuilding my kernel (and modules) I run mk_initrd and after a small think it ends with the line, failed to mount image. I've tried several different kernel sources and they all come up with the same message. ------------------------------------------------------------------ Here is the total output from mk_initrd. using "/dev/hda6" as root device (mounted on "/" as "reiserfs") creating initrd "//boot/initrd" for kernel "//boot/vmlinuz" (2.4.18) failed to mount image --------------------------------------------------------- This is how I build a kernel (as per the reference book p 234). cd /usr/src/linux make xconfig (choose a known working configuration with SuSE 8.0) make dep make clean make bzImage make modules cp /usr/src/linux-2.4.18/arch/i386/boot/bzImage /boot/vmlinuz make modules_install mk_initrd lilo Thanks for any help (I cannot turn off my computer until I have this fixed:-) -- --------- Darren Harmon http://www.darrenharmon1.uklinux.net

4 7

Fwd: Look at that Asteroid
by Clive Rogers 01 Aug '02

01 Aug '02

Hi peoples, Just got this in my email. Looks exciting enough to want to try and image it !!! There's no danger of a collision. Even so, a big space rock will soon come so close to Earth that sky watchers can see it through binoculars. FULL STORY at http://science.nasa.gov/headlines/y2002/30jul_ny40.htm?list563691 -- Clive. Fighting for darker skies.

6 9

"X" application Paths?
by Chris Roberts 31 Jul '02

31 Jul '02

OK, here's an easier, newbie-ish one for you! :-) I sometimes try to build applications from magazine CD's that are based on... "X library" stuff. These use a variety of installation procedures but, with default SuSE settings, I usually end up "missing something" :-| In the latest example I'm using command "make all" to build an applications (Procmeter3) based on GTK3+(?). It fails near the start with e.g. gcc being unable to find header files: X11/X.h, X11/Xlib.h... OK, I'm sure I could (eventually) fix this (apologies for the laziness component here :-) but sometimes I need a *GENERAL* prod in the right direction. Is this a question of PATHS not being pre-defined as the author assumed or have I neglected to *install* some component of the X-library? All this under a fairly barefoot SuSE 8.0 installation. Thanks, Chris

2 2