扩展coLinux分区镜像文件

现在我用coLinux跑ArchLinux，镜像只有256M，不过装几个包就不够用了，急需扩展镜像大小。

link：http://colinux.wikia.com/wiki/ExpandingRoot

上面链接上说了很多方法，下面是我最喜欢的一种，优点是安全，且不需要额外软件（如cygwin），缺点是复制了两次已有fs，有点占空间，不过原始大小只有256M，所以没什么问题

1.关掉所有coLinux

2.假设现在的文件镜像为cur.img,复制一份，设文件名为old.img

3.创建新的镜像文件，假设新文件名为new.img，大小2G，则在命令行下运行

fsutil file createnew new.img 2147483648

注：Vista下需管理员权限

4. 修改coLinux的conf文件，把三个文件都挂上，例如：
hda1="c:\Program Files\coLinux\cur.img"
hda3="c:\Program Files\coLinux\old.img"
hda4="c:\Program Files\coLinux\new.img"

5. 启动coLinux

6. 检查old fs: e2fsck /dev/hda3

7. copy fs: dd if=/dev/hda3 of=/dev/hda4

8.检查new fs: e2fsck -f /dev/hda4

9.resize new fs: resize2fs -p /dev/hda4

10. 再检查 new fs: e2fsck /dev/hda4

11. 最后修改coLinux的conf文件，用new.img作为root，如果没有问题，就可以删掉cur.img和old.img

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