mirror of
https://github.com/CoderSherlock/CoderSherlock.github.io.git
synced 2026-06-12 23:58:11 -07:00
Updated all covers and small css change
This commit is contained in:
@@ -2,6 +2,7 @@
|
||||
title: "STSD: Stop Talking Start Doing"
|
||||
date: 2016-10-26 22:50:33 -0400
|
||||
tags: Diary
|
||||
cover: '/static/2024-04/logo.png'
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Using charles proxy to monitor mobile SSL traffics"
|
||||
date: 2016-10-27 22:50:33 -0400
|
||||
tags: ["Network", "Charles proxy"]
|
||||
author: Pengzhan Hao
|
||||
cover: '/static/2021-12/charles-proxy-logo.png'
|
||||
cover: '/static/2024-04/charles.png'
|
||||
---
|
||||
|
||||
In this blog, I will generally talk about how to use proper tools to monitor SSL traffics of a mobile devices. Currently, I only can dealing with those SSL traffics which use an obviously certification. Some applications may not using system root cert or they doesn't provide us a method to modify their own certs. For these situation, I still didn't find a good solutions for it. But I'll keep updating this if I get one.
|
||||
|
||||
@@ -3,17 +3,18 @@ title: "Some of my previews experiment works: 2016"
|
||||
date: 2016-10-28 12:27:33 -0400
|
||||
tags: ["Research", "Log", "Miscellanies"]
|
||||
author: Pengzhan Hao
|
||||
cover: '/static/2024-04/research2016.png'
|
||||
---
|
||||
This blog contains only some basic record of my works. For some details, I will write a unique blog just for some specific topics.
|
||||
<!--more-->
|
||||
|
||||
# 2016-10
|
||||
## 2016-10
|
||||
|
||||
## Time Experiment of rsync
|
||||
### Time Experiment of rsync
|
||||
|
||||
Patch is based on rsync with version 3.1.2. \[[Rsync](https://download.samba.org/pub/rsync/rsync-3.1.2.tar.gz)\|[Patch](/static/2016-10/rsync/rsync-3.1.2-time.patch)\]
|
||||
|
||||
### How to collect data
|
||||
#### How to collect data
|
||||
|
||||
Basically, everything of transmission time and computation time will be output with overall time will be printed on the console.
|
||||
But we also need some bash script to collect data through different size of random size and with different modification through them.
|
||||
@@ -22,11 +23,11 @@ But we also need some bash script to collect data through different size of rand
|
||||
- Start from 8K to 64M, modify at last, \[[Bash script](/static/2016-10/rsync/small2Big_change_at_last.sh)\]
|
||||
- Start from 8K to 64M, modify at random place with a (slow) python script, \[[Bash script](/static/2016-10/rsync/small2Big_change_at_anyplace.sh)\|[Python program](/static/2016-10/rsync/addbyte.py)\]
|
||||
|
||||
## Time Experiment of seafile
|
||||
### Time Experiment of seafile
|
||||
|
||||
Patch is based on seafile 5.1.4. You can find the release from [seafile official repo](https://github.com/haiwen/seafile/releases). You may follow official compile instructions from [here](https://manual.seafile.com/build_seafile/linux.html). \[[Patch **no longer avaiable, new version at following sections**]()\]
|
||||
|
||||
### How to collect data
|
||||
#### How to collect data
|
||||
|
||||
We also need everything be done using scripting. But this time I only design added some distance between two increasing files' sizes.
|
||||
|
||||
@@ -42,7 +43,7 @@ awk '/CDC|HUT|ALL/ {print $4,$5}' ~/.ccnet/log/seafile.log > results.stat
|
||||
~~~~
|
||||
|
||||
|
||||
### Install Seafile on odroid xu
|
||||
#### Install Seafile on odroid xu
|
||||
|
||||
Due to failure of my cross-compile to seafile on android. I used develop board as a replacement experiment platform for ARM-seafile testing. I used a [odroid xu](http://www.hardkernel.com/main/products/prdt_info.php?g_code=G137510300620) as hardware standard. Because all I need is an ARM platform, only an ARM-Ubuntu is enough for me. But develop prototype on a board is much fun than coding, I won't address much this time. But I'll start a blog telling some really cool stuff I made for a strange aim.
|
||||
|
||||
@@ -60,11 +61,11 @@ sudo dd if=ubuntu-14.04lts-xubuntu-odroid-xu-20140714.img of=/dev/sdb bs=1M conv
|
||||
sync
|
||||
~~~~
|
||||
|
||||
# 2016-11
|
||||
## 2016-11
|
||||
|
||||
## Android Kernel
|
||||
### Android Kernel
|
||||
|
||||
### How to build an Android Kernel?
|
||||
#### How to build an Android Kernel?
|
||||
|
||||
Generally, I won't tell anything in this parts, just mark some related links, and point out some mistakes or error solutions.
|
||||
|
||||
@@ -74,11 +75,11 @@ Generally, I won't tell anything in this parts, just mark some related links, an
|
||||
|
||||
- [Packing and Flashing a Boot.img](https://softwarebakery.com/building-the-android-kernel-on-linux) **[highly recommend]**
|
||||
|
||||
# 2016-12
|
||||
## 2016-12
|
||||
|
||||
## Android Kernel
|
||||
### Android Kernel
|
||||
|
||||
### How to compile with ftrace?
|
||||
#### How to compile with ftrace?
|
||||
|
||||
If we want to debug under android, ftrace is a great tool for working. But, ftrace is not available in android if we used default configure file. Android kernel configuration is in **arch/arm64/kernel/configs**. We need to add few lines under that.
|
||||
|
||||
@@ -94,7 +95,7 @@ CONFIG_SCHED_TRACER=y
|
||||
CONFIG_STACK_TRACER=y
|
||||
~~~~
|
||||
|
||||
### How to extract android images: Dump an image
|
||||
#### How to extract android images: Dump an image
|
||||
|
||||
If we want to hold a rooted status after flashing boot, we need to extract an image from android devices. We can first use following command to find which blocks belongs to. According to some references, [this article](http://forum.xda-developers.com/showthread.php?t=2450045) provide three ways to dump an image, I picked one for easy using.
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Xv6 introduction"
|
||||
date: 2017-07-28 14:56:55 -0400
|
||||
tags: ["Xv6", "Teaching", "Operating system"]
|
||||
author: Pengzhan Hao
|
||||
cover: '/static/2021-10/Xv6_LS_Command_Output.png'
|
||||
cover: '/static/2024-04/xv6.png'
|
||||
---
|
||||
|
||||
In this post, you will learn a few basic concepts of xv6. Learning path will be closed coupled to first project assignment I gave when I assisted in teaching OS classes.
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Generate Word Cloud Figures with Chinese-Tokenization and WordCloud pyt
|
||||
date: 2020-09-15 22:00:14 -0400
|
||||
tags: Visualization
|
||||
author: Pengzhan Hao
|
||||
cover: '/static/2020-09/2020-06-28.png'
|
||||
cover: '/static/2024-04/wordcloud.png'
|
||||
---
|
||||
|
||||
Let's generate a word cloud like this.
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "EDDL: How do we train neural networks on limited edge devices - PART 1"
|
||||
date: 2021-10-13 16:53:20 -0400
|
||||
tags: ["Research", "Edge computing"]
|
||||
author: Pengzhan Hao
|
||||
cover: '/static/2021-10/edgelearn-1.png'
|
||||
cover: '/static/2024-04/eddl1.png'
|
||||
---
|
||||
This post introduces our previous milestone in project "Edge trainer", as the paper "EDDL: A Distributed Deep Learning System for Resource-limited Edge Computing Environment." was published.
|
||||
As the first part of the introductions, I focus only on the motivation and summary of our works.
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "EDDL: How do we train neural networks on limited edge devices - PART 2"
|
||||
date: 2021-10-31 13:01:14 -0400
|
||||
tags: ["Research", "Edge computing"]
|
||||
author: Pengzhan Hao
|
||||
cover: '/static/2021-10/f.5_Impl_leader_worker.png'
|
||||
cover: '/static/2024-04/eddl2.png'
|
||||
mathjax: true
|
||||
---
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Labs of CS350"
|
||||
date: 2022-02-22 17:08:17 -0400
|
||||
tags: ["Xv6", "Teaching", "Operating system", "Binghamton university"]
|
||||
author: Pengzhan Hao
|
||||
cover: '/static/2022-02/BU.jpeg'
|
||||
cover: '/static/2024-04/bu.png'
|
||||
---
|
||||
|
||||
This will be a series regarding lab I gave during the spring 2022 semester.
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Debug Kubelet"
|
||||
date: 2024-04-10 03:34:00 -0400
|
||||
tags: ["Kubernetes", "Kubelet", "Debug"]
|
||||
author: Pengzhan Hao
|
||||
cover: '/static/2024-04/Kubelet.webp'
|
||||
cover: '/static/2024-04/kubelet.png'
|
||||
---
|
||||
|
||||
## Debug logs
|
||||
|
||||
Reference in New Issue
Block a user