Re: uname -v does not report an n-number
Date: Wed, 20 Aug 2025 18:40:17 UTC
On Wed, Aug 20, 2025 at 04:08:04PM +0000, Marcin Cieslak wrote: > On Wed, 20 Aug 2025, bob prohaska wrote: > > > I've an old Pi2 v1.1 which has been tracking -current for some time. > > > > uname -v reports > > bob@www:/usr/src % uname -v > > FreeBSD 15.0-PRERELEASE #100 main-325e0b4c1a68: Mon Aug 18 15:23:41 PDT 2025 bob@www.zefox.org:/usr/obj/usr/src/arm.armv7/sys/GENERIC > > bob@www:/usr/src % > > > > Can the older machine be persuaded to display the sequence number? > > Obviously I could reinstall, but I'm curious to see how long the > > original installation can last. > > > > Thanks for reading, > > > > bob prohaska > > On the machine where you build your kernel for "www": > > git -C /usr/src rev-parse --is-shallow-repository > > If your repository is shallow, it will not get an "n" number. > That's the problem, the reply is "true". > Whether having this is worth extra gigabytes on disk (git counts the number > of commits "since the beginning"), it's up to you. The machine has only a 32GB disk, df reports: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s2a 35532636 11410120 21279908 35% / devfs 1 0 1 0% /dev /dev/da0s1 51088 17348 33740 34% /boot/msdos so it appears I have about 20 GB available. IIRC it's possible to "set a depth", could it be set to some small number, like 1, 2 or maybe 3, so I get the N-number without all the baggage? Thanks for writing! bob prohaska > If you convert the repository to have all the commits, you need to rebuild the kernel. > Marcin