Weblogs for lters
Seems the kernel thinks its never except-able to have a prefix other than /64?
And I find that sudo -s changes the current user to root.
The breaks all the current users aliases and environment.
Normally after logging into a box, and needed to do root type things, sudo -s gets me privileges but keeps everything like my pwd, aliases, environment vars etc.
Is there anyway to get the current /Lenny/ behavior back?
That was much nicer or was I doing something I should not have been doing?
And allow us to setup a full IPv6 network behind it. When traffic needs to be converted back to IPv4, and I have public IPv4 and IPv6 space, is there a need for NAT64 or something like it?
If you have a ipv6 solution going, how to get back to the rest of the world without using a some other carrier?
If I have a public ip on v4 and v6, why would I want to use a broker?
Seems like some sort of nat from ipv6 to ipv4 and some sort of fancy DNS service is needed to handle the "on the fly" conversion...
NAT64 appears to be a compilable option for lenny.
Be sure you have these modules loaded:
ip_conntrack_ftp ip_nat_ftp ip_conntrack_pptp ip_nat_pptp
Otherwise, you will have weird problems with vpns not coming up right.
If anyone ever figures our how to set the default dns search domain, I would really like to know about it.
The included terminal.app does not send the F1 etc keys properly to the linux terminals.
I tried different terminal settings like xterm, xterm-color, vt100 and etc.
Each one brings its own problems it seems, none run perfectly like konsole or gnome-terminal.
There is an xterm application that is installed with X11, but who wants X11 running all the time.
Also, I miss the mouse single click paste and highlight to copy.
However, the macbook performs amazingly quick and well other wise.
If you are afraid of trying linux, try a Macbook.
until I ran
xrdb ~/.Xdefault or xrdb ~/.Xresources
After this xterm saw the changes.
Hope this saves someone else some grief!
I add something like this to /etc/network/interfaces
auto bond0 iface bond0 inet static address 10.1.1.2 netmask 255.255.255.0 network 10.1.1.0 gateway 10.1.1.1 up /sbin/ifenslave bond0 eth0 up /sbin/ifenslave bond0 eth1 pre-up modprobe -v bonding -o bond0 mode=4 miimon=50 post-down rmmod bond0
After creating the first DomU, I could not get it to use my bond0. It wanted to use eth0. I tried adding
('network-bridge netdev=bond0')to /etc/xen/xend-config.sxp but it would not work.
After doing some research I found this article: http://www.performancemagic.com/Dell1950_MD3000i_Xen_Debian_iSCSI_RDAC/Networking.html which proved to be very helpful.
I added the network-bond to the scripts in /etc/xen/scripts, set it to executable with chmod. I commented out the network-bridge and used this instead.
After a reboot it quit working. After reviewing the above link again, I saw I was missing the netboot in /etc/modules. Adding this and another reboot makes it all work great.
I sent an email with this info to the debian xen package team, but did not hear back from them.
It would be nice to have this script included and a comment added to /etc/xen/xend-config.sxp.
Perhaps this is all fixed in Lenny.
Or maybe there is a better way to do this.
Hopefully this can save someone else similar problems.
The system has minimal config changes and creating the xen client looks like this:
xen-create-image --hostname Xrrr.my.flat --ip 10.1.1.1 --dist etch
Installing ntpdate and running ntpdate -b myntpserver does not seem to fix it.
Tzconfig changes the timezone but does not fix it.
It still seems to be about 5 hours off.
Why is a xen client different than regular Etch?
Although I like icewm I still use konsole and other kde applications.
With kde4 apps showing up, it is fun to try them out as well.
I notice that although they work fine, icewm shows a black spot where the application icon should be.
Are there any tips for fixing this?