MLD-5.x > General

(MLD 5.4 testing) kernel 5.3.5.202.31 amd64

<< < (3/10) > >>

clausmuus:
It is possible to use the space of the sdb3 device by resizing the root partition.
Therefor you must first remove the mount of the sdb3 device from the /etc/fstab . There sould be some lines that contain the device. One line by device id and some bind mounts of the /mnt/... device mount point. If you do not have any data on the partition it sould be secure to do so. After that change you must reboot the system. Be award, to add a new data device, if you plan to make any recordings.
Now you can remove the sdb3 partition with fdisk and expand the sdb2 partition. After a second reboot you can use the btrfs tool to resize the sdb2 partition to use the new space.

I never have test this, but I think it should be work.

It is also possible to start the MLD development docker container on any other PC witch can run docker container. Maybe that's a more simple way if you have one with more free space.

gr4vity:
Okay, i have 7.1GB free space instead of 1.7GB  on sdb2 partition.  :D
I already tried that many times on Android SD cards distros but i had to ask you 1st just to make sure.

It's my 1st time to use that docker container so i'm still learning about it.
I had installed it by access MLD from my Raspberry pi 3 via ssh.
Now, when i start docker container i can see MLD folder via ssh but i can't access it using samba on the Raspberry pi.

- How i can paste the module source folder inside docker container in order to compile it?
- Do i have to modify the module Makefile because it points to /usr/src/linux-headers-5.3.5.202.31

clausmuus:
You do not need to change the dockerfile. You have a full linux (debian) system inside the docker container. So you can inside install packages, call a "git clone", use scp to copy files,...
You can also install and start a samba server if you want. You must only know, that no init scripts will be start automatically inside the docker container.
After you have build the new kernel, you can copy it by scp to outside (after you have installed it).

gr4vity:



--- Quote from: clausmuus on October 22, 2019, 00:06:54 ---You do not need to change the dockerfile. You have a full linux (debian) system inside the docker container.

--- End quote ---


If you tried the application in the above screenshot, you will not say that  ;)
You can read about it here
https://www.linuxtv.org/wiki/index.php/UpdateDVB
In order to make the application work, you must install the kernel in the link i posted.
I don't understand why you are against it, maybe there is something i should know so please tell me.

Beim ersten “make” wird nach dem Namen und der E-Mail-Adresse gefragt. Dies wird insbesondere benötigt, wenn man Änderungen einchecken möchte. Dann werden diese Informationen ins Logfile geschrieben.

I was not asked about any name or email, why?

clausmuus:
You do not have a physical PC inside the docker container, but you can use all functions of a linux system (debian) inside it. If you want to access the hardware of the host, you must make that available by additional docker create options.

By the way:
If you want to build a driver for the MLD system, you must give the build tool the path to the MLD kernel sources. You can find examples for that in some of the dvb-... packages (e.g. the dvb-dddvb package).

It is no problem to use an other kernel for the MLD. But the kernel must support some features as I describe before.

You will only be ask for you name and email if you build the whole MLD system. Since you build only one package, you will not asked.

Navigation

[0] Message Index

[#] Next page

[*] Previous page