Paper to do
Fix the architecture diagram: make it actually show some reasonable interactions if possible.
Fix the architecture diagram: make it actually show some reasonable interactions if possible.
Haven’t blogged much in a while.
Finished poster for PAM. Good.
Sorted out quite a bit of my paper for wintersim. Good.
More work to do on wintersim paper. Then leave for Boston on the 29th. Good.
From Tony: * A couple of bits (or just one?) was getting much too dense * Don’t sell myself strongly enough! Present the negative too much and don’t present the positive enough perhaps. Needs work. * Remember audience: simulation people, not OS people. Some bits Tony couldn’t quite figure out what I was really saying, so the chances of someone not involved in operating systems? Not so good. * Got lots of stuff there, can probably get two publication out of this. Ideally, I’d finish the larger paper first, then the smaller one for Wintersim. Might not be possible with the time constraints though. * Look into the simulation scenarios; they perhaps don’t show the best differences and again, aren’t sold well enough! There are still differences there, if I could come up with some concrete example where this mattered the section would be a lot stronger. * When Tony says “vague”, it is often because I’ve come up with, eg. a value judgement or such. Need to remember to keep things scientific. Sometimes hard to find these in your own writing.
My, what a lovely prompt.
-bash-2.05b# ipfw add 100 pipe 1 ip from { 10.0.11.0/24 or 10.0.12.0/24 or 10.0.13.0/24 } to
{ 10.0.14.0/24 or 10.0.15.0/24 or 10.0.16.0/24 } out
00100 pipe 1 ip from { 10.0.11.0/24 or 10.0.12.0/24 or 10.0.13.0/24 } to { 10.0.14.0/24 or
dst-ip 10.0.15.0/24 or dst-ip 10.0.16.0/24 } out
-bash-2.05b#
-bash-2.05b# ipfw add 100 pipe 2 ip from { 10.0.14.0/24 or 10.0.15.0/24 or 10.0.16.0/24 } to
{ 10.0.11.0/24 or 10.0.12.0/24 or 10.0.13.0/24 } out
00100 pipe 2 ip from { 10.0.14.0/24 or 10.0.15.0/24 or 10.0.16.0/24 } to { 10.0.11.0/24 or
dst-ip 10.0.12.0/24 or dst-ip 10.0.13.0/24 } out
-bash-2.05b#
-bash-2.05b# ipfw show
00100 0 0 pipe 1 ip from { 10.0.11.0/24 or 10.0.12.0/24 or 10.0.13.0/24 } to
{ 10.0.14.0/24 or dst-ip 10.0.15.0/24 or dst-ip 10.0.16.0/24 } out
00100 0 0 pipe 2 ip from { 10.0.14.0/24 or 10.0.15.0/24 or 10.0.16.0/24 } to
{ 10.0.11.0/24 or dst-ip 10.0.12.0/24 or dst-ip 10.0.13.0/24 } out
65535 12998732 11656541880 allow ip from any to any
-bash-2.05b#
-bash-2.05b# ipfw pipe 1 config bw 2Mbit/sec delay 100ms queue 10
-bash-2.05b# ipfw pipe 2 config bw 2Mbit/sec delay 100ms queue 10
-bash-2.05b#
Why does it ask you to select terminal type when logging into OpenBSD? That always annoys me. You need to remove references to tset in .login and .profile (depending on csh vs. sh/zsh shells).
Hacked upimagezip to compile and link on OpenBSD. Turned threads off, then it complained about dkcksum. This is defined inline in a FreeBSD header, but only defined (and only as a forward declaration) when compiling for the kernel in OpenBSD. So I copied and pasted the FreeBSD code into a file and linked that in. Still complains about an implicit declaration, but seems to compile and link OK.
I wanted to change runlevel to single user mode in OpenBSD. I’m not sure if there is a nice and easy way to do this. After some googling, I ended up typing:
kill -15 1
And it seemed to work. Lovely. Actually no, it’s crap. Maybe it didn’t work.
Apparently shutdown now goes to single-user. There doesn’t seem to be runlevels.
Remounting the root filesystem read-only was:
cd /
mount -ur /
And making an image:
ssh -n -l root machine19 '/root/imagezip/imagezip -o -d /dev/wd0c -' > ./openbsd-new.img
Note the /dev/wd0c — the ‘c’ means “the entire partition, not a single slice” (at first I tried wd0 then wd0a).
Made an image of DragonFlyBSD…
machine12# uname -a
DragonFly machine12 1.1-Stable DragonFly 1.1-Stable #0: Sat Feb 19 13:58:58 CET2005
root@chlamydia.fs.ei.tum.de:/usr/obj/usr/src/sys/GENERIC i386
Hooray!
After a Solaris machine boots:
stj2@relic ~/relic$ ssh machine19
Last login: Thu Mar 3 11:26:41 2005
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
-bash-3.00# ifconfig -a
lo0: flags=2001000849<up ,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
elxl0: flags=1004843<up ,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
inet 192.168.2.119 netmask ffffff00 broadcast 192.168.2.255
ether 0:b0:d0:ac:98:7
-bash-3.00# ifconfig rtls0 plumb
-bash-3.00# ifconfig rtls0 10.0.11.19 netmask 255.255.255.0
-bash-3.00# ifconfig rtls0 up
-bash-3.00# route add default 10.0.11.8
add net default: gateway 10.0.11.8
-bash-3.00# /opt/sfw/sbin/tcpdump -i rtls0 -s 100 -w ~/m19.pcap &
-bash-3.00# cd iperf-1.7.0
-bash-3.00# export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/sfw/lib
-bash-3.00# ./iperf -c 10.0.14.12 -t 20
Need to figure out how to set up rtls0 on boot, obviously. Also need to figure out LD paths and default route/static routes.
When we first setup the rtls0 device, we need to run devfsadm -v to get the device links set up.
I’ve decided: 1. Making a poster with Latex is a bad idea 2. Generating graphs with xplot and saving them to .PS then attempting to fix the PS is no fun.
Number 2. can at least be fixed up by my Perl script I wrote some time ago.
But I need a program I can import PS/EPS into then add more stuff and layout nicely. Hmm. The Gimp would almost do it, though it’s hardly a vector drawing program.
I’ll have to have a play with stuff on my home computer…
While brainstorming for the number 10. spot we considered:
Powered by WordPress