初尝 64位 linux kernel

机器是athlon64的，不跑跑64bit linux实在不过瘾，于是下了个linux kernel 2.6.22.5自己编译看，一开始下载是想编译32位的，但是启动时有点小问题，中间会卡住，要不断按开机键才能继续，挺诡异的，但是64位的编译好后竟然没有这个问题了，比较有趣。

在编译前进行配置时倒是出了些问题，由于我要在32位系统下编译64位内核，是交叉编译，不是很熟练，查了半天在发现应该在make是加入ARCH=x86_64的参数。（ubuntu里习惯称amd64, 但linux内核里叫x86_64)

另外configure的时候也有问题，我直接make ARCH=x86_64总报错， make ARCH=x86_64 config也不行，后来想到，现在的.config是按i386配置的，可能跟64位的有冲突，于是用make ARCH=x86_64 oldconfig重新配置，别说，还真问了几个新问题，之后再make ARCH=x86_64就可以编译了，最后别忘了编译模块，再都安装就好了。

现在运行挺不错，但是aptitude不能找到64位程序，还有待研究。

Comments

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later, gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with --userns=auto and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared various networking options and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...

WangLu's Notes

Search This Blog