| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
Comments:
<0> what is a 6600gt?
<0> (oh wait - lemme google it)
<1> meh...i want HDR and AA at the same time :|
<2> Skippyboy: nvidia gpu
<3> howdy duder
<4> hola mate
<0> google is my friend.
<5> yaloki: did you get a chance to play with kwlan?
<2> frb-work: nope
<6> on 10.1 can other get direct rendering working and xgl running at the same time?
<3> going to go do some drinking bbl
<5> yaloki: what's the url to the src.rpm?
<2> frb-work: had a very quick look at the source code
<6> just refuses to happen here, I can get only one or the other
<0> ok - I am playing with smpppd now...
<2> frb-work: seems to me that it just has to be run as root
<5> it asks for a root p***word though when run as non-root
<1> alright, more suse related: how can i get a proxy up and running? (such as squid and/or tinyproxy)
<2> frb-work: http://ftp.gwdg.de/pub/linux/misc/suser-guru/rpm/packages/Network/kwlan/src/kwlan-0.4.1-1.guru.suse100.src.rpm
<4> yast -i squid
<0> squid is nice and easy
<1> i already have squid "set up", but it says "access denied" when i try and use it
<0> Hey - have any of you checked out webmin? It is freakin awesome
<5> then you didn't set it up right
<2> frb-work: or here, faster: http://ftp.skynet.be/pub/suser-guru/rpm/packages/Network/kwlan/src/
<1> plus, i'm behind a router.....
<5> acl localnet src 10.0.0.0/16
<5> http_access allow localnet
<1> maybe i should have said i have it installed with default settings, frb-work
<5> those are the importnat lines
<1> what is 10.0.0.0/16?
<5> my intranet
<7> !samba
<8> SAMBA howto for Suse: http://www.tweakhound.com/linux/samba/page_1.htm
<1> so....mine could be 192.168.1.100/120?
<5> not 120, 24
<5> it's a netmask :)
<5> 192.168.1.0/24
<1> ah i thought it was the range of lan IPs
<1> ...so just add those to squid.conf and restart it?
<5> yeah add them near line 1872
<5> that's where the acls are explained
<9> Hi. I've heard some rumours about package management under SUSE 10.1 being a lot harder/different from 9.3 & 10.0. Can anyone comment? What are the major changes?
<2> blahdeblah: well, you said it yourself: rumours
<6> blahdeblah: for the end-user it's pretty much all the same
<9> yaloki: Well, more opinions of nervousness from people who've beta tested.
<6> blahdeblah: it was a long and gruesome beta because of the build-system, yes :P
<9> apokryphos: I'm more interested from the internals/reliability side of things. Will it become more like SLES?
<6> but all is well now
<10> blahdeblah: part of that is because the package management backend was completely re-worked during the beta period..
<9> Is there a summary of the changes available?
<9> (To package management only, i mean)
<10> blahdeblah: they saw significant improvements over time, and I believe the final product is nicer than what was in 9.3/10.0 (multiple update sources, for example)
<9> sarnold: Any dramas with caching updates via squid?
<1> yes....i think they should implement a way for the network install discs to use multiple repos.....
<10> blahdeblah: none that I know of
<10> blahdeblah: but it is relatively new, and I wasn't very involved with beta customers
<6> only annoying things for me with the package management system (which aren't changed in 10.1) are: absolutely no indication of download rate/speed
<4> shuffle2: write the code
<6> both for updating sources and for installing packages
<6> .......and, I'm not really convinced that download -> install, download -> install, is the best method for a package management system
<9> sarnold, apokryphos: I've got a mix of Red Hat, Fedora Core, Debian, SUSE 9.3, SLES 9, OES, and i'm trying to cut back and simplify. :-) SLES updates are a pain because they don't cache, so you have to wait for every single machine. I was planning to settle on SUSE 10.0, but apparently Xen is a lot better on 10.1.
<1> i agree with that too apokryphos
<9> apokryphos, shuffle2: Under 9.3 it was download+, install+, not (download, install)+ - has that changed?
<6> blahdeblah: I enjoy trying out new distros too :). 10.1 is superior to 10.0, for sure, though.
<6> blahdeblah: not sure I follow your notation :P
<10> blahdeblah: ugh, the SLES updates couldn't be run through a proxy? that's annoying
<9> apokryphos: I only care about servers and stability. Eye candy borrowed from Mac OS X is very low on my priority list.
<9> sarnold: You're not wrong.
<9> apokryphos: Notation is regex.
<11> Except for their new updating software :-p
<6> blahdeblah: needless to say, suse is quite stable, as always :)
<11> it is the ****. :-p
<9> apokryphos: All downloads happen first, then all installs.
<1> :P
<5> **** **** ****
<5> I think I found a bug in pppd
<5> I hope factory is working today
<6> blahdeblah: I've only ever tried 10.0 and 10.1 of suse, but in both the method for the package management system is (i) download all the packages required to fix dependencies for x, (ii) install, (iii) download all packages needed for y, (iv) install etc etc
<2> shuffle2: don't hold your breath, not near being a first alpha ;)
<6> instead of (i) download all packages required, (ii) install all packages.
<11> frb-work: last i checked i didn't see any updates
<10> apokryphos: if you run "yast -i foo bar baz", yast would download all requirements for foo, bar, and baz, as well as foo bar and baz themselves, before starting to install any of it
<9> so apokryphos, sarnold, shuffle2, are any of you running production servers on 10.1?
<1> frb-work: what does "http_access allow our_networks" do?
<1> heck no, i'm a desktop user
<9> sarnold: That's what i'm used to.
<5> shuffle2: they define the acl as "our_networks", then allow it
<6> sarnold: is yast -i to be differentiated from the yast graphical installer? Since, it certainly doesn't handle it that way.
<10> blahdeblah: no, i've only got 10.1 test machines
<6> blahdeblah: not me
<9> apokryphos, sarnold, shuffle2: Thanks for the advice, anyway.
<10> blahdeblah: have a nice night
<5> shuffle2: you could say acl goToHell 192.168.45.42/32 then http_access deny goToHell to tell that user he can't use it
<9> sarnold: It's day in UTC+10:00. ;-)
<6> blahdeblah: smart is very good however :)
<1> hehe
<2> blahdeblah: CET counts :P
<10> blahdeblah: +10? where are you?
<6> and it ships in 10.1 by default, doesn't it?
<9> sarnold: .au
<2> apokryphos: it does
<6> *on the cds
<10> blahdeblah: cool ;) have a good day, then :)
<2> apokryphos: but not with preconfigured channels, at least not with packman + my repo
<6> *nod*
<2> apokryphos: but you can still upgrade to my smart package to have them ;)
<5> I use y2pmsh, it downloads on the fly
<1> frb-work: maybe i should have asked this before, but: can i use squid to serve clients outside my lan?
<5> I like it better that way
<9> apokryphos: Let me guess, yet another new package management tool. Why can't Novell release ONE tool that will work with OES, SLES, SUSE, & OpenSUSE. >:-(
<2> or just smart channels --show > channels.txt
<6> blahdeblah: not from Novell or SuSE :)
<5> shuffle2: you can
<1> thats good then :)
<2> blahdeblah: !smart
<5> shuffle2: I've done that before to byp*** lame website blocking
<9> shuffle2: You can even use squid as a reverse proxy in front of apache.
<1> :D
<9> yaloki: ?
<12> what kind of program would I be able to use to check the speed of the cpu?
<6> blahdeblah: indeed, suse is cursed with many package management systems, but it wouldn't be good to dismiss them all. Smart is really very good.
<2> !smart
<8> smart is a great package management frontend that supports many repository formats - more info on http://smartpm.org - grab SUSE RPMs here: http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=System/smart/
<9> NickGarvey: cat /proc/cpuinfo
<2> blahdeblah: see above
<9> yaloki: Thanks
<12> blahdeblah: I want to know how it runs, not what it says it runs ;)
<2> blahdeblah: very interesting project
<6> blahdeblah: there's been some talk about ubuntu (debian-based, of course), switching to the smart package management system.
<10> blahdeblah: the idea with the CODE 10 package management changes is that SLES and openSUSE would use it; I'm not sure about the OES stuff, but I get the impression that their updates needed other functionality that might not fit well into simple "package updates"... maybe that's changing? or a poor impression?
<9> NickGarvey: You mean benchmarking?
<6> blahdeblah: not that I care that much for ubuntu, just that such a move would be quite controversial, needless to say.
<2> yeah, so they can have biarch at last lol
<12> blahdeblah: yup
<6> yaloki: having to make a chroot is really tiresome
<1> prime95?
<2> time a kernel compile ;D
<9> NickGarvey: p*** - try searching for benchmark in yast
<2> apokryphos: a chroot of what ?
<6> make+use, rather
<12> yaloki: I was going to but I have no idea how to compile a kernel in suse, I have done it a few times in gentoo but thats it
<13> is Suse linux better than NetBSD?
<2> apokryphos: it's very easy with y2pmbuild
<9> yaloki: Is smart the default/official SUSE 10.1 package manager?
<6> yaloki: as debian and ubuntu are currently, if you want any 32bit apps you have to recreate an entire chroot and run off that
<2> blahdeblah: no
<2> apokryphos: ah, ok
Return to
#suse
or
Go to some related
logs:
i810 xorg refresh rate lvds
Amallya+undernet
#lisp
paython command
supremedestiny boot
equivalent debug.exe linux
making directory perl
rufsketch1
python isattribute inspect
#linux
|
|