@# Quotes DB     useful, funny, interesting





Google
 
Web www.quotesdb.info
Undernet  |  EFnet  |  Quakenet  |  Freenode  |  Dalnet  |  Ircnet  |  Galaxynet
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



Comments:

<0> didn't see one like that
<1> pm2: dunno, never used opera :-/
<2> susehelp helpme
<2> can you guys see what I'm writing?
<3> pm2: there should also be a kde_use_ipv6
<0> yeah, I think it got it set right now... let me try some stuff
<3> you could of course get a router that doesn't ****
<4> hi all
<4> hmm
<0> yep - seems to be solved, thanks
<4> how easy is XGL/compiz in 10.1
<4> and how is madwifi support
<0> Just out of curiosity, should this default be considered a bug? Or is there something in my home network setup that caused it to fail like that?
<3> madwifi has had the atheros driver removed
<3> !madwifi
<5> For atheros drivers in SUSE 10.1: a) install kernel-source, kernel-syms, gcc, make b) download http://snapshots.madwifi.org/madwifi-ng-current.tar.gz c) extract and run make and "make install" d) configure card in yast -> network devices -> network card



<3> pm2: your router ****s and breaks with ipv6#
<0> benJIman|tov, my home router or something at my ISP?
<3> probably cheap cable modem or something?
<4> why did they remove it from default install
<4> ?
<3> brainiac_ghost: because it violates kernel developers' copyright because it is non-gpl
<0> benJIman|tov, whatever the nice folks at comcast gave me... I know that I didn't setup my debian router box specifically for ipv6, but it seems silly to rely on ipv6 as a default if this is a common issue
<3> pm2: it only seems to be a common issue with some US cable ISPs
<4> benJIman|tov: non-gpl kernel package
<3> brainiac_ghost: that no longer exists
<0> benJIman|tov, I see
<3> pm2: and better to be future proof than support legacy things
<4> benJIman|tov: have they ever thought that by being so stuck up (RMS) it stops h/ware manufacturers supporting linux
<3> and be screwed in the future
<6> Hey guys, I'm having quite a problem here with Suse 10.1.... I have a wireless card integrated in my laptop with a Prism 2.5 chipset. When I first loaded Suse KnetworkManager found my network and connected to it properly... Now I can't even detect my router... Anyone has a clue?
<3> brainiac_ghost: there is no point using a free system if you're going to rely on non-free stuff to talk to the hardware
<7> benJIman|tov: That would be "open" stuff as opposed to "free" ;)
<3> brainiac_ghost: linux is distributed under the GPL, which does not grant you the right to create derivative works unless they are also GPLed, using linux is your choice
<3> daPhoenix: however Linux is Free
<3> if you want to be able todo what you want use bsd
<4> benJIman|tov: still, hardware manufacturers are entitled to make closed src drivers, why shouldn they be allowed to
<4> benJIman|tov: yes, but BSD doesn have these afformetioned wireless drivers
<3> brainiac_ghost: because they;re not entitled to
<4> WHY
<3> because Linux is GPLed
<4> god this makes me hate linux sometimes
<3> noone's forcing you to use it
<8> your hate is misplaced
<3> they can use a "shim" like nvidia, or put non-gpl code in userspace
<9> brainiac_ghost: hardware manufactures may make closed source drivers. But they should not expect them to be supported by anything. If they chose to go alone, they are alone.
<4> benJIman|tov: i suppose
<0> nine, yeah, but when 98% of their userbase is satisfied - Windows (& mac sometimes) why should they care?
<6> Hey guys, I'm having quite a problem here with Suse 10.1.... I have a wireless card integrated in my laptop with a Prism 2.5 chipset. When I first loaded Suse KnetworkManager found my network and connected to it properly... Now I can't even detect my router... Anyone has a clue?
<9> pm2: well, that's the problem :)
<10> i installed sqlite 2.8 from Yast, and then i just installed sqlite 3.3.5 from source (configure make make install) - everything went through fine, but when i type 'sqlite' in the shell, it is still running 2.8 - how do i re***ign that?
<11> lol sPiN .. makin ye nervous where i put me warm paws was i lol.. ill work on that for ya..
<8> tech9iner: much appreciated
<9> But going the closed source route is not that funny either. Do you really want to pay for most of your drivers, like you have to do for Solaris? After all, why should hardware manufactures give them for free? It's their valuable intellectual property after all...
<10> first of all, how do i track down what typing 'sqlite' in the shell is actually running, so that i can delete it? and then re***ign it to the new one
<12> which sqlite
<11> ;].. niiice.. Shakatura - Midheaven :: http://205.188.215.231:8000
<3> nine: they are selling hardware, they want people to use their hardware it has to work
<3> open drivers is in their best interests if everyone did it, the only thing stopping them is the stupid situation with patents which would mean any one company who opened their driver would be likely to have patent suits from all their competitors
<12> the software is nothing, the hardware is the money product
<1> weswh-: set the $PATH, dont delete anything
<9> benJIman|tov: so they want to sell their hardware. Well if they give out documentation for it and/or open drivers, they sell more.
<11> amaroks is STILL grr.. freezing n trapping keyboard input upon occasion it gets bogged down loading/buffering a stream.. but encouraged here that its shortened at least to max 20 seconds vs 1.3.8 that sometimes would freeze me kybrd out for upto 60 secs.. not goot
<11> old not good.. 1.4 least improved i meant
<6> ANyone can help me out with my Prism 2.5 chipset on my wireless card?... It worked on first boot of Suse 10.1 now... I detect the card with Knetwork Manager but it doesnt detect any network
<13> Thibod: it's a bug in network manager
<13> I had the same problem with my prism2.5, I just bought a new card
<6> ahahaha ok... No KInternet in this release?
<13> the prism2.5 also doesn't do WPA, so it's pretty useless
<13> kwifimanager is available in kdenetwor3-wireless, it might work for you
<6> yeah but,... its my builtin Wireless card -_-
<6> it didnt
<13> err kdenetwork3-wireless that is
<6> he acts like I have no wireless card
<13> usually builtin are really mPCI cards
<6> I've tried it



<6> it's stupid how it worked the very first time I boot.. I had internet access.. and now... I can't
<6> it's like if during the shutdown I had sent him some data that make him go nuts on my card
<13> wtf
<6> did u see what I wrote?
<13> yeah
<6> if Yast2 is configured properly with my card and that in hardware information it shows up that it's installed...
<6> why I can't see my wireless when I try iwconfig or ifconfig?
<13> I suggest using ifplugd not networkmanager
<6> Oh
<13> at least then, you can enter the wireless information in yast, and that network will work
<6> if thats the problem I'm a moron... cuz Ive been seein that since this morning and I thought to myself.. No.. it ain't gonna change nothing
<6> btw sorry my english kinda sux -_-
<6> IT WORKSSSS
<6> IM an idiot
<6> ahahaha
<6> ty man
<10> rohan - how do i "set the $PATH"?
<8> weswh-: what are you trying to do?
<10> i installed sqlite 2.8 from Yast, and then i just installed sqlite 3.3.5 from source (configure make make install) - everything went through fine, but when i type 'sqlite' in the shell, it is still running 2.8 - how do i re***ign that?
<8> there arent many reasons to mess with $path yourself
<8> you should uninstall 2.8
<13> he should get an sqlite rpm of 3.3.5
<8> well yea..
<10> yah - tried to find one for 10.0, but couldn't..
<13> or use a more popular and regularly maintained db like mysql or pgsql
<10> ok, i see...if i run 'sqlite3', it is there. 3.2.2 interestingly, even though the source was 3.3.5, but whatever
<10> frb - yeah...well, i do use postgres for a lot of things. but sqlite has some advantages for certain applications
<1> weswh-: sorry was afk
<14> seems counter productive to have >1 db system
<1> weswh-: export PATH=/bin/foo:$PATH
<1> frb-work: many people need newer versions, maybe ?
<14> rohan: that's not the point
<14> rohan: he said he uses both pg and sqlite on the same system
<1> oh .. so whats wrong ? s'pose app1 reqs pg and app2 reqs sqlite ?
<14> maintaining more than one db, with more than one set of privileges, and slightly different syntaxes is a useless waste of time
<14> it's like running debian and suse on the same network
<14> as an admin, I would _never_ do it, it's stupid, and wasteful
<15> lol
<15> my experience with Suse thus far tells me that I wouldnt want it as a server
<14> then you've only used 10.1
<16> you mean you will never mai tain both mssql and mysql at same time ...
<15> my experience with Suse thus far also tells me I dont really want it as a desktop either
<7> My experience tells me that there's a whole load of stupid people the come and go.
<14> bill-barriere: if it was my choice, yes
<7> s/the/that.
<16> ho you input the choice argument ...
<1> frb-work: well, amarok requires both. what now ? :P
<7> Gumby: Here's an idea - try it as a server before making such allegations?
<1> not require, but use
<14> amarok doesn't require both
<1> Gumby: lol
<15> daPhoenix: I can agree with that. But when a distro ships as messed up as 10.1 has, I dont have much respect for those that decided to ship it.
<14> Gumby: you cannot base any intelligent decisions on suse 10.1
<14> every distro has had it's bad releases
<7> Gumby: Who forces you to use 10.1? 10.0 works like a charm.
<1> Gumby: what is wrong with 10.1 ?
<14> rohan: more than you would ever believe
<15> rohan: what isnt wrong with 10.1?
<1> frb-work: well, start anyway ... i will belive you, i promise
<17> Pretty much everything I've used on it so far *isn't* wrong with it...
<1> Gumby: well, lets start with my question ? :)
<15> rohan: suse's "baby" called yast is extremely horrible
<14> rohan: networkmanager is a joke, yast's package management has issues
<14> Gumby: only the package management
<14> the rest of yast works like a charm
<1> hmm.. use smart ?
<1> actually .. to put it clear - rpm ****s big time. its rpm, not the frontends.
<15> rohan: yes, but thats not the point really. A new user to linux shouldnt have to setup a different package manager other than the default because the default simply doesnt work
<14> no, it's not rom
<15> rohan: no, its not rpm
<14> err rpm, Yast Software Management has Known Bugs
<14> you said you'd believe me, so stfu and believe me


Name:

Comments:

Please enter the result of the sum 63 + 46 (to avoid spam):






Return to #suse
or
Go to some related logs:

#suse
#kde
#css
gtoaster cannot guess build type
#php
#gimp
find symbolic links linux
#perl
airsnort error fetching interface
ubuntu unattended install



Home  |  disclaimer  |  contact  |  submit quotes