Adam.KungFooHampster.Com Is Not A Blog. I don't like journals and you
will never find anything out about my life here. ( update: it has been pointed out to me that this has become a blog... but.. i still won't say anything personal on here... dangit )
I have been experiencing some strange issues with my machine during high
load times... I posted
to freebsd-questions and got a very
interesting responce. The whole time I had assumed that the problem
was with my raid controller card when in actuallity it may be my Western
Digital Hard Disks.
I know I said that I wouldn't put journal sorta stuff on here, but I just
couldn't pass this up. I was playing Atari's Pong and
I found a sweet spot! I didn't have to move the paddle!!! It just
scored over and over and over and over and over... I found the sweet spot
right around when I scored 5 points and I just left it there till it got
to 21 and the level stopped. -- time passes -- WOO HOO!!! It left the
paddle where I left it! I was able to do it again from the start and get
60 seconds of proof! The madness!! WOO HOO!!
I personally use portupgrade on my FreeBSD system and have found it to be
invaluable. Another slashdot
post pointing to onlamp.com has a great
run-thru on the power of
portupgrade.
The FreeBSD handbook has a great
page that explains the differences between all of the different
branch tags so that one can decide which version is best for them.
When compiling on FreeBSD along with instructions on KVim's site, try
--with-qt-dir=/usr/X11R6
This assumes you have all the jail stuff(Jailer, Jail Utilities) from this dude(N. Nielsen)'s jail page.
PATH="/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin"
JAIL_NAME=jail-name
JAIL_HOSTNAME=jail-name.hostname.com
JAIL_IP=ip.ad.rde.ss
JAIL_DRIVE=vn0
jail_mount_drive () {
vnconfig -s labels -c ${JAIL_DRIVE} /jail/ufs/${JAIL_NAME}.ufs && \
disklabel -r -w ${JAIL_DRIVE} auto && \
tunefs -n enable /dev/${JAIL_DRIVE} && \
mount -o noatime /dev/${JAIL_DRIVE} /jail/home/${JAIL_NAME}
}
jail_unmount_drive () {
umount /jail/home/${JAIL_NAME} && \
vnconfig -u ${JAIL_DRIVE} && \
vnconfig -r labels ${JAIL_DRIVE}
}
case "$1" in
start)
;;
nostart)
jails | grep -q "${JAIL_HOSTNAME}"
if [ $? = 0 ]; then
echo " ${JAIL_NAME} already running"
else
if [ -x /jail/home/${JAIL_NAME}/usr/local/sbin/jailer ]; then
/usr/bin/true
else
jail_mount_drive && echo " mounted ${JAIL_NAME}"
fi
if [ -x /jail/home/${JAIL_NAME}/usr/local/sbin/jailer ]; then
/usr/sbin/jail /jail/home/${JAIL_NAME} ${JAIL_HOSTNAME} ${JAIL_IP} \
/usr/local/sbin/jailer && echo " started ${JAIL_NAME}"
else
echo " error: ${JAIL_NAME}: could not mount"
fi
fi
;;
stop)
jails | grep -q "${JAIL_HOSTNAME}"
if [ $? = 0 ]; then
killjail ${JAIL_HOSTNAME} && echo " stopped ${JAIL_NAME}"
else
echo " ${JAIL_NAME} already stopped"
fi
;;
restart)
jails | grep -q "${JAIL_HOSTNAME}"
if [ $? = 1 ]; then
echo " ${JAIL_NAME} not running - try start"
else
killjail -r ${JAIL_HOSTNAME}
fi
;;
mount)
if [ -x /jail/home/${JAIL_NAME}/usr/local/sbin/jailer ]; then
echo " ${JAIL_NAME} already mounted"
else
jail_mount_drive && echo " mounted ${JAIL_NAME}"
fi
;;
unmount|umount)
jails | grep -q "${JAIL_HOSTNAME}"
if [ $? = 0 ]; then
echo " error: ${JAIL_NAME}: could not unmount - still running"
else
if [ -x /jail/home/${JAIL_NAME}/usr/local/sbin/jailer ]; then
jail_unmount_drive && echo " ${JAIL_NAME} unmounted"
else
echo " ${JAIL_NAME} already unmounted"
fi
fi
;;
status)
jails | grep -q "${JAIL_HOSTNAME}"
if [ $? = 0 ]; then
echo -n " ${JAIL_NAME} running"
else
echo -n " ${JAIL_NAME} not running"
fi
if [ -x /jail/home/${JAIL_NAME}/usr/local/sbin/jailer ]; then
echo -n '+mounted'
else
echo -n '+unmounted'
fi
echo
;;
*)
echo ""
echo "Usage: `basename $0` { start | stop | restart | mount | u(n)mount }"
echo ""
exit 64
;;
esac
I have come across some intersting guideliness if one is writing an
Apache Module in C and wants to catch directories with their
Sethandler.
( Just imagine a directory as a file of type
httpd/unix-directory or DIR_MAGIC_TYPE. )
SetHandler doesn't affect directories inside a
<Location> or <Directory> directive.
SetHandler does affect all files within those directories
recursively.
mod_mime.c's first few
lines of its "type checker" immediately rule out directories as
r->content_type=DIR_MAGIC_TYPE and returns OK.
mod_autoindex and mod_dir will catch this mime type.
This is why the handler of the module I am working on isn't getting a
chance. The way my module can get a chance is by implementing its own
"type checker". I had it access mod_mime's configuration data and check
to see if its cfg->handler matched the name of my module's
handler. If it checked out then I changed r->handler to equal
the name of my module's handler. I also added another condition to check
if the r->uri's last character was a slash("/"). If it wasn't
a slash then I returned DECLINED so that mod_dir would
redirect it to the appropriate path.
The reason I had to do this is because every module's type checker gets a
shot to change the attributes of a request object. It gets called every
time there is a hit to apache and does not care if you defined a
SetHandler inside a <Location> or
<Directory> directive. I needed to know that the object
being requested was within the bounds of a
SetHandler(cfg->handler) with the same name as my
handler handler. I found this out the hard way when every virtual host on
my site ended up with a blank page because I assumed that my module would
only be called within a SetHandler directive and that I wouldn't have to
verify.
I hope someone out there finds this information useful because I wasted a
lot of time looking in the wrong places to solve my problem.
rule of thumb: know thy ip's - now you don't have to figure out what
ports to keep open (destination to you).. ( works best when dealing with
static ip's )
- printing - cups
$ smbspool smb://username:password@server/printer
ln -s /usr/local/bin/smbspool /usr/local/libexec/cups/backend/smb
(/usr/local)/etc/lmhosts
ip.ad.dre.ss server
- mounting
$ mount_smbfs -I ip.ad.dre.ss //username@server/share /mnt/share
(/usr/local)/etc/nsmb.conf
[server:username:share]
password=password
(/usr/local)/etc/rc.d/samba_mount.sh
#!/bin/sh
case $1 in
start)
/sbin/mount | grep -q '/mnt/share'
if test $? = 0 ; then
echo "alrady mounted"
else
/usr/sbin/mount_smbfs -I 192.168.1.2 //username@server/share /mnt/share
fi
;;
stop)
/sbin/mount | grep -q '/mnt/share'
if test $? = 0 ; then
/sbin/umount /mnt/share
else
echo "already unmounted"
fi
;;
*)
echo "Useage: `basename $0` (start|stop)"
esac
HOW can I get mozzilla and IE to render xml pages with xsl in similar fashions?
- XML's xml:space="preserve" is an attribute
that will tell a tag to preserve whitespace and linefeeds
- XSL's <xsl:preserve-space
elements="tag"/> is a xsl tag that will tell the xsl
processor to preserve whitespace and linefeeds for the specified
elements (white seperated list)
- XML's second line! <?xml-stylesheet
type="text/xsl" href="template.xsl" alternate="no"?>
- XSL's <xsl:stylesheet ... >
- omit-xml-declaration="no" -- keeps the
<?xml version="1.0"?> at the top of the
output. -- tells IE to respect
xml:space="preserve" among other things.
- indent="no" -- prevents IE from getting
confuzed with whitespace if you have white-space: pre CSS
usage being processed on the outputted HTML.
- method="html" -- tells mozilla to process this
output like html (obviously it doesn't do anything intelligent with
media-type, doctype-public, or
doctype-system ... they're just output ... not
instructions like method
- media-type="text/xml" -- tells IE to use this
document like an XML document... so that it will respect the
xml:space="preserve"'s
- doctype-public="-//W3C//DTD HTML 4.01
Transitional//EN" -- we can't use xhtml because
method="html" doesn't make self ending tags like
<br/>
- doctype-system="http://www.w3.org/TR/html4/loose.dtd"
-- we can't use xhtml because method="html" doesn't make
self ending tags like <br/>
To see this page as XML processed against XSL on the
fly with both IE and MOZ ... clicky ... clicky ...
If you REALLY feel that its necessary to contact me...