Recommended Posts

  • 3 weeks later...

It looks like we have got different packages format in DSM 7.0.  Previously I can open the package via 7Zip. But right now I doesn't. Also DSM 6.2.3 can't import the new package(SynologyPhoto, etc...) - I have receive the new message: Invalid file format

Link to post
Share on other sites
10 hours ago, T-REX-XP said:

Previously I can open the package via 7Zip. But right now I doesn't.

it still looks similar to a tar file, the content of the file "INFO" can be read at the beginning, looks like the data between the file content is altered, maybe they just did a slight mod of tar where the metadata is "customized"

there needs to be a program that unpacks the new spk's and if they used tar then i guess they would need to publish the source (like with the kernel ...)

  • Thanks 1
Link to post
Share on other sites
On 12/11/2020 at 7:51 PM, Aigor said:

Have you read DSM spk build manual ? 

no, i did not expect them to have anything new as they did not publish new stuff for ages (last thing was about 6.0) and seem to be more secretive then open (like not publishing source code or only when threatened)

so i guess there should be at least beta kernel source soon

 

edit:

looke like thats the interesting part of the git

https://github.com/SynologyOpenSource/pkgscripts-ng/tree/DSM7.0

 

its still a tar from the "pkg_util.sh"

...
pkg_make_package() { # <source path> <dest path>
	local source_path=$1
	local dest_path=$2
	local package_name="package.tgz"
	local temp_extractsize="extractsize_tmp"
	local pkg_size=
	local tar_option="cJf"

	# check parameters
	if [ -z "$source_path" -o ! -d "$source_path" ]; then
		pkg_warn "pkg_make_package: bad parameters, please set source dir"
		return 1
	fi
	if [ -z "$dest_path"  -o ! -d "$dest_path" ]; then
		pkg_warn "pkg_make_package: bad parameters, please set destination dir"
		return 1
	fi

	# add extractsize to INFO
	pkg_size=`du -sk "$source_path" | awk '{print $1}'`
	echo "${pkg_size}" >> "$dest_path/$temp_extractsize"
	echo ls $source_path \| tar $tar_option "$dest_path/$package_name" -C "$source_path" -T /dev/stdin
	ls $source_path | tar $tar_option "$dest_path/$package_name" -C "$source_path" -T /dev/stdin
}
...
  
  pkg_make_spk() { # <source path> <dest path> <spk file name>
	local pack="tar cf"
	local source_path=$1
	local dest_path=$2
	local info_path="$source_path/INFO"
	local spk_name=$3
	local spk_arch=
	local temp_extractsize="extractsize_tmp"

	# check parameters
	if [ -z "$source_path" -o ! -d "$source_path" ]; then
		pkg_warn "pkg_make_spk: bad parameters, please set source dir"
		return 1
	fi
	if [ -z "$dest_path"  -o ! -d "$dest_path" ]; then
		pkg_warn "pkg_make_spk: bad parameters, please set destination dir"
		return 1
	fi

	# check INFO exists and source INFO
	if [ ! -r "$info_path" ]; then
		pkg_warn "pkg_make_spk: INFO '$info_path' is not existed"
		return 1
	fi
	spk_name=${3:-`pkg_get_spk_name $info_path`}
	# add extractsize to INFO
	pkg_size=`cat $source_path/$temp_extractsize`
	echo "extractsize=\"${pkg_size}\"" >> $info_path
	rm "$source_path/$temp_extractsize"

	echo "toolkit_version=\"$DSM_BUILD_NUM\"" >> $info_path
	echo "create_time=\"$(date +%Y%m%d-%T)\"" >> $info_path

	# tar .spk file
	pkg_log "creating package: $spk_name"
	pkg_log "source:           $source_path"
	pkg_log "destination:      $dest_path/$spk_name"
	$pack "$dest_path/$spk_name" -C "$source_path" $(ls $source_path)
  
  ...
  

 

anyway as long as there is no new loader there is no need for new drivers or source code

 

the package format does not bother my atm but that part  fom the 7.0 pdf might worry some people thinking it would be a option to change to 7.0 if there is a loader, looks like no old package can be installed

 

...
Runtime Requirements
If your package is for DSM6 then you should have a DSM6 NAS.
If your package is for DSM7 then you should have a DSM7 NAS.
Package for DSM6 is not compatible with DSM7
...

 

edit2:

just in case if someone wants to download the beta *.pat files ... but there is no way of using them with the existing loader

(the path is easy to guess and if you know the build number like 41222 provided above ...)

https://archive.synology.com/download/DSM/beta/7.0/41222/DSM_DS3615xs_41222.pat
https://archive.synology.com/download/DSM/beta/7.0/41222/DSM_DS3617xs_41222.pat

https://archive.synology.com/download/DSM/beta/7.0/41222/DSM_DS918+_41222.pat

 

 

 

Edited by IG-88
Link to post
Share on other sites
  • 4 weeks later...
On 12/11/2020 at 9:36 PM, IG-88 said:

just in case if someone wants to download the beta *.pat files ... but there is no way of using them with the existing loader

(the path is easy to guess and if you know the build number like 41222 provided above ...)

https://archive.synology.com/download/DSM/beta/7.0/41222/DSM_DS3615xs_41222.pat
https://archive.synology.com/download/DSM/beta/7.0/41222/DSM_DS3617xs_41222.pat

https://archive.synology.com/download/DSM/beta/7.0/41222/DSM_DS918+_41222.pat

 

 

 

So what the Russian guy wrote some posts ago about DSM 7 installed in his NAS was fake or what?

Link to post
Share on other sites
1 hour ago, Cr4z33 said:

So what the Russian guy wrote some posts ago about DSM 7 installed in his NAS was fake or what?

It was virtual DSM. You also can try to install it on your xpenology.

Link to post
Share on other sites
  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.