OSS (Open Source Software) BOM list for L4T 21.5

Robotics & Edge Computing Jetson & Embedded Systems Jetson TK1
1

Can nVidia provide the OSS BOM for L4T 21.5? Our software is developed based on L4T 21.5 for TK1 and I need sort out a full OSS BOM list based on it, it should include name, version, license type/revision and source (download URL) at least, thanks in advance.

2

Hi jianhui.chen,

Please check Licenses section from L4T documention - [url]http://developer.nvidia.com/embedded/dlc/l4t-Jetson-TK1-Driver-Package-Documents-R21-5[/url]

Thanks

3

Hi Kayccc,
Thanks a lot for your information!
I have see the comment under “Sample File System”:

The license agreement for each software component is located in the software component’s source code, made available from the same location from which this software was downloaded, or by request to oss-requests@nvidia.com.

Does it mean that we have to sort out the OSS BOM list one by one ourselves? or there is another way to get it conveniently? thanks.
Best regards,
Jianhui

4

Just FYI, the sample root file system is purely Ubuntu. I saw a useful URL on looking at licensing for Ubuntu:
https://askubuntu.com/questions/247757/how-do-you-find-the-licenses-for-everything-installed-on-your-system?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa

Basically it uses the “copyright” file of each package. You can list all copyright files of “.deb” installs via:

find /usr/share/doc -maxdepth 2 -iname "*copyright*"

The excerpt from the URL I see which creates “licenses.txt” in the home directory for any “.deb” package (https://askubuntu.com/a/247793/477031) is:

$ packages=`dpkg --get-selections | awk '{ print $1 }'`
$ for package in $packages; do echo "$package: "; cat /usr/share/doc/$package/copyright; echo ""; echo ""; done > ~/licenses.txt

I’m not sure if the Linux kernel itself is in there somewhere (the kernel has a package when upgraded by some mechanisms, but may not have a package when bare metal on an embedded system), but that is always available in the source of the kernel. Some additional notes here:
https://en.wikipedia.org/wiki/Linux_kernel#Licensing_terms

EDIT: It was pointed out that some of the systems which still have annoying issues with the package signature or date errors complaining that it needs to be adjusted. If you have issues with errors try this which uses “cut” (thanks @Honey_Patouceul):

packages=`dpkg --get-selections | awk '{ print $1 }' <b>| cut -d':' -f1</b>`