@# 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



Comments:

<0> How much do you know about the installer to defer it farhan? :-)
<1> but, it did not even prompt me with this message
<1> sbahra : i used it several times just now
<1> and the documentation
<0> You install Solaris in a production environment (30 boxes or so with it)?
<0> I like the documentation.
<1> ...
<0> The installer is fine, I've seen worse.
<1> ...
<0> farhan, are you an *** or an ***? :-)
<2> sbahra: pkgadd/etc isn't too bad. i prefer it to crufty rpm.
<3> Yeah, pkgadd is nice.
<0> niv_, pkg_add is nicer. :-)
<2> sup aedinius
<3> yo niv



<2> sbahra: is that netbsds?
<0> niv_, FreeBSD's.
<3> netbsd also has a pkg_add
<2> yeah thought so
<0> Yes, it does, but I prefer FreeBSD's package framework (specifically how fetching is handled).
<0> Well, actually, PKG_PATH *is* better.
<0> Yeah, point is...dpkg/pkgsrc/pkg > Solaris packages. :-P
<2> heh aedinius, when i wantto install packages from sun freeware in my homedir on solaris systems that i don't have root on, i wrote an LD_PRELOADable binary that simulates euid(0) and makes chown/chmod return 0
<2> because pkgadd for some reason wants to run as root - even if you want to install underneath your own homedir
<0> niv_, heh
<2> I don't particularly like Linux, but apt-get+aptitude is a slick, easy combination
<2> aptitude was just like, pick the packages I want, bang
<2> it'd auto-download them, which went really quick
<2> i never bothered learning apt-get because of aptitude.. plus like I said I don't use linux much
<2> happened to be running debian somewhere which had it
<0> Same thing with FreeBSD/NetBSD though.
<2> AH
<2> ****, capslock
<2> ah
<2> they have nice ncurses guis that go and fetch everything for you nicely?
<2> and you can list all the available packages through categories and pick them out?
<4> I've used dselect once.
<2> that's what rules about aptitude
<2> dselect is the older one i think alex__
<2> aptitude is similar but better
<0> niv_, no, they don't.
<4> dselect came out before apt
<2> dselect is the mono-ncurses interface and aptitude is the color one
<0> niv_, note in the core package management facilities...
<0> niv_, but you know that you can use sysinstall for this? :-)
<0> niv_, you have lists by category, etc...(shows dependencies and all)
<2> nice
<2> yeah that's just like aptitude
<5> Hi guys
<2> hey
<4> Uh.
<4> dselect had color.
<2> ah.. i didnt remember that
<2> err wait, was it like red?
<2> aptitude is like blue
<6> niv_: what a coincindence, im trying to get rid of mine
<2> heh
<1> arg, someone in my family accidently installed sysprotect on our other computer
<1> and apparently, the makers of this particular program have gotten really good at it and have made it very very difficult to remove
<3> Spyware?
<0> http://www.securitystronghold.com/gates/spyware-adware-solutions/SysProtect_System.exe_solution.htm
<1> yeah, i've been here. this is for an older version
<1> thanks though
<2> probably has a .sys winnt kernel driver that protects it from being removed
<2> you should try booting up with some sysinternals utils and removing the registry entries
<7> How do control the name of your program as seen in 'ps'?
<7> I thought renaming argv[0] would work, but it still appears as the name it has on dis
<7> disk
<3> bynari: Why would you want to do that?
<7> To change the name of kids
<7> I'm not some script kiddie, aedinius. Anything I do is on my own servers
<3> I never said that ...
<3> Anyway, I thought ps got it from argv[0]
<3> Which is from exec()
<7> Perhaps FreeBSD is different. Although setting $0 in Perl changes it



<3> Hm.
<3> Well, in C, you can't change argv[0] from within the program.
<3> afaik.
<7> Oh?
<3> Yeah.
<7> It must be doable somehow if Perl does it
<3> Lies.
<7> :)
<3> LIES I SAY
<8> some os's store the cmd name in kernel space so changing user-space doesn't affect what ps prints
<2> aedi: you can change argv[0] in C
<2> aedi: can't point it somewhere else, but you can overwrite it
<3> Ah.
<2> but only as many characters as are available, of course
<3> Yeah
<2> some OS's are a bit smarter (modern unices) and use setproctitle()
<7> I'll try that. There's even a setprogname, but that doesn't work either
<3> Hm. guess I'm not mdern enough
<3> Let's try that again.
<3> Hm. Guess I'm not modern enough.
<2> and on some even if you change argv[0] it will show up in ps list as (original_name): changed_name
<2> or something similar
<7> With perl it'll show up as new_name (Perl ver)
<2> if you use setproctitle(), make sure you don't p*** it a user-defined input value because it is a format-string function like printf
<7> setproctitle is useful but it only sets text after the progname
<2> so instead of setproctitle(input); do setproctitle("%s", input);
<2> oh
<7> :)
<2> yeah, just strcpy(argv[0], "newtext"); then
<2> and make sure strlen("newtext") <= strlen("argv[0]");
<2> err
<2> *strlen(argv[0])
<2> heh
<7> Still not working even with the new name <= strlen(argv[0]) :/
<7> I'll try on my linux laptop
<2> does it segfault or something?
<2> maybe the kernel is putting argv[] strings in a non-writable memory page
<9> isn't argv on the stack?
<2> jiffe: the pointers are.. i don't know if the actual strings are
<9> I would figure the process queue would hold the binary title
<7> Doesn't segfault, just doesn't set it at all
<2> they can point anywhere, when you execve() something the kernel sets up the process image
<2> bynari: interesting.. well, i havent done it since like 99-2000
<2> but back then it was prevalent
<7> Doesn't work on linux either
<2> damn.. i know for sure it _did_ work in linux
<2> like 2.0 or even 2.2
<2> maybe 2.4
<7> Hm :/
<2> looks like most un*ces got smart and started storing an extra copy of the parameters (argv[]) in kernel memory, for /bin/ps to read
<7> Could be a security measure
<7> Oh well.
<2> yeah
<7> I can always hack ps.c
<2> most likely
<2> because we used to do that to hide processes we were running
<7> I'm handing in my notice for my current job. Company is a bit dodgy and didn't pay the last sysadmin his final wages. :)
<2> like i'd add strcpy(argv[0], "vi"); to a program
<7> So I need to make sure I retain access to the servers in case they reset the p***words and don't pay me
<2> lol
<2> so you putting something in to hold over their heads?
<7> They'll make me work up until the final day then backstab me
<7> Yeah. Unfortunately I'll have to
<7> Or I'll be screwed. :)
<2> bynari
<2> don't hand in your notice then
<2> just quit after you get paid that day
<7> Could do, but then I'll be the bad guy
<2> after you deposit the check
<2> well
<7> Also
<2> you already know what theyre gonna do
<7> They owe me holiday pay. They won't give me that u nless i'm leaving
<7> Also they might well be nice and just pay me


Name:

Comments:

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






Return to #c
or
Go to some related logs:

#linuxhelp
#firebird
#beginner
#sex
cadusd usdcad
#politics
#gamedev
#beginner
#computers
Thomas Remvik Aasen



Home  |  disclaimer  |  contact  |  submit quotes