| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11
Comments:
<0> doug8429, yeah temporary nic is sometimes the way to go too
<1> someone who nows how i set my charset to iso-8859-15 in Screen ?
<2> orc_orc i dont find a package for amd64 in the nvu page... :(
<3> zkorpio: the Oracle says the fedora folks are not yet aware of nvu -- but that Suse and cAos are in source format: http://pastebin.ca/123715
<3> zkorpio: this means a trip to the builder for you -- http://www.rpm.org/hintskinks/buildtree/ has help for you in this venture
<4> orc_orc: so, we're dis***embling a rack today, which brings me to ask "is there a better sight than a PFY with one hand on the bus-bar and one hand on a metal shelf?
<5> [sudoers: "username ALL = /bin/su" ] - what would be wrong?
<3> Evolution: a female PFY lathered in vegetable oil, stripped to te waist, with one hand on the bus-bar and one hand on a metal shelf?
<4> lehel: what VPS are you using?
<6> whats a 'PFY' please?
<4> lehel: by default, anyone can run su.
<2> orc_orc sorry i am some newbie but, can i install a src.rpm from suse or fedora in my centos?
<3> boudiccas: first google hit
<0> lehel, man sudoers probably have to define your username first, I don't do much sudoer customization
<3> zkorpio: it is unfortunate you are a newbie, but the only way to solve that is to study -- the link I pointed you do discuses building a binary from a source RPM as an end user
<0> Evolution, he wants to allow anyone to run su as root....might as well just give them full sudoer capability... :)
<4> so_: yeah. I'm a little terrified by what he's doing....
<3> lehel: that is not good syntax -- did you use visudo?
<2> yes orc_orc thank you i go to read right now
<3> Evolution: hand him a fully loaded BFG-9000, and make sure the safety is off
<5> Evolution: no VPS/ orc_orc: "visudo" ?
<3> lehel: yes
<4> orc_orc: it's loaded, and equipped with a scope ranged for feet.
<5> so_: i'm reading the man sudoers
<4> lehel: visudo ensures that you don't **** up editing /etc/sudoers
<5> orc_orc: no
<5> i see
<7> i dont use visudo for automation purposes
<7> havent ran into any problems
<5> Evolution: what should i f/u with adding a user to be able to the "su" command?
<8> orc_orc: silly orc. There is no safety on a BFG-9000!
<3> Zathrus: ahh -- I must have a prototype before they stabilized the design
<8> lehel: yes, visudo -- you know, just like the /etc/sudoers file says at the very top.
<5> ok
<5> sure..
<5> bye
<9> Jinzora requires Iconv. I cannot see a package with yum, anyone know if there is a rpm of this?
<3> SoulOrb: glibc-common has: /usr/bin/iconv -- what are you looking for that varies by on echaracter
<9> Oh, Maybe that will do. I thought I needed a separate RPM. I am still learning the structure of Centos and what is included. I was also having a problem with GD, on Gentoo it is a separate package.
<9> larts? :-)
<3> SoulOrb: an instructional tool -- google will elucidate
<9> Well more simply, no worries, I will eventually figure it out.
<9> Just thought I would hang outhere a while, since I kind of like Centos and trying it on a few boxes.
<9> I am impressed with the centos install in a Epia. Works better than any other distro so far, including epios.
<4> wtf is an epia?
<3> SoulOrb: we are sorry centos is boring, but then, that is its mandate ;)
<10> It's like a VIA
<10> Very like a VIA
<10> So like a VIA in fact it /is/ a VIA
<11> I _like_ boring server operating systems.
<3> longword: heh
<9> Yes, the more boring the better. I log into my web servers so little, I forget the p***words half the time.
<9> One Via of many...
<12> hi
<12> just installed Centos on an Alpha DS20e but I could not make software raid during install (the option was missing)
<12> any ideas?
<3> riker_mini: using the 4.2 beta spin for alpha, or some ohter?
<12> if I use fdisk, the standard fiesystem tags are missing (I dont' have 83 - raid autodetect)
<12> 4.3 final it says
<3> hmmm
<12> which is odd, coz I only see 4.2 Final at cenos.org :)
<3> thus my question
<12> but /etc/redhat-release reads CentOS release 4.3 (Final)
<12> hmm..checked cenos.org again - on the main page it says the Alpha version is 4.2 but if you go to the download section, it says 4.3
<3> riker_mini: understood -- please file a bug, rather tahn put content in IRC which will be forgotten
<12> k
<3> ty
<13> anyone running x86_64 that can tell me of any benefits over i386? Really the only reason I can see using the x86_64 right now is that it will allow me to have 64bit vmware sessions for testing but is it worth the headache
<8> Nacho|w: you can have 64 bit VMWare sessions w/ a 32-bit install.
<13> ...
<13> really?
<10> vmware does CPU emulation now?
<4> yep
<8> Nacho|w: really.
<4> longword: no
<13> reaaaaallllly?
<13> didn't even look into that much
<13> I've had some quirks with x86_64 and not sure if it's worth the headaches
<4> you simply need 64bit hardware, onto which you install 32bit centos, and host 64bit virtual machines.
<4> it's freakish, but it works very well
<3> Evolution: will it emulate an Alpha, so I may diagnose riker_mini's issue more easily?
<8> Nacho|w: the advantages of x86_64 are a _much_ bigger memory size allowed w/o (as much of a) speed hit, and slightly improved performance in theory.
<10> What you definitely get in x86_64 mode is double the number of registers as well as double the size so code should get an across the board speed bump
<10> s/bump/boost/
<13> right now the box only has 2gb in it
<8> longword: yes, but sadly too much stuff is compiled w/o knowledge of the extra registers.
<13> might take it to 4
<13> Zathrus: yeah I'm seeing that
<10> Zath: Doesn't gcc take advantage by default when targetting x86_64?
<13> I've also got package issues with openssl where there are conflicts with i386 and x64_86 packages
<10> It's not as if there are any x86_64 arch processors without the additional register set
<8> longword: I should hope so, but anything compiled for i386 instead of for x86_64 won't know about the registers.
<3> smooge: Pastor Smooge, I mean, after marrying dogs and cats in public, greetings
<13> another odd issue is with lvm
<13> I've got 1.75tb I'm using lvm with for iscsi and at boot the volumes aren't active
<13> I have to manually do vgchange -ay and then all is well
<8> longword: really there's a vast amount of software out there that could get a decent speed boost by compiling in 32-bit x86_64 mode; but that's not how things are done here. And, frankly, I haven't seen much that indicates significant real world speed improvements.
<10> Does openssl include hand-rolled x86_64 asm yet?
<10> I know that's a _big_ win on most ciphers
<13> from what I'm seeing I think I'll just stick with 32bit since the main role of this box is iscsi storage and 64bit isn't going to make that any faster
<8> yah, should be. I know it's compiled in 64-bit mode -- one of the few packages where it's significant.
<14> is it possible to have virtual interfaces on a bonded (bond0) interface ?
<10> Zath: Building openssl C code in 64-bit mode barely approaches the speed of the hand-crafted 32-bit ASM
<8> longword: the agreement was with your conjecture; not with whether or not it does so. That was unclear.
<10> I've seen the numbers on test patches from 3rd parties
<10> With good code I tested Opterons running up to three times faster on some ciphers than the fastest Xeon we had
<13> that's the key... good code
<13> and in the real world it's sad to say that the 64bit streamlining is a bit lacking
<10> In the case of OpenSSL it's just making a level playing field
<10> The i686 code has long been hand-crafted to within an inch of perfection
<12> orc_orc: solved it, thanks for bothering!
<10> The other level playing field is compiled C code vs. compiled C code
<15> orc_orc, I say once again that dogs and cats marrying is ok. now cats and mice.. that I have a problem with
<3> riker_mini: still -- please doco your solution in the tracker for those who follow you
<3> smooge: ahh
<10> I would have thought it fairly easy for gcc to make good use of the enlarged register file to enhance x86_64 object code
<12> orc_orc: it was a disklabel problem. there was VMS on the machine previously so it had BSD OSF/1 disklabel - that was the cause of all problems
<10> But it's not something I've delved into much myself
<12> orc_orc: so it wasn't actually a bug, but just something unexpected
<3> longword: _nothing_ in a project spanning all arches, and as many years as gcc/egcs/gcc does is going to be easy ;)
<3> riker_mini: ok -- just being cautions
<12> orc_orc: the installer used disk partiton types allowed by OSF/1, which is not much :)
<3> riker_mini: sensible, as it has to know how to transition into them
<12> orc_orc: yea. but it was my first time install on Alpha :) parted solved the problem (mklabel msdos)
<10> orc: But on the flip side, gcc has been running on CPUs with decently sized register files for a long time
<10> And making use of basic features like that isn't terribly different from one CPU arch to another
<2> orc_orc finally i found this: nvu-1.0-6mdv2007.0.src.rpm and when i tried rpmbuild --rebuild --clean nvu-1.0-6mdv2007.0.src.rpm i get: warning: user couriousous does not exist - using root
<2> error: line 20: Tag takes single token only: Release: %mkrel 6
<4> zkorpio: the first message is a warning from rpm saying that the user who made the package doesn't exist on your system. it's a cpio holdover I believe. nothing at all to worry about.
<4> the second means you need to edit the release line of the spec file to correct it.
<3> Evolution: tar, actually
<2> tks Evolution and where do i find the spec file?
<2> i see that i have a directory in /usr/src/redhat/SPECS
<3> zkorpio: on the RPM website is a training piece by GuruLabs which you will want to work through if you build on an ongoing basis
<3> zkorpio: did you set up the end user build environment as recommended, or are you building as root? - it affects the answer (btw: building as root is .... dirty)
<4> orc_orc: ah, tar.. right.
<8> dirty is fun!
<2> orc_orc i do it like rooot
<2> root
<3> Zathrus: in the proper context, as with the Olsten twins and a 55 gal drum of chocolate pudding in a child's pool
<3> zkorpio: bad habits are hard to break, -- it is your systen to mune as you wish -- /usr/src/redhat/SPECS should have the file you seek when you unpack the file this: rpm -U nvu-xxx.src.rpm
<16> ohhh building as root you hope that some broken script doesn't rm -rf / your box, highly recommended as a learning experience
<2> yes orc_orc i know that is stupid use root for this things but my time today is limited
<16> I want a pretty pink pony with a long braided mane
<17> donavan your pony: http://tinyurl.com/ms4yy
Return to
#centos
or
Go to some related
logs:
#kde
linux, ubuntu dc++ hub
#linux
ssh command mount f xbox ubuntu
#osdev
dapper to edgy xwindows
you must be member of group users
#gentoo
spcaXXX driver
__libc_csu_init glxinfo
|
|