User Details
- User Since
- Jun 25 2022, 1:00 PM (101 w, 16 h)
Sat, May 18
- Addressed IPv6 and formatting issues
Thu, May 9
Wed, May 8
I accidentally created it. There is already another revision, D45124.
I tested the IPv6-only machine and found no errors affecting it. Here are some methods I employed to ensure IPv6 cleanliness:
Jan 27 2024
Oh, I get it. It is using the "dev.pcm.0.dest" to control the output. In my device, it is like below. The HDMI output can work whilst setting it to 2.
Jan 20 2024
This is my test result:
Jan 19 2024
Thank you for your response. I'm currently experiencing confusion. I applied the patch from https://lists.freebsd.org/archives/freebsd-arm/2022-February/000949.html to my RPI4 device, compiled it, and encountered no errors. It seems the patch referenced in the link corresponds to D37878, D37878, D36431.
Jan 18 2024
Is this patch based on the three preceding patches? Were there compilation warnings (or errors) encountered when applying those three patches, leading to the creation of this patch to address those issues?
Dec 31 2023
Greetings! I am Yan-Hao Wang, and I present my Q4 status report, which serves as a continuation of the Q3 report concerning the FreeBSD online editor. I appreciate your review and feedback.
Nov 15 2023
- Use cp -f in "commit" case
- Revise "lower_file" in the "commit" case.
- Revise lower_file in "basic" and "revert" case
- Update according lwhsu advices
- Remove gunion unload.
- Update "basic" test case.
- Move "create" teas case to the first one.
- Describe "2097152" magic number.
- Update "revert" test case.
Nov 9 2023
- Update according lwhsu advices
Nov 8 2023
- Update according lwhsu advices
Oct 16 2023
Greetings, I am Yan-Hao Wang, a FreeBSD developer who has been a summer intern at FF. I am pleased to present my Q3 status report.
Sep 25 2023
- Fix expected_value variable
Sep 24 2023
- Remove $FreeeBSD$
- Fix BSD.tests.dist
- Use conf.sh to share common function
Sep 23 2023
- Remove unnecessary code and simplify again.
- Remove unnecessary code and simplify
Sep 5 2023
Use fsck -p -f to check gunion and readable device
Sep 3 2023
Sep 2 2023
Format writable_device statement remove. In general, upper device is not necessary to format.
Sep 1 2023
The tests are described below.
- load:
- Use kldstat to confirm the gunion load and unload is actually work.
- create:
- Look /dev/ folder to confirm the gunion create and destroy is actually work.
- commit:
- Use checksum to check the file is actually commit.
- offset:
- Create two partitions and see if we can mount the union device which use the two partitions. Test the gunion commit -o offset.
- size:
- Use diskinfo test gunion commit -s size.
- secsize:
- Use diskinfo test gunion commit -S secsize.
- gunionname:
- Look /dev/ folder to test gunion commit -Z gunionname.
- revert:
- Use checksum to check the file is actually revert.
- add one test case to test gunion commit -o offset
- format the code.
Aug 31 2023
Aug 21 2023
- Fix file format.
- Fix the format.
- Use number style.
- Remove unnecessary xo_finish function.
- Use number style.
- Using xo_err to replace printf.
- Use number style.
Aug 20 2023
- Change usage function.
- Use EXIT_ string style.
- Use number style here.
- Using xo_error instead of 'fprintf'.
- Decide use number style here.
Using xo_error instead of fprintf.
- Using sysexits.h string in all the files.
Aug 19 2023
- Use EX_ string from sysexits.h if the file include it.
In some files sysexit.h is not include (below lists), I use the number style there to avoid much change.
a. main.c b. netisr.c
The above has sysexit.h use EX_ string.
a. common.c b. if.c c. nhgrp.c d. nhops.c e. route.c f. route_netlink.c f. route_netlink.c
- Use xo_error instead of fprintf.
- Decide using 1 and 0 instead of EXIT_FAILURE and EXIT_SUCESS.
Old revision.
Aug 16 2023
- Fix the file foramt.
- Fix the file format.
Aug 15 2023
Only simple two test cases.
- using echo to check the environment value is correct and the environment variable is actually exist.
- try add env and delete the env, then use printenv to check that env.
- use different way to test.
Aug 12 2023
- Return non-zero status on write failuer.
Originally check the xo_finish return value can achive the POSIX standard. Howeve I use (trap "" PIPE; vmstat 2>stderr; echo $? >status | true to check this, it didn't work. I find check xo_finish return value is not enough here. Becuase xo_finish will always return 0, there is already a xo_flush call before xo_finish. So we need check xo_flush return value here.
- Remove unnecessary space line.
- Remove unnecessary space line.
- Remove unnecessary space line.
- Remove unnecessary space line.
- Remove unnecessary space line.
- Remove unnecessary space line.
- Remove unnecessary space line.
Remove unnecessary space.
Remove unnecessary space.
Remove unnecessary space.
Aug 11 2023
Aug 10 2023
Ignore this. Create this revision accidentally.