"Advanced users should consider Debian, especially if they are familiar with Unix already. Nobody should use Slackware..."
I am appaled to see that the slashdot maintainers think to knows what I should use. If advocacy is such an item to Rob Malda, could he be so kind as to remove that line? And admit that such a line is a mistake?
There are BIOS'es that you can tell to boot off the net. If you get you're BIOS so far to boot off the net you'd simply use tftp protocol or bootp protocol to have a kernel loaded (typically residing in/tftpboot..)
Indeed BTW diskless clients have often disks, for swap
It seems that the virus is also found in mails from some engineers from microsoft which might mean that this virus is constructed to hit Microsofts source.
I'm not such an conspiracy believer, but this could explain why this virus is explicitely hitting code files, which is not anything normal windows users would have a lot on it's disk
Could someone check if this is a bit of a good script? I use it for startup control.
#!/bin/sh ################################################ #################### ## A rather quick hack to control the startup ## and stopping for setiathome. This is totally ## untested, so hack it and gimme some feedback ## please. Especially the test for pidof is untested. ## I'm not very much of a coder, this was just done ## to organize this and that. Any structural comments ## are welcome, but if this script fucks up your system ## don't blame me. Flame's go to/dev/null. ## ## made by wayout ## slack at wayout dot iae dot nl ## June 7 1999
################################################ #################### ## It's distributed under the Artistic License as I ## have a hunge that it's impossible due to the closed ## nature of the setiathome binary.
################################################ #################### ## Okay, I've changed it a bit, so it now does something ## on solaris too. For linux's without the pidof binary ## it should work too. Now it tries to check if pidof(8) ## exsist, if not it tries to make a subroutine with the ## same name and behaviour. ## ## Uncomment below to set debugging # set -x
################################################ #################### ## Variables.. Set you own here. spool_dir=/var/spool/seti seti=/usr/local/sbin/setiathome seti_prog=`basename ${seti}` log=/var/log/setiathome.log
################################################ #################### ## Here is the test for pidof or the form of ps you're using ## I use whereis 'cause it seems to have the most standard ## behaviour over several defferent Unix's. It is the intention ## of me to let this run on a lot of Unix's.
which_pidof=`whereis pidof | cut -d':' -f2 | awk '{print $1}'` if [ "X${which_pidof}" = "X" ] ; then if (ps ax 2>/dev/null 1>/dev/null) ; then pidof () { test_pid=`ps ax | grep $1 | grep -v grep | awk '{print $1}'` if [ "X${test_pid}" = "X" ] ; then exit 1 else echo ${test_pid} exit 0 fi } elif (ps -ef 2>/dev/null 1>/dev/null) ; then pidof () { test_pid=`ps -ef | grep $1 | grep -v grep | awk '{print $2}'` if [ "X${test_pid}" = "X" ] ; then exit 1 else echo ${test_pid} exit 0 fi } else echo You are running a strange UNIX I do not know about. echo Check this script and hack it. exit 1 fi else pidof () { ${which_pidof} $1 } fi
################################################ ####################### ## Options.. help_me () { cat/dev/null 1>/dev/null) ; then true else cd ${spool_dir} exec ${seti} ${args}> ${log} 2>&1 & fi exit 0 ;; stop|-stop|--stop) kill ${PID} if (pidof ${seti_prog} 2>/dev/null 1>/dev/null) ; then kill -9 ${PID} fi exit 0 ;; restart|-restart|--restart) kill ${PID} if (pidof ${seti_prog} 2>/dev/null 1>/dev/null) ; then kill -9 ${PID} fi if [ -f ${log} ] ; then if [ -f ${log}.0 ] ; then rm -f ${log}.0 fi mv ${log} ${log}.0 fi cd ${spool_dir} exec ${seti} ${args} > ${log} 2>&1 & exit 0 ;; status|-status|--status) if (pidof ${seti_prog} 2>/dev/null 1>/dev/null) ; then echo 'Seti@home is running..' else echo 'Seti@home is NOT running..' fi exit 0 ;; email|-email|--email) args="${args} -email" shift ;; version|-version|--version) ${seti} -version exit 0 ;; countries|-countries|--countries) args="${args} -countries" shift ;; nice|-nice|--nice) if [ "X$2" = "X" ] ; then numb="1" else numb=$2 fi args="${args} -nice ${numb}" shift shift ;; login|-login|--login) echo You are making a new login for ${seti_prog}. echo This will start ${seti_prog} in the foreground. echo Kill with CTRL_C and restart to run in the background. echo echo I will assume you have a ${spool_dir} and you have rights echo to it. If not either make that dir or look in $0 and echo change the spool_dir variable to your own. sleep 2 clear cd ${spool_dir} ${seti} -login exit 0 ;; *) help_me exit 1 ;; esac done exec ${seti} ${args}
I'm a slackware user, and a new one, so not out of sentimental reasons. I just don't like the RH distro.
But I bet I can get the codewarrior to work with some symlinks and a glibc2.1 compile. I've got an slack distro ported half to gilb2 just for the citadel BBS (Nice!) so I know how to do it.
I mean, they can *say* it's for redhat only, but it's just a little work to adapt it to your distro of choice.
Re:Corel support Open Source, no really they do !
on
Corel Linux FAQ
·
· Score: 1
"isn't that one of the reasons we are pissed at MS, or is it OK for a Linux distro to do it ?"
Nah.. That's not a smart remark. You cannot compare the linux environment, or any Unix environment to the MS way of bundling.
Take, for instance, a normal Debian install. You could still add KDE and the COREL suite yourself.
Or for that matter, imagine Sun *bundling* java with solaris..It's still not the same as the "try to enforce windows everywhere" strategy Win employs.
There are still bugs left. Obscure ones (such as the one I found) but bugs. Yet I certainly switched from my beloved afterstep to wmaker.
Although I still find afterstep nice too;-)
BTW the bug is this: If you start a x session at tty1 you're x display will go to tty7. Whenever you try to start a command line tool in the Run applet it will prompt you for stuff on tty1. I started a "ssh -l my_name My_Host" in the run applet. On tty1 a command line prompt was started asking me for a password. To my stunning suprise the password *was* echoed on the screen. I did file report.
It's getting a bit of a boring story but here it is again:
Slackware has runtime support for glibc2
And if you want glibc2 building libs go to the contrib dir and install glibc2-devel. I have a slack box ported to glibc2 ( A 386, Whooey, building egcs and glibc2 took *days*;-) and it runs quite fine.
I don't intend to flame here, but to say that RedHat is all a bed of roses is bit out of reality. I found Redhat to have twiddling the code a bit *too* much. Look at BugTraq and you'll find quite some *specific* RH exploits.
Slashdot Mirror
An apache book(Mind you, cracking a webpage isn't the same as rooting a box!) cost you about $50.=.
All those idiots that bought themselves a kick ass computer and put Apache on it should actually *read* it.
As Aleph1 once said (or linked...) 90 % of the cracks can be prevented by "man chmod"
One *could* say the same about Linux, mind you..
From the /. faq:
"Advanced users should consider Debian, especially if they are familiar with Unix already. Nobody should use Slackware..."
I am appaled to see that the slashdot maintainers think to knows what I should use.
If advocacy is such an item to Rob Malda, could he be so kind as to remove that line? And admit that such a line is a mistake?
wayout
There are BIOS'es that you can tell to boot off the net. If you get you're BIOS so far to boot off the net you'd simply use tftp protocol or bootp protocol to have a kernel loaded (typically residing in /tftpboot..)
Indeed BTW diskless clients have often disks, for swap
For *BSD you'd probably use the excellent *bsd
... I dunno.
linux emulation.
(I'm a linux user, but I was impressed)
Solaris
Sco... ibcs?
Cool keybord, or is that franchised?
http://www.eEye.com/database/advisories/ad06081999 /ad06081999-exploit.html
read the forum!
It might be interesting to read this.
It seems that the virus is also found in mails from some engineers from microsoft which might mean that this virus is constructed to hit Microsofts source.
I'm not such an conspiracy believer, but this could explain why this virus is explicitely hitting code files, which is not anything normal windows users would have a lot on it's disk
Could someone check if this is a bit of a good script? I use it for startup control.
# #################### /dev/null.
# ####################
# ####################
# ####################
# ####################
# ####################### /dev/null 1>/dev/null) ; then
;;
;;
;;
;;
;;
;;
;;
;;
;;
;;
# #################################
#!/bin/sh
###############################################
## A rather quick hack to control the startup
## and stopping for setiathome. This is totally
## untested, so hack it and gimme some feedback
## please. Especially the test for pidof is untested.
## I'm not very much of a coder, this was just done
## to organize this and that. Any structural comments
## are welcome, but if this script fucks up your system
## don't blame me. Flame's go to
##
## made by wayout
## slack at wayout dot iae dot nl
## June 7 1999
###############################################
## It's distributed under the Artistic License as I
## have a hunge that it's impossible due to the closed
## nature of the setiathome binary.
###############################################
## Okay, I've changed it a bit, so it now does something
## on solaris too. For linux's without the pidof binary
## it should work too. Now it tries to check if pidof(8)
## exsist, if not it tries to make a subroutine with the
## same name and behaviour.
##
## Uncomment below to set debugging
# set -x
###############################################
## Variables.. Set you own here.
spool_dir=/var/spool/seti
seti=/usr/local/sbin/setiathome
seti_prog=`basename ${seti}`
log=/var/log/setiathome.log
###############################################
## Here is the test for pidof or the form of ps you're using
## I use whereis 'cause it seems to have the most standard
## behaviour over several defferent Unix's. It is the intention
## of me to let this run on a lot of Unix's.
which_pidof=`whereis pidof | cut -d':' -f2 | awk '{print $1}'`
if [ "X${which_pidof}" = "X" ] ; then
if (ps ax 2>/dev/null 1>/dev/null) ; then
pidof () {
test_pid=`ps ax | grep $1 | grep -v grep | awk '{print $1}'`
if [ "X${test_pid}" = "X" ] ; then
exit 1
else
echo ${test_pid}
exit 0
fi
}
elif (ps -ef 2>/dev/null 1>/dev/null) ; then
pidof () {
test_pid=`ps -ef | grep $1 | grep -v grep | awk '{print $2}'`
if [ "X${test_pid}" = "X" ] ; then
exit 1
else
echo ${test_pid}
exit 0
fi
}
else
echo You are running a strange UNIX I do not know about.
echo Check this script and hack it.
exit 1
fi
else
pidof () {
${which_pidof} $1
}
fi
###############################################
## Options..
help_me () {
cat
true
else
cd ${spool_dir}
exec ${seti} ${args}> ${log} 2>&1 &
fi
exit 0
stop|-stop|--stop)
kill ${PID}
if (pidof ${seti_prog} 2>/dev/null 1>/dev/null) ; then
kill -9 ${PID}
fi
exit 0
restart|-restart|--restart)
kill ${PID}
if (pidof ${seti_prog} 2>/dev/null 1>/dev/null) ; then
kill -9 ${PID}
fi
if [ -f ${log} ] ; then
if [ -f ${log}.0 ] ; then
rm -f ${log}.0
fi
mv ${log} ${log}.0
fi
cd ${spool_dir}
exec ${seti} ${args} > ${log} 2>&1 &
exit 0
status|-status|--status)
if (pidof ${seti_prog} 2>/dev/null 1>/dev/null) ; then
echo 'Seti@home is running..'
else
echo 'Seti@home is NOT running..'
fi
exit 0
email|-email|--email)
args="${args} -email"
shift
version|-version|--version)
${seti} -version
exit 0
countries|-countries|--countries)
args="${args} -countries"
shift
nice|-nice|--nice)
if [ "X$2" = "X" ] ; then
numb="1"
else
numb=$2
fi
args="${args} -nice ${numb}"
shift
shift
login|-login|--login)
echo You are making a new login for ${seti_prog}.
echo This will start ${seti_prog} in the foreground.
echo Kill with CTRL_C and restart to run in the background.
echo
echo I will assume you have a ${spool_dir} and you have rights
echo to it. If not either make that dir or look in $0 and
echo change the spool_dir variable to your own.
sleep 2
clear
cd ${spool_dir}
${seti} -login
exit 0
*)
help_me
exit 1
esac
done
exec ${seti} ${args}
###############################################
## Bye bye
I'm a slackware user, and a new one, so not out of
sentimental reasons. I just don't like the RH distro.
But I bet I can get the codewarrior to work with some symlinks and a glibc2.1 compile. I've got an slack distro ported half to gilb2 just for the citadel BBS (Nice!) so I know how to do it.
I mean, they can *say* it's for redhat only, but it's just a little work to adapt it to your distro
of choice.
"isn't that one of the reasons we are pissed at MS, or is it OK for a Linux distro to do it ?"
Nah.. That's not a smart remark. You cannot compare the linux environment, or any Unix environment to the MS way of bundling.
Take, for instance, a normal Debian install. You could still add KDE and the COREL suite yourself.
Or for that matter, imagine Sun *bundling* java with solaris..It's still not the same as the "try
to enforce windows everywhere" strategy Win employs.
There are still bugs left. Obscure ones (such as the one I found) but bugs. Yet I certainly switched from my beloved afterstep to wmaker.
;-)
Although I still find afterstep nice too
BTW the bug is this:
If you start a x session at tty1 you're x display will go to tty7. Whenever you try to start a command line tool in the Run applet it will prompt you for stuff on tty1. I started a "ssh -l my_name
My_Host" in the run applet. On tty1 a command line
prompt was started asking me for a password. To my
stunning suprise the password *was* echoed on the
screen. I did file report.
Uhmm... Neutrino don't *DO* anything.
That's their characteristic, and thats why the're
so incredibly hard to detect.
Also, the so called "homunculus", the dust cloud that surrounds eta carina, points to what youm were saying
*All* OS'es suffer from DoS exploitable bad code. /sys dir on my FreeBSD box for
I had to patch the
some exploit too.
Get the libstdc++-2.8.glibc2-compiled package
/lib, and therefor you can run a libc5 stdc++ and a stdc++ for glibc2.
from Brian Dial's excellent
ftp://lrasputin.linuxos.net/pub/slakware-packs.
It installs in
way
I think that KDE resembles OS2 the most.
I think KDE was developed to look like OS2/warp,
if I recall correctly.
Win probably nicked quite a lot from OS2.
In other words: You have an imac
ftp://rasputin.linuxos.net/pub/slackware-packs/gno me
Read the readme's as gnome is a cmplicated package with lot of libs.
The four point for upgrading slack to glibc2
1. Remove your libc.tgz package with pkgtool
2. Install the glibc2-devel.tgz package from the contrib dir
3. Rebuild egcs and binutils
4. Rebuild libgdbm and sendmail,ypstuff and perl
Enjoy your fresh and shiny libc6 box!
It seems that the following distro is going to be
glibc2 based. What I've heard is that Patrick is
halveway a box with glibc2.1.1.alpha.what.have.you
"and linuxconf meant that, generally speaking, I didn't have to worry about much."
..except for possible exploits
http://geek-girl.com/bugtraq/1999_2/0317.html
It's getting a bit of a boring story but here it is again:
;-) and it runs quite fine.
Slackware has runtime support for glibc2
And if you want glibc2 building libs go to the contrib dir and install glibc2-devel.
I have a slack box ported to glibc2 ( A 386, Whooey, building egcs and glibc2 took *days*
I don't intend to flame here, but to say that
RedHat is all a bed of roses is bit out of reality.
I found Redhat to have twiddling the code a bit
*too* much. Look at BugTraq and you'll find quite
some *specific* RH exploits.