IRC Networks
Irc Logs Stats
Start date: 2007-09-27 02:48:27
Last update: 2008-04-02 18:00:08
Channels: 41
Logged Lines: 6229042
Size: 1809.13 MB
Powered by
Channel Info
Network: freenodeChannel: #gentoo |
Search in www.irclog.org
Log from #gentoo at freenode 2006-05-25
Pages: < Prev
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
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Next >
[12:10]<ma-pu>essid is the 'name' of an access point
[12:11]<meskd>huh wtf where all the ladys ?
[12:11]<meskd>;}
[12:11]<svjzddjzz>The network name like 'Internet Cafe'
[12:11]<ma-pu>yes.
[12:11]<svjzddjzz>k
[12:11]<ma-pu>http://www.google.co.nz/url?sa=X&start=2&oi=define&q=http://en.wikipedia.org/wiki/ESSID
[12:11]<jdn_nnlxnz>Goodmorning
[12:11]<ma-pu>In Wi-Fi Wireless LAN computer networking, a service set identifier (SSID) is a code attached to all packets on a wireless network to identify each packet as part of that network. The code consists of a maximum of 32 alphanumeric characters.
[12:11]<wusxy>is there anyway to defrag my / partition? after over a year of work, it's really gotten slow and reads/writes alot to the hd =/
[12:12]<ma-pu>afaik, ext3 doesn't need defragging
[12:12]<ma-pu>it's an 'efficient' file system
[12:12]<lzvzyc_dzw>nanobanshee, did you change any Xdefaults?
[12:12]<vj2djjw>i wonder how much longer itll take for kde to emerge
[12:12]<lzvzyc_dzw>or just $TERM
[12:12]<wusxy>dj-fu: that's true but up to a point.. and a year of emerging, filling to 99.9% and emptying, etc... it does have its effects
[12:13]<ma-pu>xushi, probably more related to hardware failure than filesystem I'd say
[12:13]<ma-pu>bad blocks etc
[12:13]<ma-pu>may wanna 'fsck' the drive?
[12:13]<ma-pu>in single user mode of course
[12:14]<wusxy>dj-fu: the system does fsck the partition/drive at boot every 20 times with no problems. I could do it manually if that's different
[12:14]<grgj2rgsxnn>patrik_mrx: just $TERM. shuts off color in most things. some apps stop working with vt100-m. but work with no color using vt100.
[12:14]<ma-pu>naw, it's not different
[12:14]<wusxy>ugh.. anything other than /etc, .config, and /~ that needs to be backed up? =/
[12:14]<lzvzyc_dzw>not for me, i tried it out in gnome-terminal to. Not working there either
[12:15]<ma-pu>xushi, might wanna backup 'world'?
[12:15]<lsd`>xushi: /usr/portage if you want to avoid the lenghty sync+download
[12:15]<ma-pu>or make some quickpkg's of your monolithic stuff
[12:15]<lzvzyc_dzw>nanobanshee, wonder what you have that i don't to make it workd
[12:15]<lzvzyc_dzw>*work
[12:15]<wusxy>thanks
[12:16]<grgj2rgsxnn>patrik_mrx: how are setting $TERM ?
[12:16]<lzvzyc_dzw>export TERM=vt100-m
[12:16]<lzvzyc_dzw>have it in my .bashrc file
[12:17]<lzvzyc_dzw>i dont't think it's worng to have that in my .bashrc file...
[12:17]<grgj2rgsxnn>patrik_mrx: are you restarting bash ?
[12:17]<lzvzyc_dzw>it should still work
[12:18]<grgj2rgsxnn>patrik_mrx: try declare -x TERM=vt100-m
[12:18]<svyffugcgjwg>anyone know why important apps, libraries, etc have so many patches in the ebuild (why aren't they moved upstream for the next version)?
[12:18]<lzvzyc_dzw>starting new aterm for testing so, yes, guess so
[12:19]<lzvzyc_dzw>nanobanshee, do you mean bash -x TERM=vt100?
[12:19]<lsd`>stillunknown: I'm sure a lot of them do get merged upstream but something has to be done in the mean time
[12:19]<grgj2rgsxnn>patrik_mrx: nope. declare -x TERM=vt100-m
[12:19]<grgj2rgsxnn>patrik_mrx: then hit ls. should be b+w.
[12:20]<lzvzyc_dzw>nanobanshee, don't understand, what program is suppose to get -x TERM=vt100-m?
[12:20]<lzvzyc_dzw>just writing it is wrong
[12:20]<grgj2rgsxnn>patrik_mrx: huh? type 'declare -x TERM=vt100-m' into the aterm and hit the enter key.
[12:21]<grgj2rgsxnn>without the quotes.
[12:21]<lzvzyc_dzw>ah
[12:21]<grgj2rgsxnn>patrik_mrx: and add it to the end of your .bashrc
[12:21]<grgj2rgsxnn>patrik_mrx: echo 'declare -x TERM=vt100-m' >> ~/.bashrc
[12:21]<lzvzyc_dzw>declare -x TERM=vt100-m;ls --color is still in color
[12:22]<grgj2rgsxnn>patrik_mrx: hmm. so it is. it seems that applications can choose to respect terminfo or not.
[12:23]<lzvzyc_dzw>that's bad for me
[12:23]<grgj2rgsxnn>patrik_mrx: yup. now you need a way to force strict terminfo compliance ...
[12:23]<grgj2rgsxnn>patrik_mrx: which I have no clue how to do.
[12:23]<lzvzyc_dzw>can't find a strict b/w term through google...
[12:24]<2frrarrn>patrik_mrx: function aterm { ARGS=( "--background ${1}" "--foreground ${2}" $(for ((i=0;i<=15;i++)); do echo -n "--color${i} ${2} "; done) ); /usr/bin/aterm ${ARGS[@]}; }; aterm black white
[12:24]<2frrarrn>patrik_mrx: that even works for me :P
[12:25]<lzvzyc_dzw>blackace, you redefine all the colors?
[12:25]<2frrarrn>patrik_mrx: yes
[12:25]<2frrarrn>patrik_mrx: that's the best suggestion I can make :)
[12:25]<lzvzyc_dzw>that's one way of doing it =)
[12:25]<lzvzyc_dzw>perhaps i should backup the termcolors file before executing it...
[12:26]<2frrarrn>patrik_mrx: they're just command line options
[12:26]<lzvzyc_dzw>so it is not written into file?
[12:26]<2frrarrn>patrik_mrx: you could do it in a resource file too
[12:26]<2frrarrn>patrik_mrx: not that way
[12:27]<zryfc>modprobe fglrx -> "FATAL: Error inserting fglrx (/lib/modules/2.6.16-gentoo-r7/video/fglrx.ko): Invalid module format"... last line of dmesg -> "fglrx: disagrees about version of symbol struct_module"... help?
[12:27]<lzvzyc_dzw>blackace, thx alot, works like a charm
[12:27]<ma-pu>railk, make sure you are actually running the kernel you compiled fglrx against
[12:27]<ma-pu>(you currently are not ;P)
[12:28]<zryfc>... weird :P
[12:28]<ma-pu>update grub/lilo etc
[12:28]<zryfc>huh?
[12:28]<qzgvjuzysa>for the last 3 months i've been unable to compile glibc: http://pastebin.com/736725
[12:28]<qzgvjuzysa>[ebuild U ] sys-libs/glibc-2.3.6-r3 [2.3.5-r2] -build +erandom -glibc-compat20 -glibc-omitfp +hardened -linuxthreads-tls (-multilib) +nls +nptl +nptlonly -pic -profile (-selinux) -userlocales 0 kB
[12:29]<ma-pu>o0o. 2.6.16.
[12:31]<2frrarrn>patrik_mrx: this will let it pass through other options: function aterm { ARGS=( "--background ${1}" "--foreground ${2}" $(for ((i=0;i<=15;i++)); do echo -n "--color${i} ${2} "; done) ); shift; shift; /usr/bin/aterm ${ARGS[@]} ${@}; }
[12:33]<grgj2rgsxnn>blackace: stop dude. just set the aterm*color0 through 15 resources.
[12:33]<vj2djjw>ive been emerging kde for the last six hours. id like to get to sleep by 5 am though. is there a way to pause emerge?
[12:33]<2frrarrn>nanobanshee: I didn't see you chiming in 10 minutes ago, lose the attitude.
[12:34]<zryfc>dj-fu: i updated grub, what else?
[12:34]<lzvzyc_dzw>blackace, i found out that it was bad to put your function in my .bashrc file
[12:34]<ma-pu>railk, that's all you should need to do, make sure grub is pointing at the correct kernel
[12:34]<ma-pu>then reboot
[12:34]<vj2djjw>lol i cant sleep because my laptops on my bed doing this while its plugged in one one side of the room and the cat5 is plugged into the router on the other side of my room
[12:34]<2frrarrn>patrik_mrx: why?
[12:34]<vj2djjw>so ive got a laptop sitting on my bed that cant be moved while its doing this
[12:34]<grgj2rgsxnn>blackace: I didn't think of it 10 minutes ago. but your one-liners are starting to hurt my brain :P
[12:34]<vj2djjw>itd be cool if there were a way to pause emerge and sleep though
[12:35]<2frrarrn>nanobanshee: well, I've never needed to set a resource in my life, so if you know how, why don't you tell him? :)
[12:35]<grgj2rgsxnn>oh wow. I didn't know that was the issue.
[12:35]<ma-pu>tobmoox, uh, ctrl+z?
[12:35]<lzvzyc_dzw>it starts up more and more aterms
[12:35]<vj2djjw>doesnt ctrl+z just put it in the background?
[12:35]<ma-pu>no, ctrl+z pauses. it
[12:36]<2frrarrn>patrik_mrx: you left out the /usr/bin/ ?
[12:36]<ma-pu>ctrl+z, bg - that puts it into the bg.
