beenull/ladybird
1
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2024-11-22 15:40:19 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 6
ladybird/Kernel/run

67 lines
2.1 KiB
Text
Raw Normal View History

Import the "gerbert" kernel I worked on earlier this year. It's a lot crappier than I remembered it. It's gonna need a lot of work.
2018-10-16 09:01:38 +00:00
#!/bin/sh
run: Make it easy to override which qemu executable is used. Patch contributed by "pd"
2019-05-04 00:51:50 +00:00
[ -z "$SERENITY_QEMU_BIN" ] && SERENITY_QEMU_BIN="qemu-system-i386"
Kernel: Expose kernel command line to userspace through /proc/cmdline
2019-06-16 12:05:07 +00:00
[ -z "$SERENITY_KERNEL_CMDLINE" ] && SERENITY_KERNEL_CMDLINE="hello"
Kernel: Make better use of the multiboot info. Define the multiboot info struct properly so we don't have to grab at byte offsets in the memory access checker code. Also print kernel command line in init().
2019-06-02 07:50:18 +00:00
Run: Properly use common memory size
2019-11-01 22:46:39 +00:00
[ -z "$SERENITY_RAM_SIZE" ] && SERENITY_RAM_SIZE=128M
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
[ -z "$SERENITY_COMMON_QEMU_ARGS" ] && SERENITY_COMMON_QEMU_ARGS="
$SERENITY_EXTRA_QEMU_ARGS
-s -m $SERENITY_RAM_SIZE
-d cpu_reset,guest_errors
-device VGA,vgamem_mb=64
-hda _disk_image
-debugcon stdio
-soundhw pcspk
-soundhw sb16
"
Fix jittery mouse
2019-05-01 19:45:17 +00:00
export SDL_VIDEO_X11_DGAMOUSE=0
Give the emulator testing environments 128 MB of RAM. I'm working on porting GCC and it needs a fair bit of memory to run.
2019-03-27 12:02:29 +00:00
Kernel: Add a NetworkTask and a received network packet queue. It will be easier to deal with incoming packets in a separate task.
2019-03-11 11:43:45 +00:00
if [ "$1" = "b" ]; then
# ./run b: bochs
bochs -q -f .bochsrc
elif [ "$1" = "qn" ]; then
# ./run qn: qemu without network
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
$SERENITY_QEMU_BIN \
$SERENITY_COMMON_QEMU_ARGS \
Allow passing extra args to qemu via a SERENITY_EXTRA_QEMU_ARGS env var.
2019-04-24 19:06:16 +00:00
-device e1000 \
Build: Remove grub from default build process This removes grub and all the loopback device business from the default build process. Running grub takes about a second, and it turns out it's inconsistently packaged in different distributions, which has led to at least one confusing issue so far (grub-install vs grub2-install). Removing it from the basic path will make it easier for people to try Serenity out. There are now two scripts that can be used to build a disk image: 1. `build-image-grub.sh` - this will build an image suitable for writing to the IDE hard drive of a physical machine, complete with a partition table and bootloader. This can be run in qemu with the `qgrub` target for the `run` script. 2. `build-image-qemu.sh` - this is a simpler script which creates a bare filesystem image rather than a full MBR disk. Both of these call out to `build-root-filesystem.sh` to do most of the work setting up... the root filesystem. For completeness' sake, I've retained the `sync.sh` script as a simple forwarding to `build-image-qemu.sh`. This relies on the functionality from #194 and #195. #195 allows us to use `/dev/hda` as the root device when nothing else is specified, and #194 works around a strange feature of qemu that appends a space to the kernel command line.
2019-06-04 12:16:30 +00:00
-kernel kernel \
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
-append "${SERENITY_KERNEL_CMDLINE}"
More work on IPv4 sockets and /bin/ping. It's now actually possible to ping other hosts on the network! :^) I've switched the "run" script over to starting QEMU with user networking since that works better for my testing needs right now.
2019-03-13 02:26:01 +00:00
elif [ "$1" = "qtap" ]; then
# ./run qtap: qemu with tap
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
sudo $SERENITY_QEMU_BIN \
$SERENITY_COMMON_QEMU_ARGS \
Runner: Enable QEMU's KVM mode by default This makes QEMU run significantly faster on Linux systems with KVM.
2019-10-13 13:07:23 +00:00
-enable-kvm \
Allow passing extra args to qemu via a SERENITY_EXTRA_QEMU_ARGS env var.
2019-04-24 19:06:16 +00:00
-object filter-dump,id=hue,netdev=br0,file=e1000.pcap \
-netdev tap,ifname=tap0,id=br0 \
-device e1000,netdev=br0 \
Build: Remove grub from default build process This removes grub and all the loopback device business from the default build process. Running grub takes about a second, and it turns out it's inconsistently packaged in different distributions, which has led to at least one confusing issue so far (grub-install vs grub2-install). Removing it from the basic path will make it easier for people to try Serenity out. There are now two scripts that can be used to build a disk image: 1. `build-image-grub.sh` - this will build an image suitable for writing to the IDE hard drive of a physical machine, complete with a partition table and bootloader. This can be run in qemu with the `qgrub` target for the `run` script. 2. `build-image-qemu.sh` - this is a simpler script which creates a bare filesystem image rather than a full MBR disk. Both of these call out to `build-root-filesystem.sh` to do most of the work setting up... the root filesystem. For completeness' sake, I've retained the `sync.sh` script as a simple forwarding to `build-image-qemu.sh`. This relies on the functionality from #194 and #195. #195 allows us to use `/dev/hda` as the root device when nothing else is specified, and #194 works around a strange feature of qemu that appends a space to the kernel command line.
2019-06-04 12:16:30 +00:00
-kernel kernel \
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
-append "${SERENITY_KERNEL_CMDLINE}"
Build: Remove grub from default build process This removes grub and all the loopback device business from the default build process. Running grub takes about a second, and it turns out it's inconsistently packaged in different distributions, which has led to at least one confusing issue so far (grub-install vs grub2-install). Removing it from the basic path will make it easier for people to try Serenity out. There are now two scripts that can be used to build a disk image: 1. `build-image-grub.sh` - this will build an image suitable for writing to the IDE hard drive of a physical machine, complete with a partition table and bootloader. This can be run in qemu with the `qgrub` target for the `run` script. 2. `build-image-qemu.sh` - this is a simpler script which creates a bare filesystem image rather than a full MBR disk. Both of these call out to `build-root-filesystem.sh` to do most of the work setting up... the root filesystem. For completeness' sake, I've retained the `sync.sh` script as a simple forwarding to `build-image-qemu.sh`. This relies on the functionality from #194 and #195. #195 allows us to use `/dev/hda` as the root device when nothing else is specified, and #194 works around a strange feature of qemu that appends a space to the kernel command line.
2019-06-04 12:16:30 +00:00
elif [ "$1" = "qgrub" ]; then
# ./run qgrub: qemu with grub
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
$SERENITY_QEMU_BIN \
$SERENITY_COMMON_QEMU_ARGS \
Runner: Enable QEMU's KVM mode by default This makes QEMU run significantly faster on Linux systems with KVM.
2019-10-13 13:07:23 +00:00
-enable-kvm \
Build: Remove grub from default build process This removes grub and all the loopback device business from the default build process. Running grub takes about a second, and it turns out it's inconsistently packaged in different distributions, which has led to at least one confusing issue so far (grub-install vs grub2-install). Removing it from the basic path will make it easier for people to try Serenity out. There are now two scripts that can be used to build a disk image: 1. `build-image-grub.sh` - this will build an image suitable for writing to the IDE hard drive of a physical machine, complete with a partition table and bootloader. This can be run in qemu with the `qgrub` target for the `run` script. 2. `build-image-qemu.sh` - this is a simpler script which creates a bare filesystem image rather than a full MBR disk. Both of these call out to `build-root-filesystem.sh` to do most of the work setting up... the root filesystem. For completeness' sake, I've retained the `sync.sh` script as a simple forwarding to `build-image-qemu.sh`. This relies on the functionality from #194 and #195. #195 allows us to use `/dev/hda` as the root device when nothing else is specified, and #194 works around a strange feature of qemu that appends a space to the kernel command line.
2019-06-04 12:16:30 +00:00
-object filter-dump,id=hue,netdev=breh,file=e1000.pcap \
Runner: Forward host TCP port 8823 to guest port 23 in QEMU This makes it easier to test TelnetServer when running in QEMU.
2019-09-09 07:19:43 +00:00
-netdev user,id=breh,hostfwd=tcp:127.0.0.1:8888-10.0.2.15:8888,hostfwd=tcp:127.0.0.1:8823-10.0.2.15:23 \
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
-device e1000,netdev=breh
Kernel: Enabling Text mode debugging (#696) Also added an option to start Serenity with text mode in QEMU in the run script.
2019-10-29 15:41:40 +00:00
elif [ "$1" = "qtext" ]; then
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
# ./run: qemu with serenity in text mode
$SERENITY_QEMU_BIN \
$SERENITY_COMMON_QEMU_ARGS \
Kernel: Enabling Text mode debugging (#696) Also added an option to start Serenity with text mode in QEMU in the run script.
2019-10-29 15:41:40 +00:00
-device e1000 \
-kernel kernel \
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
-append "${SERENITY_KERNEL_CMDLINE} text_debug"
More work on IPv4 sockets and /bin/ping. It's now actually possible to ping other hosts on the network! :^) I've switched the "run" script over to starting QEMU with user networking since that works better for my testing needs right now.
2019-03-13 02:26:01 +00:00
else
# ./run: qemu with user networking
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
$SERENITY_QEMU_BIN \
$SERENITY_COMMON_QEMU_ARGS \
Runner: Enable QEMU's KVM mode by default This makes QEMU run significantly faster on Linux systems with KVM.
2019-10-13 13:07:23 +00:00
-enable-kvm \
IPv4: Begin fleshing out TCP support.
2019-03-13 16:17:07 +00:00
-object filter-dump,id=hue,netdev=breh,file=e1000.pcap \
Runner: Forward host TCP port 8823 to guest port 23 in QEMU This makes it easier to test TelnetServer when running in QEMU.
2019-09-09 07:19:43 +00:00
-netdev user,id=breh,hostfwd=tcp:127.0.0.1:8888-10.0.2.15:8888,hostfwd=tcp:127.0.0.1:8823-10.0.2.15:23 \
IPv4: Begin fleshing out TCP support.
2019-03-13 16:17:07 +00:00
-device e1000,netdev=breh \
Build: Remove grub from default build process This removes grub and all the loopback device business from the default build process. Running grub takes about a second, and it turns out it's inconsistently packaged in different distributions, which has led to at least one confusing issue so far (grub-install vs grub2-install). Removing it from the basic path will make it easier for people to try Serenity out. There are now two scripts that can be used to build a disk image: 1. `build-image-grub.sh` - this will build an image suitable for writing to the IDE hard drive of a physical machine, complete with a partition table and bootloader. This can be run in qemu with the `qgrub` target for the `run` script. 2. `build-image-qemu.sh` - this is a simpler script which creates a bare filesystem image rather than a full MBR disk. Both of these call out to `build-root-filesystem.sh` to do most of the work setting up... the root filesystem. For completeness' sake, I've retained the `sync.sh` script as a simple forwarding to `build-image-qemu.sh`. This relies on the functionality from #194 and #195. #195 allows us to use `/dev/hda` as the root device when nothing else is specified, and #194 works around a strange feature of qemu that appends a space to the kernel command line.
2019-06-04 12:16:30 +00:00
-kernel kernel \
Run: Don't repeat common QEMU arguments
2019-11-01 23:01:45 +00:00
-append "${SERENITY_KERNEL_CMDLINE}"
fi
Reference in a new issue Copy permalink