Shortlist of unstable and stable distributions


#1

I’d like to compile a shortlist.

Time of the build of the kernel; git revision; whether it became stable; its DRM patch level.

For starters:


2017-01-06 19:28:21f92c24b – unstable? – DRM patch level unknown

2017-02-05 13:22:4727d3221 (2017-02-05 13:10 GMT) – stable – DRM patch level unknown

2017-02-20 18:07:509b5e7d8 (2017-02-19 18:30 GMT) – unstable – DRM patch level unknown

2017-02-21 23:42:39a7f7424 (2017-02-21 22:23 GMT) – stable – DRM patch level unknown

2017-02-25 05:22:572dc2a76 (2017-02-25 03:41 GMT) – unstablehttps://github.com/trueos/freebsd/commit/67f2c8dd57d954980eddcefe37afd880145ce123


Any others?

References

In Stack Overflow: the accepted answer to Understanding uname output


#2

Nice. This will be helpful for me as well. I have all the ISOs for stable builds archived for sure. For drm patchlevel are you just looking for drm 4.9, or what are you looking for there?


#3

Chat: https://gitter.im/trueos/troubleshooting?at=58b2bff9567b0fc8138eadf1


Repeating updates (unstable)?
#4

2017-02-28 16:23:55b3d5020 (2017-02-28 15:26 GMT) – unstableb3d5020


#5

suggestion. Just add to your first post? maybe easier to read


#6

Thanks Rod, I agree (I had the same thought before posting) but it was too late.

When I find somewhere more suitable to maintain the shortlist, I’ll add a link.


#7

taken from the ABOUT command

STABLE:
** Wed 2017 Jun 21 01:09:23 UTC – ac2f0aa3b
Mon 2017 Apr 17 18:50:02 UTC - 6a971c9a - STABLE
2017 Mar 30 18:18:02 UTC - d44fdf245 - STABLE
2017-02-21 23:42:39 – a7f7424 (2017-02-21 22:23 GMT) – STABLE

UNSTABLE:
*** Thu 2017 Oct 19 19:19:04 UTC- 5e243190c - trueos-master

Sat 2017 Oct 14 20:33:43 UTC - 88c007ae5
Fri 2017 Sep 22 13:48:41 UTC - 2a2a3070d - drm-next
Mon 2017 Sep 18 15:04:04 UTC - 075edd7be - drm-next
Mon 2017 Aug 14 14:53:32 UTC - 334f3850a - drm-next
2017 Jul 28 21:44:30 UTC - 57b410cea - drm-next
Sat 2017 Jun 24 21:47:25 UTC - 2b3a1daf1 - drm-next
Wed 2017 Jun 21 01:09:23 UTC – ac2f0aa3b
Mon 2017 May 29 20:21:45 UTC - d7b9fac18
Mon 2017 May 29 20:21:45 UTC - d7b9fac18
Fri 2017 May 26 02:33:05 UTC 6c08c7b9a
Mon 2017 Apr 17 18:50:02 UTC - 96a971c9a - UNSTABLE - drm-next
2017 Mar 30 18:18:02 UTC - d44fdf245 - UNSTABLE
Mon 2017 Mar 27 14:32:11 UTC - 831f60b42 - UNSTABLE
2017 Mar 17 20:51:29 UTC - 1eae0fde0 - UNSTABLE


#9

https://github.com/trueos/trueos-core/issues/1453


#10

I’ve browsed the github issue. I’m not sure the source packages is the way to go (it’s a bit of an rpm-ism) since it’s all built from the github sources. The uname -a command includes the github revision for building the kernel. Do a checkout to that revision from a clone (or do a download from the github at that revision) and there you are.

If you are building third-party kernel modules, you should try to set them up as a port, then it should just get picked up with all the other ports when they are rebuilt for a release and pkg will do the rest. Developing a kernel module not ready for general consumption? Well, if you doing it against -CURRENT (or TrueOS UNSTABLE), you are going to be following the source. (My assumption, since FreeBSD’s ABI doesn’t change in -RELEASE/-STABLE, but does change often in -CURRENT).

Could the repositories on github have tags to make this a bit simpler to follow (especially for the ports tree)? I believe it could. The good part is that—aside from using the github repos—the directions for building kernels and ports yourself follow the FreeBSD handbook and do work (from personal experience).


#11

twschulz

Thanks for pointing out that uname -a gives the kernel github revision - I’d not noticed that. That mostly solves my issue but it would still be nice if it was scripted although it would be a very simple script.


#12

The latest UNSTABLE is in the wild. time to upgrade

that time again


Managing packages from the command line
#13

#14

#15

#16