You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: kernel-data-structure-lab1/README.md
+37-3Lines changed: 37 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,43 @@ Esta práctica también nos permitirá aprender a utilizar ciertas funciones que
19
19
20
20
## Commands
21
21
22
+
### Other way to compile module bridgeOwn and clientBridge
23
+
24
+
firstly, go to the folder /**kernel-data-structure-lab1** inside the project, run the command **sudo ./scripts/run_it_run**, this command will create symbolic links or just links to access in an easier way to commands like: bridge_load, bridge_reset also to clientBridge executable easier.
25
+
26
+
Now, if you want execute clientBridge you just to write:
27
+
28
+
```sh
29
+
sudo clientBridge
30
+
```
31
+
32
+
Here, command list:
33
+
34
+
```sh
35
+
sudo bridge_status
36
+
```
37
+
=> show if the module is on.
38
+
```sh
39
+
sudo bridge_load
40
+
```
41
+
=> load the module.
42
+
```sh
43
+
sudo bridge_reset
44
+
```
45
+
=> reset the module, but before, unload the module, it execute the make command and finally load the module again.
46
+
```sh
47
+
sudo bridge_syslog_clean
48
+
```
49
+
=> clean the syslog in /var/log/syslog. Don't worry it will make a backup.
50
+
51
+
```sh
52
+
sudo compile_client
53
+
```
54
+
=> compile the clientBridge from **kernel-data-structure-lab1** only. It will replace with Makefile in future versions.
55
+
56
+
Note: Some of these commands work just if you are in the **kernel-data-structure-lab1** path in his terminal or console.
0 commit comments