April 2006 - openSUSE Users - openSUSE Mailing Lists

What is eaccess()? Trying to compile ruby from the factory
by Greg Freemyer 04 Apr '06

04 Apr '06

I've previously downloaded and compiled ruby 1.8.3 from the factory on a SUSE 10.0 machine. On the same machine, I just tried to do the same with Ruby 1.8.4 I'm getting compile errors. gcc main.o libruby-static.a -ldl -lcrypt -lm -o miniruby -O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -fPIC -DRUBY_EXPORT -rdynamic -Wl,-export-dynamic libruby-static.a(file.o): In function `test_r': /usr/src/packages/BUILD/ruby-1.8.4/file.c:1125: undefined reference to `eaccess' libruby-static.a(file.o): In function `test_w': /usr/src/packages/BUILD/ruby-1.8.4/file.c:1160: undefined reference to `eaccess' libruby-static.a(file.o): In function `test_x': /usr/src/packages/BUILD/ruby-1.8.4/file.c:1194: undefined reference to `eaccess' libruby-static.a(dln.o): In function `dln_find_1': /usr/src/packages/BUILD/ruby-1.8.4/dln.c:1814: undefined reference to `eaccess' I'm comfortable with compiling C code, but I don't think I've ever heard of eaccess. Any ideas on how I can go forward. Thanks Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century

2 2

YOU breaks Xorg
by Peter Onion 04 Apr '06

04 Apr '06

I ran YOU for the first time in a few weeks yesterday. Today both my SuSE 10.0 boxes have broken X configurations.... Both machines have ATI cadrs and use the ATI fglrx drivers. For some reason something changed the "driver" line in xorg.conf to say "radeon" where is used to say "fglrx". SInce the radeon driver doesn't support my cards I ended up with broken X (i.e. No dual head, No DRM, No 3D acceleration/openGL). Why should anything in YOU be messing about in xorg.conf files ? Peter

7 15

Reduced DVD capacity?
by Josef Wolf 04 Apr '06

04 Apr '06

Hello! Earlier, my plextor px708a happily wrote almost 4700000000 bytes (4.7GB in marketing speak). A couple of weeks ago, the troubles began. Growisofs still writes that much without an error message. But reading them back gives an IO error at about 4300000000 Bytes: ~ # dd if=/dev/cdrecorder of=/dev/null 8388604+0 records in 8388604+0 records out 4294965248 bytes (4.3 GB) copied, 964.8 seconds, 4.5 MB/s My first guess was that the media (RW) was bad, so I tried some new ones. Then, I decided to change the burner, but Plextor px716a has the same problem. Now I noticed that the error is always at the same position. Please note that 4294965248==0xfffff800, which looks pretty much like an integer overflow to me. When I installed suse-10.0 (professional, ot opensuse), everything worked as expected. Since I run YOU regularly, I assume that one of the updates is responsible for this problem. But I can't say which update exactly. Any ideas? BTW: ~ $ uname -a Linux raven 2.6.13-15.8-default #1 Tue Feb 7 11:07:24 UTC 2006 i686 athlon i386 GNU/Linux PS: I tried to search bugzilla, but it looks like a login is required to search it?

2 2

RE: [SLE] YAST2/YOU Control
by Chiu, PCM (Peter) 04 Apr '06

04 Apr '06

Thanks a lot, Kai, most helpful. Peter -----Original Message----- From: kai [mailto:kai@perfectreign.com] Sent: 31 March 2006 13:50 To: suse-linux-e(a)suse.com Subject: Re: [SLE] YAST2/YOU Control On Friday 31 March 2006 03:03 am, Chiu, PCM (Peter) wrote: > Two questions really: > > a. where can I get more details in the setting up the control on YAST2 > - YOU in particular? > Both the man page on yast2 and the document refered in > /usr/share/doc/packages/yast2 > do not give more details in controller how the online update is > handled. > > b. On a system that I have previously configured to have automated > updates from yast2, > I would like to disable one product from being updated. I am not > convinced the way > I did it have actually taken into effect. Basically from Yast2, > on-line update, > manually selected patches, next, searrch (as the one in question > does not > show up in the YOU Patches), found a grey-out product, select it, > then > from You Patch tab- All in this list - Protected - Do not modify. > (Here I noticed the icon has not been changed.) I think you should have it. If you want to be sure, go into YaST2 under System > Software Management and find the application you want to not be updated. When it shows up on the list in the right pane, right-click it and select Proected -- Do Not Modify. You can certainly test this with something innocuous if you want to be sure. For example get an old RPM of some unimportant game and then protect it then do a YOU to see that it doesn't update. -- kai - www.perfectreign.com www.livebeans.com - the new NetBeans community 43...for those who require slightly more than the answer to life, the universe and everything. -- 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 Please read the FAQs: suse-linux-e-faq(a)suse.com

1 0

Re: [SLE] The future of SuSE Linux as we know it?
by lerninlinux＠comcast.net 04 Apr '06

04 Apr '06

> > > As you probably know, Mandriva is no longer the old Mandrake but is now > > > a combination of Mandrake, Conectiva and Lycoris. > > > > > > > according to reports, Mandriva is hemoraging money, showed its > founder to the door, and unless Mandriva team gets it act together, it > most like will suffer an untimely demise. I haven't heard about them hemoriging! Last I knew they were doing much better. They were out of bankruptcy and that was when they bought up Conectiva, then they signed a deal with some south American country, where they come preloaded on thier pc's. Last I heard, that accounted for 25% of thier business. > Interesting to note. I actually switched from Mandrake to SuSE because > of my perception of them as going down in quality. I had run Mandrake 6 > on my laptop and 8 on a test machine. When 10.0 came out I tried to use > it but it wouldn't detect my hardware. Popping SuSE 9.1 in did the > trick. I've been a SuSE/SUSE fan ever since. > > Besides, YOU is so much easier than urpmi. (Unless they now have some > similar GUI tool which I don't know of.) I switched from Mandrake to Suse, after a few things built up to bother me. I went from RH5.2 to Mandrake 6 through 8.0, then I got one of those infamous magazines with the bad discs. I tried two other people's I knew and no luck either. I had bought the box sets previously, but the one time I registered it, and tried to use the installation support, in the alloted time, I received no replies or help. That was when I started watching the newsgroups a lot more. The next time I went to buy a Mandrake, it wasn't in stores any longer (since been rectified, with one store). Suse started appearing in stores, locally, and I knew it had a big following, so I made the switch. Been much happier since. And I also agree about YOU. Now I feel more comfortable as I have one well functioning system, so I plan on taking a couple of older ones, and trying things like Gentoo on them, so I learn more about how things work. As I am not sure what I know, and what distro's like Suse, help make easy for me.

2 1

Re: [opensuse] 10.1 Beta 9 uses too high refresh for 1280x1024 LCD
by Mark Gray 04 Apr '06

04 Apr '06

Steffen Winterfeldt writes: > On Tue, 4 Apr 2006, Mark Gray wrote: >> Steffen Winterfeldt writes: >>> On Mon, 3 Apr 2006, Mark Gray wrote: [snip] >> How does the installer know it is a monitor capable of 1280x1024 in >> the first place? DDC? If so, this monitor can also communicate its >> "best" refresh for that resolution. I think the problem could have >> something to do with confusion over whether it is a CRT or LCD monitor >> because it is difficult to get sax2 to generate a good modeline for >> it, and it looks like that is because it is confusing it with a CRT >> monitor with a similar model number. (But this is just a guess by >> someone too busy to look closer at the problem.) > No, the problem is the other way around. :-) > Your monitor is properly detected. Just your BIOS does not care. And, as I > wrote, you have _no influence whatsoever_ on the timing the BIOS is going > to use. Okay, I see now. The problem is that the VESA standard has stood still since the death of DOS. Now more sophisticated hardware detection and configuration is necessary, bypassing the BIOS entirely. (Apart from some minimal low resolution support for BIOS configuration, booting, and screens displayed prior to the OS'es hardware detection, and loading of drivers.) The BIOS on this machine uses 640x480 for the boot screen by the way, and Win-XP uses a low resolution Splash screen before it boots (rebooting into Win-XP to make a note of what resolution it uses would be tricky since the time window to gather the information is rather short (it is an AMD64-x2 4200+ with 3GB of ram, and boots rather quickly.) The bottom line as I see it is that unless the install is willing to default to 1024x768 or below, the days of relying on the BIOS to properly configure your video card for the monitor are numbered. Further updates to the VESA standard to take into account new video cards and monitors are not very likely. [snip]

1 0

10.0 floppies
by jdd 04 Apr '06

04 Apr '06

Hello :-) SUSE Linux used to offer floppies images on the /boot directory of the first disk. these images couls be made from linux or from Windows. There where a windows start app on the first cd and inserting it in a windows machine gave the choice of booting linux (the cd) or making floppies. this is no more available (10.0). There is a perl utility (mkbootdisk) that build the (7) floppies. so: * where are the floppies images? Looks like they are cat'ed (on the "rescue" 21Mb file?) - how are they built with the script, reading it didn't gave me enough clues, * if so why does rawrite still exist in the cd? don't seem anymore usefull. (perl is not that usual on windows :-) * what is the real + in this system? are the 64 bits floppies so similar to 32 one is enough to change just some bits? thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos

2 5

openSUSE Status Meeting 2006/04/04 18:00 CET (17:00 GMT)
by Sonja Krause-Harder 04 Apr '06

04 Apr '06

Hi there, the next openSUSE status meeting will take place at the official #opensuse IRC channel on freenode (irc://irc.freenode.net/openSUSE) tomorrow at 2006/04/04 18:00 CET (17:00 GMT) This meeting is meant to discuss the latest developments in and around openSUSE. Topics so far: 1. Status SUSE Linux 10.1 2. Status Build Service 3. openSUSE Wiki Update 4. Linuxtag 2006 Planning 5. Cleanup old Action Items If you have additional topics, please add them to the meeting wiki page at: http://en.opensuse.org/Meetings/Status_Meeting_2006-04-04 as soon as possible. Also, if you cannot attend the meeting tomorrow, but have questions regarding any agenda topic, please add them to the meeting wiki page as well. For general info about our IRC meetings read: http://en.opensuse.org/Meetings/About For details about this IRC meeting read: http://en.opensuse.org/Meetings/Status_Meeting_2006-03-07 For a general technical introduction to IRC (Internet Relay Chat) see http://www.irchelp.org/ (not affiliated with openSUSE) or enter "IRC help" into your preferred search engine. The network we use is freenode - for more information on this, including how to find a server, visit http://freenode.net/ (not affiliated with openSUSE either). cheers, Sonja -- Sonja Krause-Harder (skh(a)suse.de) Research & Development SUSE Linux Products GmbH

3 3

Re: [opensuse] 10.1 Beta 9 uses too high refresh for 1280x1024 LCD
by Mark Gray 04 Apr '06

04 Apr '06

Steffen Winterfeldt writes: > On Mon, 3 Apr 2006, Mark Gray wrote: > >> Steffen Winterfeldt writes: >> >>> On Mon, 3 Apr 2006, Mark Gray wrote: >>> >>>> This is the same thing that happened when I installed SUSE-10.0 boxed >>>> set on this machine -- when starting the install using the default >>>> 1280x1024 resolution, the installer uses too high a refresh rate for >>>> my brand new HP vs17e LCD monitor H: 46.4 kHz V: 87Hz. The best >>> This is 43Hz interlaced (!). Not much to do about it, the BIOS picks >>> the timing. >> The computer is an HP also -- you'd think the BIOS would know better. >> When I encountered the problem with 10.0 there were a lot of hits for >> the same problem on google, so some sort of warning might save some >> installation support calls. > How should I warn? The BIOS doesn't tell the timing it chooses. Neither > before nor after a video mode change. How does the installer know it is a monitor capable of 1280x1024 in the first place? DDC? If so, this monitor can also communicate its "best" refresh for that resolution. I think the problem could have something to do with confusion over whether it is a CRT or LCD monitor because it is difficult to get sax2 to generate a good modeline for it, and it looks like that is because it is confusing it with a CRT monitor with a similar model number. (But this is just a guess by someone too busy to look closer at the problem.) In any case, monitors which can do interlaced video are becoming rare according to www.hwupgrade.com, so using it is probably asking for trouble in the first place. >From looking on google this is not an isolated problem. Hiding the default resolution chosen for the installation behind the F3 "other options" button probably is asking for trouble for new users who have not installed SUSE dozens of times already. (I have an older monitor which "lies" about how well it can do resolutions above 1024x768, so I have a long experience with changing resolution during install -- but in its case it will display up to 1600x1200, but just too fuzzily to put up with.) As an aside, Fedora Core 5 defaults to 800x600 for the install (ugly as sin, but foolproof.) Perhaps defaulting to a more conservative resolution and refresh would save your installation support staff some money?

2 1

Re: [SLE] The future of SuSE Linux as we know it?
by Kai Ponte 04 Apr '06

04 Apr '06

> On 04/04/06, Basil Chupin <blchupin(a)tpg.com.au> wrote: > > >>> In the latest TUX magazine there is a comparison of several Linux > > >>> distros and SuSE does NOT come up on top. The top choice is Mandriva, > > >>> and SuSE is beaten by other distros (Mepis comes in 2nd and Fedora as 3rd). > > >>> > > >>> > > >> I read this yesterday afternoon. It's interesting reading but I don't > > >> agree with the overall result. It does seem to be skewed. > > >> > > > > > > Anytime Mandriva comes out at the top of the list in a distro shoot-out, it makes the entire results of a product comparison suspect. Granted, certain community pundits (LinuxFormat & Tux) like Mandriva but the quality of the distribution is no longer the cutting edge distro that it was a year or so back, > > > > As you probably know, Mandriva is no longer the old Mandrake but is now > > a combination of Mandrake, Conectiva and Lycoris. > > > > > according to reports, Mandriva is hemoraging money, showed its founder to the door, and unless Mandriva team gets it act together, it most like will suffer an untimely demise. > > > > > Ah, so Mandriva is going and doing a "SuSE" then :-)? SuSE's old and > > intelligent brigade has been deserting also - or haven't you heard about > > that? - and Novell is also going down the financial gurgler. When they > > discovered (?)last year that SuSE actually made some money for them they > > were flabbergasted - which just goes to show how well they did their > > homework when they decided to buy SuSE. > > I would like to point out that, though I doubt the conditions that > testing was performed under in the Tux Magazine round up, I actually > like the latest two versions of Mandriva. Prior to these it was > absolutely awful. Now it is very good, very useable and I would not > hesitate recommending it to anybody. I would point them to SuSE as > being better :-) Interesting to note. I actually switched from Mandrake to SuSE because of my perception of them as going down in quality. I had run Mandrake 6 on my laptop and 8 on a test machine. When 10.0 came out I tried to use it but it wouldn't detect my hardware. Popping SuSE 9.1 in did the trick. I've been a SuSE/SUSE fan ever since. Besides, YOU is so much easier than urpmi. (Unless they now have some similar GUI tool which I don't know of.) > > Now, how do I also become a certified Cleavage Inspector :-))) is > this dependent upon one's height? Yeah, where do I sign up?? -- kai ponte www.perfectreign.com || www.filesite.org linux - genuine windows replacement part

1 0