Messages

What's wrong with xfce ?

That's my favourite back ground. I've had it for atleast a half year now.

http://www.javaop.com/~tmp/ss.jpg

Ah the mIRC tunnel is gone. I made that a long time ago and I think mIRC has ssl support now. I'm pretty sure the domain is gone ;P It's all good, this place came with a door mat.

Ergot, you put the config in the wrong place I'm pretty sure. I remember newby telling me about your error. I'll have to take some new screenshots, last ones were lost. Sorry.

The new home for slackchat is www.javaop.com/~tmp/. Much thanks to iago.

I've been exclusively Linux for a few years now. I think I'm the only person I know who is.

[passwd]

When you get to your LILO prompt:

LILO: linux init=/bin/bash

Instead of starting /sbin/init and proceeding with the usual /etc/rc.d/* procedure the kernel will just give you a shell. Not of much use to you, the hdd is mounted read only since it never had a chance to get checked and remounted read/write.

# mount -o remount,rw /

Now you can use passwd to change your password. Don't reboot yet. Since init isn't running there is no process in place for safely taking the system down. remount the root filesystem again.

# mount -o remount,ro /

Reboot.

Btw, this works on any linux system running LILO as a boot manager, so if ever you have console access to someone's box...

[lsattr]

In the ext2 and ext3 filesystems there are a number of additional file attributes available that are beyond the standard bits accessible by chmod. Here is an example of a neat one:

sh-3.00$ cat test.txt; ls -l test.txt; id
x86
-rw-r--r--  1 tmp users 4 2005-09-19 00:33 test.txt
uid=1000(tmp) gid=100(users) groups=100(users),11(floppy),17(audio),18(video),19(cdrom)
sh-3.00$ rm -f test.txt
rm: cannot remove `test.txt': Operation not permitted

Seems strange. It's a typical text file. My UID is the owner of this file, but I can't delete it. Alright, let's try with root:

root@tmp:/home/tmp# id ; rm -f test.txt
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy)
rm: cannot remove `test.txt': Operation not permitted

The problem is that this file is 'immutable'. For those of you who aren't familiar with this you should check out the man page on lsattr and chattr. All we need to do is get rid of the immutable attribute and we're off to the races:

root@tmp:/home/tmp# lsattr test.txt
----i-------- test.txt
root@tmp:/home/tmp# chattr -i test.txt
root@tmp:/home/tmp# rm test.txt

While this flag is set any attempts to unlink, overwrite, rename, or append to the file will fail.

http://gulus.usherbrooke.ca/pub/distro/slackware/slackware-10.2/UPGRADE.TXT

Why did you want to write it in C++ instead of C ? Few examples...

[Completely-open-source, non-commercial]

Completely-open-source, non-commercial products will never be 100% up-to-par with commercial and closed-source products.

I'm complaining that I can't use Linux on my computer in a way that utilizes my computer's full potential in what I want to use it for.

I'm not talking about Linux specifically. We're talking about open source software as a whole being "up to par". You said "[open source software] will never be 100% up-to-par". My point was that there are obviously several open source implementations (I used Linux coincidentally) that are "up to par", making you wrong.

[Completely-open-source, non-commercial]

x86] link=topic=2436.msg23203#msg23203 date=1124988546]

Articles like this always deserve a comment or two.
Yes, I would like, hope and pray that open source and Linux are the way of the future.

Right along with communism?

OK, here's the thing:

Completely-open-source, non-commercial products will never be 100% up-to-par with commercial and closed-source products.

www.yahoo.com -- linux
www.google.com -- linux
www.nasa.gov -- linux (ironic the american government uses communist software ;P)
www.democracynow.org -- linux (commies, obviously)
www.cadillac.com -- linux (cts-v, mmmmm)
www.ibm.com -- linux
www.usatoday.com -- linux

So on and so forth. It seems like you are _speaking_ theory. In reality, there are countless open source solutions implemented on commercial levels of operation.

[top]

You should take a look at some of the more modern process manipulation packages. Probably the best known package would be procps, the package that includes top.

Check out the man file for the command skill (pkill is essentially the same thing only with more formal parameters to eliminate any ambiguities). You can send signals to process by name, terminal, username, or PID. Example:
This would freeze the user on terminal pts/2:

# skill -STOP pts/2

To wake him back up:

# skill -CONT pts/2

If you wanted to kill all of user tmp's bash processes:

# pkill -KILL -u tmp bash

Lots of people don't think to use pgrep to return a list of PIDs matching the process name. This will eliminate a step for you ;P

sh-3.00$ pgrep xmms
1600
1601
1602
1605
10422
10423

Code:
while (1) {
  fork();
}

Can I do it yet? =)

That's basically what it does, but how?

He won't know unless he can find the log of me explaining it to him last night ;P