From venture37 at gmail.com Mon Jun 1 18:02:33 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Mon, 1 Jun 2015 18:02:33 +0100 Subject: [Ukfreebsd] London BSD Pub meeting - May In-Reply-To: <20150528161053.GD451@halon.org.uk> References: <20150528161053.GD451@halon.org.uk> Message-ID: On 28 May 2015 at 17:10, Vassilis Laganakos wrote: > On Tue, May 26, 2015 at 09:52:30PM +0100, Sevan / Venture37 wrote: >> If that lot up there are going to have a meeting, so are we!, ours >> will be in a even smaller pub too! >> > Hahaha :) :o) > Hope you had a good time down there! Maybe we should arrange a common pub > night out ;) It was good to catch up with folks, we'd been slacking extra hard since the new year :) A common pub night out would be cool, somewhere around liverpool street or kings cross, right? Sevan From james at netinertia.co.uk Wed Jun 3 19:32:18 2015 From: james at netinertia.co.uk (James O'Gorman) Date: Wed, 3 Jun 2015 19:32:18 +0100 Subject: [Ukfreebsd] London BSD Pub meeting - May In-Reply-To: References: <20150528161053.GD451@halon.org.uk> Message-ID: <20150603183218.GB18317@netinertia.co.uk> On Mon, Jun 01, 2015 at 06:02:33PM +0100, Sevan / Venture37 wrote: > It was good to catch up with folks, we'd been slacking extra hard > since the new year :) > A common pub night out would be cool, somewhere around liverpool > street or kings cross, right? Having a regular day/date in the month might be good for getting people to come along, then people can plan for it. :-) Liverpool St or Kings X works for me. There's also some nice pubs south of the river in Southwark, but I know some people have a phobia of crossing the river ;-) James From venture37 at gmail.com Thu Jun 4 16:06:59 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Thu, 4 Jun 2015 16:06:59 +0100 Subject: [Ukfreebsd] London BSD Pub meeting - May In-Reply-To: <20150603183218.GB18317@netinertia.co.uk> References: <20150528161053.GD451@halon.org.uk> <20150603183218.GB18317@netinertia.co.uk> Message-ID: On 3 June 2015 at 19:32, James O'Gorman wrote: > On Mon, Jun 01, 2015 at 06:02:33PM +0100, Sevan / Venture37 wrote: >> It was good to catch up with folks, we'd been slacking extra hard >> since the new year :) >> A common pub night out would be cool, somewhere around liverpool >> street or kings cross, right? > > Having a regular day/date in the month might be good for getting people > to come along, then people can plan for it. :-) > > Liverpool St or Kings X works for me. There's also some nice pubs south > of the river in Southwark, but I know some people have a phobia of > crossing the river ;-) James, organise something :) Sevan From jon at axismilton.ltd.uk Thu Jun 11 14:41:04 2015 From: jon at axismilton.ltd.uk (Jon Schneider) Date: Thu, 11 Jun 2015 14:41:04 +0100 Subject: [Ukfreebsd] Filesystem behaviour on filling Message-ID: <9fb203b7f8009d07d822cc254905eb60.squirrel@mail.jschneider.net> Two years ago I posted about FreeBSD's unwillingness to clean up a known inconsistent filesystem but here's a related problem. In a Virtual(box) 10.1 installation with an emptyish 12GB I start filling a filesystem with cp /dev/zero huge & (cp uses 4k blocks by default) What I find is atrocious performance. I have checked using a W7 host, a Linux host and a Linux guest doing the same test. I would expect the thing to fill and cp to terminate with a message saying so. What in fact happens is on this 12GB filesystem I get bored and go to lunch. The virtualbox host isn't doing any significant I/O After lunch I find the cp still going, the console responsive to carriage returns but shell stuck executing a "ls -lth" I asked for before I went out. I appreciate it's a virtual machine but it would surely be equally bad using a network block device such as iSCSI. What is going on ? Jon From venture37 at gmail.com Thu Jun 11 15:32:49 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Thu, 11 Jun 2015 15:32:49 +0100 Subject: [Ukfreebsd] Filesystem behaviour on filling In-Reply-To: <9fb203b7f8009d07d822cc254905eb60.squirrel@mail.jschneider.net> References: <9fb203b7f8009d07d822cc254905eb60.squirrel@mail.jschneider.net> Message-ID: <55799C11.40900@gmail.com> On 11/06/2015 14:41, Jon Schneider wrote: > What is going on ? Have you tried experimenting with the different controller settings / type for the VM to see if that makes a difference? (you shouldn't need to because the template should set an optimum setting but for the sake of testing...) I'm running 10-RELEASE as a guest of OS X for basic testing, I'm just happy it doesn't reset on doing something like portsnap extract. I don't expect any performance out of it (though I don't expect crippling performance either). Sevan / Venture37 From jon at axismilton.ltd.uk Thu Jun 11 16:47:29 2015 From: jon at axismilton.ltd.uk (Jon Schneider) Date: Thu, 11 Jun 2015 16:47:29 +0100 Subject: [Ukfreebsd] Filesystem behaviour on filling In-Reply-To: <55799C11.40900@gmail.com> References: <9fb203b7f8009d07d822cc254905eb60.squirrel@mail.jschneider.net> <55799C11.40900@gmail.com> Message-ID: > Have you tried experimenting with the different controller settings / > type for the VM to see if that makes a difference? (you shouldn't need > to because the template should set an optimum setting but for the sake > of testing...) There's only AHCI for SATA and FreeBSD sees an ICH8M. It feels like a filesystem rather than block driver issue to me but I don't have a spare real (or differently virtualised) machine to try it on. Jon From justin at specialbusservice.com Fri Jun 12 11:44:38 2015 From: justin at specialbusservice.com (Justin Cormack) Date: Fri, 12 Jun 2015 11:44:38 +0100 Subject: [Ukfreebsd] Filesystem behaviour on filling In-Reply-To: References: <9fb203b7f8009d07d822cc254905eb60.squirrel@mail.jschneider.net> <55799C11.40900@gmail.com> Message-ID: On 11 June 2015 at 16:47, Jon Schneider wrote: >> Have you tried experimenting with the different controller settings / >> type for the VM to see if that makes a difference? (you shouldn't need >> to because the template should set an optimum setting but for the sake >> of testing...) > > There's only AHCI for SATA and FreeBSD sees an ICH8M. It feels like a > filesystem rather than block driver issue to me but I don't have a spare > real (or differently virtualised) machine to try it on. Well on digital ocean it took 4 minuets to run, filling the 20GB SSD on a fresh machine (you can get free credit with code freebsdnow to test it yourself). Yes, emulated hardware is often quite bad; changing the driver may help. PV Xen is much better than emulated hw, and I believe it is now supported with FreeBSD if you are using a Linux or NetBSD host, or try the new Xhyve if it is osx, which uses virtio drivers. Justin From venture37 at gmail.com Wed Jun 17 13:09:22 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Wed, 17 Jun 2015 13:09:22 +0100 Subject: [Ukfreebsd] BSDCan 2015 Message-ID: Videos are making their way onto youtube. Some of them are available here: https://www.youtube.com/playlist?list=PLWW0CjV-TafY0NqFDvD4k31CtnX-CGn8f Sevan / Venture37 From venture37 at gmail.com Wed Jun 17 13:31:59 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Wed, 17 Jun 2015 13:31:59 +0100 Subject: [Ukfreebsd] Talks instead of pub meets Message-ID: Hiya, Following on from talks at BSDCan on BUGs I was thinking about the feasibility of holding talks (monthly or bi-monthly) instead of just meeting up at the pub. Switching away from just a drinking club with a *BSD problem. There's enough of us playing around with stuff that it could be feasible. Maybe as a one off again to test? Thoughts? Sevan / Venture37 From david at cantrell.org.uk Wed Jun 17 14:33:29 2015 From: david at cantrell.org.uk (David Cantrell) Date: Wed, 17 Jun 2015 14:33:29 +0100 Subject: [Ukfreebsd] Talks instead of pub meets In-Reply-To: References: Message-ID: <20150617133329.GE24932@bytemark.barnyard.co.uk> On Wed, Jun 17, 2015 at 01:31:59PM +0100, Sevan / Venture37 wrote: > Following on from talks at BSDCan on BUGs I was thinking about the > feasibility of holding talks (monthly or bi-monthly) instead of just > meeting up at the pub. > > Switching away from just a drinking club with a *BSD problem. There's > enough of us playing around with stuff that it could be feasible. > Maybe as a one off again to test? London Perl Mongers - another drinking club with an IT-ish problem - has monthly boozing, and then roughly quarterly tech meets. It's a format that works well. The next tech meet is the 13th of August IIRC. London.pm also has occasional hack days, at which non-perl hacking is welcome. [CCed London.pm grand high panjandrum] -- David Cantrell You don't need to spam good porn From justin at specialbusservice.com Wed Jun 17 18:51:35 2015 From: justin at specialbusservice.com (Justin Cormack) Date: Wed, 17 Jun 2015 18:51:35 +0100 Subject: [Ukfreebsd] Talks instead of pub meets In-Reply-To: References: Message-ID: On 17 June 2015 at 13:31, Sevan / Venture37 wrote: > Hiya, > Following on from talks at BSDCan on BUGs I was thinking about the > feasibility of holding talks (monthly or bi-monthly) instead of just > meeting up at the pub. > > Switching away from just a drinking club with a *BSD problem. There's > enough of us playing around with stuff that it could be feasible. > Maybe as a one off again to test? > > Thoughts? It would be nice, but the apparent issue is that there is little commercial activity in BSD in London, so getting a venue is hard and getting people to talk about anything other than side projects is hard. The Joyent people have just started a very commercial meetup, as they want to sell Docker on SmartOS to people, but that is a different thing. (also organizing regular meetups is hard; I am about to restart London Lua after a coupleof years)... Justin From james at netinertia.co.uk Wed Jun 17 19:29:22 2015 From: james at netinertia.co.uk (James O'Gorman) Date: Wed, 17 Jun 2015 19:29:22 +0100 Subject: [Ukfreebsd] Talks instead of pub meets In-Reply-To: References: Message-ID: <20150617182922.GG18317@netinertia.co.uk> On Wed, Jun 17, 2015 at 06:51:35PM +0100, Justin Cormack wrote: > On 17 June 2015 at 13:31, Sevan / Venture37 wrote: > > Hiya, > > Following on from talks at BSDCan on BUGs I was thinking about the > > feasibility of holding talks (monthly or bi-monthly) instead of just > > meeting up at the pub. > > > > Switching away from just a drinking club with a *BSD problem. There's > > enough of us playing around with stuff that it could be feasible. > > Maybe as a one off again to test? > > > > Thoughts? > > It would be nice, but the apparent issue is that there is little > commercial activity in BSD in London, so getting a venue is hard and > getting people to talk about anything other than side projects is > hard. The Joyent people have just started a very commercial meetup, as > they want to sell Docker on SmartOS to people, but that is a different > thing. $dayjob is going to attempt to have space in our new office to be able to hold meetups. If we do manage this, I should be able to blag something. :-) > (also organizing regular meetups is hard; I am about to restart London > Lua after a coupleof years)... People at $dayjob might be interested in this too. :-) James From KevinO'Connor at merseyfire.gov.uk Thu Jun 18 14:51:02 2015 From: KevinO'Connor at merseyfire.gov.uk (O'Connor, Kevin) Date: Thu, 18 Jun 2015 13:51:02 +0000 Subject: [Ukfreebsd] uname -r issue Message-ID: <81C9CF72068BAA4C85C4FA6FF062C7B36776744F@MFRSEXCH-HQ.merseyfire.gov.uk> This is more of an annoyance than a technical issue but after a freebsd-update fetch install and several reboots uname -a is still reporting the previous build number on 10.1 release. According to the handbook uname -a gets it's information from /usr/src/sys/conf/newvers.sh. I've checked the file and it does indeed list it as RELEASE-p13 but uname -r is still showing p10 Anyone have an idea why the file is not getting read correctly, permissions are fine, or where the incorrect information is coming from? Having to parse the file newvers.sh on every server would be a bit of a pain. Regards Kevin This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the originator of the message. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Merseyside Fire & Rescue Service, (MFRS). Incoming and outgoing emails may be monitored in line with current legislation. Steps have been taken to ensure that this email and attachments are free from any virus. In keeping with good computing practice the recipient should ensure they are actually virus free. http://www.merseyfire.gov.uk/ From venture37 at gmail.com Thu Jun 18 15:23:52 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Thu, 18 Jun 2015 15:23:52 +0100 Subject: [Ukfreebsd] uname -r issue In-Reply-To: <81C9CF72068BAA4C85C4FA6FF062C7B36776744F@MFRSEXCH-HQ.merseyfire.gov.uk> References: <81C9CF72068BAA4C85C4FA6FF062C7B36776744F@MFRSEXCH-HQ.merseyfire.gov.uk> Message-ID: On 18 June 2015 at 14:51, O'Connor, Kevin wrote: > This is more of an annoyance than a technical issue but after a freebsd-update fetch install and several reboots uname -a is still reporting the previous build number on 10.1 release. > According to the handbook uname -a gets it's information from /usr/src/sys/conf/newvers.sh. > I've checked the file and it does indeed list it as RELEASE-p13 but uname -r is still showing p10 > > Anyone have an idea why the file is not getting read correctly, permissions are fine, or where the incorrect information is coming from? Having to parse the file newvers.sh on every server would be a bit of a pain. > > Regards > > Kevin Hi Kevin, uname gets its information from sysctl, newvers.sh is used when rolling a new kernel. https://svnweb.freebsd.org/base/head/usr.bin/uname/uname.c?revision=256557&view=markup Are you using a custom kernel? Have you rebooted since updating? What does dmesg or the contents of /var/run/dmesg.boot say the kernel version is? Sevan From venture37 at gmail.com Thu Jun 18 15:29:02 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Thu, 18 Jun 2015 15:29:02 +0100 Subject: [Ukfreebsd] Talks instead of pub meets In-Reply-To: References: Message-ID: On 17 June 2015 at 18:51, Justin Cormack wrote: > It would be nice, but the apparent issue is that there is little > commercial activity in BSD in London, so getting a venue is hard and > getting people to talk about anything other than side projects is > hard. The Joyent people have just started a very commercial meetup, as > they want to sell Docker on SmartOS to people, but that is a different > thing. Really not interested in marketing or commercial promotion. Focus is technical details :) From venture37 at gmail.com Thu Jun 18 15:30:53 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Thu, 18 Jun 2015 15:30:53 +0100 Subject: [Ukfreebsd] Talks instead of pub meets In-Reply-To: <20150617182922.GG18317@netinertia.co.uk> References: <20150617182922.GG18317@netinertia.co.uk> Message-ID: On 17 June 2015 at 19:29, James O'Gorman wrote: > $dayjob is going to attempt to have space in our new office to be able > to hold meetups. If we do manage this, I should be able to blag > something. :-) That would be really cool James! >> (also organizing regular meetups is hard; I am about to restart London >> Lua after a coupleof years)... > > People at $dayjob might be interested in this too. :-) :) Sevan From vsevolod at FreeBSD.org Thu Jun 18 15:27:44 2015 From: vsevolod at FreeBSD.org (Vsevolod Stakhov) Date: Thu, 18 Jun 2015 15:27:44 +0100 Subject: [Ukfreebsd] uname -r issue In-Reply-To: <81C9CF72068BAA4C85C4FA6FF062C7B36776744F@MFRSEXCH-HQ.merseyfire.gov.uk> References: <81C9CF72068BAA4C85C4FA6FF062C7B36776744F@MFRSEXCH-HQ.merseyfire.gov.uk> Message-ID: <5582D560.90005@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 18/06/2015 14:51, O'Connor, Kevin wrote: > This is more of an annoyance than a technical issue but after a > freebsd-update fetch install and several reboots uname -a is still > reporting the previous build number on 10.1 release. According to > the handbook uname -a gets it's information from > /usr/src/sys/conf/newvers.sh. I've checked the file and it does > indeed list it as RELEASE-p13 but uname -r is still showing p10 > > Anyone have an idea why the file is not getting read correctly, > permissions are fine, or where the incorrect information is coming > from? Having to parse the file newvers.sh on every server would be > a bit of a pain. uname utility performs the following step to get information: 1) Check environment variables in form 'UNAME_s'/'UNAME_r' and so on 2) If there is no such a variable, then uname tries to resolve information either via the corresponding sysctl (namely, kern.osrelease for -r flag) or via some other ways, such as getosreldate(3). Hence, if you have no specific environment variables then you might check your sysctl interface to query the kernel directly. newvers.sh is used merely for building system from the sources. But since you are using freebsd-update it doesn't seem like your case. - -- Vsevolod Stakhov -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJVgtVgAAoJEAdke2eQCBQ34ioQAMl4suGHS+10t4jEC5eHOrkw TBZ/S6u8rGRKNKaljO2qsTzwEKCtEyej0yKwcbCasIUwkxirR6coYY8IiQtiFh86 lLVq4jKLUgZW/UlqpnoewXLBcdShK4ykv6Nm8XTDNgJSUkypvFZ7yWxeSnjtTlJL uULs6hvL5Jh3n5I0r4hI3VELfLVjydr8PeT4BIqRzMLzIyOxi2W9E2ZRkpTidb0H 5LPcy1l8XhBFatstneBksPl5j7xQrzD1gaJsh/f5GNLqyCdRBrhyd04P4WmYdI4T Sy/HcWN5ZJ08m3HjhVUtGegg4ENlVRZDRn7Jf0eExdVObF96jHP44qjK37V+/Pqg 3Qf7QhOixlcoM38MLp0p/tOXlxep1WsuL3d4mDfJ5ETc1LS2io4wWsqxHhJEl7nj UmRM3SiS9RYtTJv4OwyqJNu61rOOp3z6c8CLV6BXWMN+NRiJlYutdDGJKT7+ezsh yerLUI66DsXyPfyZYya0MsWtzS+r0oBEDgWjCy+9eCCuKrLeor4l+TVrkDgsfWqI 2+v/SYkC0y6FXa5zNOToF1VQFltjizJ710KlhAdckfWfffijl+SuNkC4SdYiymi6 LujMt3Ntmbk+f98bd008XXfzSrASORJuZG7HFMyTfFEc+NCifCqwl5lRzoWsTwxZ E1o4gQZnXo5V85Gtkqe0 =n2Qi -----END PGP SIGNATURE----- From KevinO'Connor at merseyfire.gov.uk Thu Jun 18 16:13:54 2015 From: KevinO'Connor at merseyfire.gov.uk (O'Connor, Kevin) Date: Thu, 18 Jun 2015 15:13:54 +0000 Subject: [Ukfreebsd] uname -r issue In-Reply-To: References: <81C9CF72068BAA4C85C4FA6FF062C7B36776744F@MFRSEXCH-HQ.merseyfire.gov.uk> Message-ID: <81C9CF72068BAA4C85C4FA6FF062C7B3677674F0@MFRSEXCH-HQ.merseyfire.gov.uk> > -----Original Message----- > From: Ukfreebsd [mailto:ukfreebsd-bounces at uk.freebsd.org] On Behalf Of > Sevan / Venture37 > Sent: 18 June 2015 15:24 > To: UK FreeBSD Users > Subject: Re: [Ukfreebsd] uname -r issue > > On 18 June 2015 at 14:51, O'Connor, Kevin > wrote: > > This is more of an annoyance than a technical issue but after a freebsd- > update fetch install and several reboots uname -a is still reporting the > previous build number on 10.1 release. > > According to the handbook uname -a gets it's information from > /usr/src/sys/conf/newvers.sh. > > I've checked the file and it does indeed list it as RELEASE-p13 but > > uname -r is still showing p10 > > > > Anyone have an idea why the file is not getting read correctly, permissions > are fine, or where the incorrect information is coming from? Having to parse > the file newvers.sh on every server would be a bit of a pain. > > > > Regards > > > > Kevin > > Hi Kevin, > uname gets its information from sysctl, newvers.sh is used when rolling a > new kernel. > https://svnweb.freebsd.org/base/head/usr.bin/uname/uname.c?revision=2 > 56557&view=markup > Are you using a custom kernel? No just the standard generic kernel. I'm well aware the freebsd-update cannot rebuild a custom kernel. > Have you rebooted since updating? Several times. I've also re-run freebsd-update install (Nothing to update) and rebooted > What does dmesg or the contents of /var/run/dmesg.boot say the kernel > version is? Yes I should have said that is also reporting p10 > > > Sevan > I suppose it's remotely possible that as the generic kernel didn't need a rebuild it's still reporting the old one. I shall do a manual rebuild and see if that resolves the behaviour. Thanks Kevin This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the originator of the message. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Merseyside Fire & Rescue Service, (MFRS). Incoming and outgoing emails may be monitored in line with current legislation. Steps have been taken to ensure that this email and attachments are free from any virus. In keeping with good computing practice the recipient should ensure they are actually virus free. http://www.merseyfire.gov.uk/ From rwmaillists at googlemail.com Thu Jun 18 16:26:25 2015 From: rwmaillists at googlemail.com (RW) Date: Thu, 18 Jun 2015 16:26:25 +0100 Subject: [Ukfreebsd] uname -r issue In-Reply-To: <81C9CF72068BAA4C85C4FA6FF062C7B3677674F0@MFRSEXCH-HQ.merseyfire.gov.uk> References: <81C9CF72068BAA4C85C4FA6FF062C7B36776744F@MFRSEXCH-HQ.merseyfire.gov.uk> <81C9CF72068BAA4C85C4FA6FF062C7B3677674F0@MFRSEXCH-HQ.merseyfire.gov.uk> Message-ID: <20150618162625.70a8e92a@gumby.homeunix.com> On Thu, 18 Jun 2015 15:13:54 +0000 O'Connor, Kevin wrote: > I suppose it's remotely possible that as the generic kernel didn't > need a rebuild it's still reporting the old one. I shall do a manual > rebuild and see if that resolves the behaviour. There was some talk of changing the way this works, but otherwise it's really common. A lot of point releases don't touch the kernel. From vassilis at einval.com Thu Jun 18 20:43:59 2015 From: vassilis at einval.com (Vassilis Laganakos) Date: Thu, 18 Jun 2015 20:43:59 +0100 Subject: [Ukfreebsd] London BSD Pub meeting - May In-Reply-To: References: <20150528161053.GD451@halon.org.uk> Message-ID: <20150618194359.GE451@halon.org.uk> On Mon, Jun 01, 2015 at 06:02:33PM +0100, Sevan / Venture37 wrote: > On 28 May 2015 at 17:10, Vassilis Laganakos wrote: > > On Tue, May 26, 2015 at 09:52:30PM +0100, Sevan / Venture37 wrote: > >> If that lot up there are going to have a meeting, so are we!, ours > >> will be in a even smaller pub too! > >> > > Hahaha :) > > :o) > > > Hope you had a good time down there! Maybe we should arrange a common pub > > night out ;) > > It was good to catch up with folks, we'd been slacking extra hard > since the new year :) > A common pub night out would be cool, somewhere around liverpool > street or kings cross, right? > Yeah sounds cool! Maybe once every couple of months would be nice; what do people think about this? Cheers, Vassilis > > Sevan > _______________________________________________ > Ukfreebsd mailing list > Ukfreebsd at uk.freebsd.org > http://mailman.uk.freebsd.org/mailman/listinfo/ukfreebsd > UK BSD Groups http://www.bsdgroups.org.uk > Hosted by EXOnetric http://www.exonetric.net > -- ?Prediction is very difficult, especially if it's about the future.? ? Niels Bohr F5E2 30B5 72BB DB1E EB24 B06F 6986 DE46 E128 CC4A From vassilis at einval.com Thu Jun 18 21:03:23 2015 From: vassilis at einval.com (Vassilis Laganakos) Date: Thu, 18 Jun 2015 21:03:23 +0100 Subject: [Ukfreebsd] Cambridge BSD Pub evenings - June Message-ID: <20150618200323.GF451@halon.org.uk> Hello, It is time again for our monthly get together! So let's meet at Fort St George (http://www.fortstgeorge-cambridge.co.uk) next week at 19:00 on the 25th, hope for some good weather :) and discuss about having a standard pub to meet in Cambridge, the common pub night out with our friends in London, and any other suggestions (like having a tech meeting, that Sevan suggested). Hope to see you there! Cheers, Vassilis -- ?Prediction is very difficult, especially if it's about the future.? ? Niels Bohr F5E2 30B5 72BB DB1E EB24 B06F 6986 DE46 E128 CC4A From james at netinertia.co.uk Thu Jun 18 21:18:56 2015 From: james at netinertia.co.uk (James O'Gorman) Date: Thu, 18 Jun 2015 21:18:56 +0100 Subject: [Ukfreebsd] uname -r issue In-Reply-To: <20150618162625.70a8e92a@gumby.homeunix.com> References: <81C9CF72068BAA4C85C4FA6FF062C7B36776744F@MFRSEXCH-HQ.merseyfire.gov.uk> <81C9CF72068BAA4C85C4FA6FF062C7B3677674F0@MFRSEXCH-HQ.merseyfire.gov.uk> <20150618162625.70a8e92a@gumby.homeunix.com> Message-ID: <20150618201856.GH18317@netinertia.co.uk> On Thu, Jun 18, 2015 at 04:26:25PM +0100, RW wrote: > On Thu, 18 Jun 2015 15:13:54 +0000 > O'Connor, Kevin wrote: > > > I suppose it's remotely possible that as the generic kernel didn't > > need a rebuild it's still reporting the old one. I shall do a manual > > rebuild and see if that resolves the behaviour. > > There was some talk of changing the way this works, but otherwise it's > really common. A lot of point releases don't touch the kernel. /bin/freebsd-version was introduced to report the exact patch level. As others have stated, uname will only report the kernel patch level. % uname -r 10.1-RELEASE-p10 % freebsd-version 10.1-RELEASE-p13 James From justin at specialbusservice.com Thu Jun 18 22:10:55 2015 From: justin at specialbusservice.com (Justin Cormack) Date: Thu, 18 Jun 2015 22:10:55 +0100 Subject: [Ukfreebsd] London BSD Pub meeting - May In-Reply-To: <20150618194359.GE451@halon.org.uk> References: <20150528161053.GD451@halon.org.uk> <20150618194359.GE451@halon.org.uk> Message-ID: On 18 Jun 2015 20:44, "Vassilis Laganakos" wrote: > > On Mon, Jun 01, 2015 at 06:02:33PM +0100, Sevan / Venture37 wrote: > > On 28 May 2015 at 17:10, Vassilis Laganakos wrote: > > > On Tue, May 26, 2015 at 09:52:30PM +0100, Sevan / Venture37 wrote: > > >> If that lot up there are going to have a meeting, so are we!, ours > > >> will be in a even smaller pub too! > > >> > > > Hahaha :) > > > > :o) > > > > > Hope you had a good time down there! Maybe we should arrange a common pub > > > night out ;) > > > > It was good to catch up with folks, we'd been slacking extra hard > > since the new year :) > > A common pub night out would be cool, somewhere around liverpool > > street or kings cross, right? > > > Yeah sounds cool! Maybe once every couple of months would be nice; what do > people think about this? > Happy to also meet in Cambridge sometimes if it is near the station eg the Cambridge Blue... Justin From KevinO'Connor at merseyfire.gov.uk Fri Jun 19 07:46:51 2015 From: KevinO'Connor at merseyfire.gov.uk (O'Connor, Kevin) Date: Fri, 19 Jun 2015 06:46:51 +0000 Subject: [Ukfreebsd] uname -r issue In-Reply-To: <20150618201856.GH18317@netinertia.co.uk> References: <81C9CF72068BAA4C85C4FA6FF062C7B36776744F@MFRSEXCH-HQ.merseyfire.gov.uk> <81C9CF72068BAA4C85C4FA6FF062C7B3677674F0@MFRSEXCH-HQ.merseyfire.gov.uk> <20150618162625.70a8e92a@gumby.homeunix.com> <20150618201856.GH18317@netinertia.co.uk> Message-ID: <81C9CF72068BAA4C85C4FA6FF062C7B367767601@MFRSEXCH-HQ.merseyfire.gov.uk> > -----Original Message----- > From: Ukfreebsd [mailto:ukfreebsd-bounces at uk.freebsd.org] On Behalf Of > James O'Gorman > Sent: 18 June 2015 21:19 > To: UK FreeBSD Users > Subject: Re: [Ukfreebsd] uname -r issue > > On Thu, Jun 18, 2015 at 04:26:25PM +0100, RW wrote: > > On Thu, 18 Jun 2015 15:13:54 +0000 > > O'Connor, Kevin wrote: > > > > > I suppose it's remotely possible that as the generic kernel didn't > > > need a rebuild it's still reporting the old one. I shall do a manual > > > rebuild and see if that resolves the behaviour. > > > > There was some talk of changing the way this works, but otherwise it's > > really common. A lot of point releases don't touch the kernel. > > /bin/freebsd-version was introduced to report the exact patch level. As > others have stated, uname will only report the kernel patch level. > > % uname -r > 10.1-RELEASE-p10 > % freebsd-version > 10.1-RELEASE-p13 > > James So basically the documentation in the hand book is wrong when it states "However, freebsd-update will always update /usr/src/sys/conf/newvers.sh. The current patch level, as indicated by the -p number reported by uname -r, is obtained from this file". I wasn't aware of freebsd-version but that does give me exactly what I need. Thanks Kevin This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the originator of the message. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Merseyside Fire & Rescue Service, (MFRS). Incoming and outgoing emails may be monitored in line with current legislation. Steps have been taken to ensure that this email and attachments are free from any virus. In keeping with good computing practice the recipient should ensure they are actually virus free. http://www.merseyfire.gov.uk/ From venture37 at gmail.com Fri Jun 19 11:39:01 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Fri, 19 Jun 2015 11:39:01 +0100 Subject: [Ukfreebsd] Beri dmesg Message-ID: Hi, Anyone able to post a copy of the dmesg from the Beri tablet? Had a chance to play with one yesterday but didn't have any means of saving a copy there & then. It'd make a nice addition to the ones on http://dmesgd.nycbug.org/index.cgi Sevan / Venture37 From virtuallysue at gmail.com Fri Jun 19 15:39:58 2015 From: virtuallysue at gmail.com (Sue Spence) Date: Fri, 19 Jun 2015 15:39:58 +0100 Subject: [Ukfreebsd] Talks instead of pub meets In-Reply-To: <20150617133329.GE24932@bytemark.barnyard.co.uk> References: <20150617133329.GE24932@bytemark.barnyard.co.uk> Message-ID: On 17 June 2015 at 14:33, David Cantrell wrote: > On Wed, Jun 17, 2015 at 01:31:59PM +0100, Sevan / Venture37 wrote: > > > Following on from talks at BSDCan on BUGs I was thinking about the > > feasibility of holding talks (monthly or bi-monthly) instead of just > > meeting up at the pub. > > > > Switching away from just a drinking club with a *BSD problem. There's > > enough of us playing around with stuff that it could be feasible. > > Maybe as a one off again to test? > > London Perl Mongers - another drinking club with an IT-ish problem - has > monthly boozing, and then roughly quarterly tech meets. It's a format > that works well. The next tech meet is the 13th of August IIRC. > > London.pm also has occasional hack days, at which non-perl hacking is > welcome. > > London.pm has tried holding bi-monthly tech meets in the past, but found it was difficult to sustain that for very long. It doesn't take very long before you run out of speakers, talks time to organise things, etc. I have been to a few Milton Keynes PM social meetings in the past, and I liked that they used the same roomy Wetherspoons pub every time and combined with the local LUG. People with something interesting to show just brought it to the meeting with them. London PM hack days are bimonthly, since the London Hackspace calendar is open enough for me to do that (so far). Non-Perl hacking is perfectly fine, as Dave says. So far my only rule is that everyone attending is reasonably supportive of whatever anyone else is doing, and it hasn't been a problem. The August London PM tech meet is going to be something of a practice round for the European Perl conference. How about a BSD-themed Perl tech meeting after that? I'd probably try to have this in the autumn (Oct/Nov). Check http://london.pm.org to see/subscribe to our calendar. I use a meetup group to announce events as well: http://www.meetup.com/London-Perl-Mongers/ From james at netinertia.co.uk Fri Jun 19 23:11:32 2015 From: james at netinertia.co.uk (James O'Gorman) Date: Fri, 19 Jun 2015 23:11:32 +0100 Subject: [Ukfreebsd] uname -r issue In-Reply-To: <81C9CF72068BAA4C85C4FA6FF062C7B367767601@MFRSEXCH-HQ.merseyfire.gov.uk> References: <81C9CF72068BAA4C85C4FA6FF062C7B36776744F@MFRSEXCH-HQ.merseyfire.gov.uk> <81C9CF72068BAA4C85C4FA6FF062C7B3677674F0@MFRSEXCH-HQ.merseyfire.gov.uk> <20150618162625.70a8e92a@gumby.homeunix.com> <20150618201856.GH18317@netinertia.co.uk> <81C9CF72068BAA4C85C4FA6FF062C7B367767601@MFRSEXCH-HQ.merseyfire.gov.uk> Message-ID: <20150619221131.GI18317@netinertia.co.uk> On Fri, Jun 19, 2015 at 06:46:51AM +0000, O'Connor, Kevin wrote: > So basically the documentation in the hand book is wrong when it > states "However, freebsd-update will always update > /usr/src/sys/conf/newvers.sh. The current patch level, as indicated by > the -p number reported by uname -r, is obtained from this file". I suppose this falls down to semantics. freebsd-update will update newvers.sh when you have the src components installed. uname -r does indeed obtain the patch level from that file. The ambiguity is that freebsd-update updating newvers.sh won't necessarily affect uname -r if there weren't any kernel updates - or if you didn't manually recompile the kernel. Historically (pre-freebsd-update) the userland and kernel were generally guaranteed to be the same because patching involved recompiling from source and it was always advised to update kernel and world at the same time. James From rwatson at FreeBSD.org Sat Jun 20 22:03:52 2015 From: rwatson at FreeBSD.org (Robert N. M. Watson) Date: Sat, 20 Jun 2015 17:03:52 -0400 Subject: [Ukfreebsd] Beri dmesg In-Reply-To: References: Message-ID: <21193687-08CB-4195-8F7B-67779E7D67AB@FreeBSD.org> The below is not quite stock FreeBSD booting on BERI ? it?s CHERI-extended FreeBSD (CheriBSD). However, close enough for this purpose? Robert On 19 Jun 2015, at 06:39, Sevan / Venture37 wrote: > > Hi, > Anyone able to post a copy of the dmesg from the Beri tablet? Had a > chance to play with one yesterday but didn't have any means of saving > a copy there & then. > > It'd make a nice addition to the ones on http://dmesgd.nycbug.org/index.cgi > > > Sevan / Venture37 > _______________________________________________ > Ukfreebsd mailing list > Ukfreebsd at uk.freebsd.org > http://mailman.uk.freebsd.org/mailman/listinfo/ukfreebsd > UK BSD Groups http://www.bsdgroups.org.uk > Hosted by EXOnetric http://www.exonetric.net Consoles: altera jtag uart main(0, 0x90000000400004e0, 0x90000000400004e8, 0x980000000010a910 (0x3eeffc00)) FreeBSD/mips BERI loader, Revision 0.1 (rnw24 at zenith.cl.cam.ac.uk, Tue Apr 29 15:27:36 BST 2014) - /boot/kernel/kernel data=0x657e00+0x128ef0 syms=[0x8+0x7a418+0x8+0x6e33a] Hit [Enter] to boot immediately, or 1 2 3 sequence for command prompt. Booting [/boot/kernel/kernel]... Kernel entry at 0xffffffff80100160 Kernel args: (null) entry: platform_start() Using FDT at 0xffffffff806c01c0 from kernel cmd line: envp: bootinfo found at 0x980000000004da70 memsize = 0x3eeffc00 Cache info: picache_stride = 4096 picache_loopcount = 4 pdcache_stride = 4096 pdcache_loopcount = 4 cpu0: Unknown cid 0 processor v0.4 MMU: Standard TLB, 144 entries (4K 16K 64K 256K 1M 16M 64M 256M pg sizes) L1 i-cache: direct-mapped with 128 sets, 128 bytes per line L1 d-cache: direct-mapped with 128 sets, 128 bytes per line Config1=0x9e703848 Config3=0x80002000 Physical memory chunk(s): 0x881000 - 0x3eefffff, 1046999040 bytes (255615 pages) Maxmem is 0x3ef00000 pcpu is available at virtual address 0xc000000000000000. KDB: debugger backends: ddb KDB: current backend: ddb platform_cpu_mask: hardware has 1 cores with 1 threads each Copyright (c) 1992-2015 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #40 36225f5(master)-dirty: Sat Jun 20 14:11:57 UTC 2015 rnw24 at vica.cl.cam.ac.uk:/home/rnw24/obj/mips.mips64/home/rnw24/git/cheribsd/sys/CHERI_DE4_USBROOT mips gcc version 4.2.1 20070831 patched [FreeBSD] VT: init without driver. module_register: module atse/miibus already exists! Module atse/miibus failed to register: 17 real memory = 1055916032 (1031168K bytes) Physical memory chunk(s): 0x009a2000 - 0x3d564fff, 1018966016 bytes (248771 pages) avail memory = 1013612544 (966MB) CHERI: compiled for 256-bit capabilities ULE: setup cpu 0 random: entropy device infrastructure driver random: selecting highest priority adaptor mem: nfslock: pseudo-device crypto: null: openfirm: random: SOFT: yarrow init() random: selecting highest priority adaptor nexus0: ofwbus0: on nexus0 simplebus0: on ofwbus0 beripic0: mem 0x7f804000-0x7f8043ff,0x7f806000-0x7f80600f,0x7f806080-0x7f80608f,0x7f806100-0x7f80610f irq 0,1,2,3,4 on simplebus0 beripic0: config region at mem 0x7f804000-0x7f804400 beripic0: IP read region at mem 0x7f806000-0x7f806010 beripic0: IP set region at mem 0x7f806080-0x7f806090 beripic0: IP clear region at mem 0x7f806100-0x7f806110 simplebus0: no default resources for rid = 5, type = 1 beripic0: 64 hard and 64 soft sources beripic0: initial config: src 0: enabled tid: 0 hardintr 1 beripic0: initial config: src 1: enabled tid: 0 hardintr 2 beripic0: initial config: src 2: enabled tid: 0 hardintr 3 beripic0: initial config: src 5: enabled tid: 0 hardintr 1 beripic0: initial config: src 6: enabled tid: 0 hardintr 0 beripic0: initial config: src 11: enabled tid: 0 hardintr 4 beripic0: initial config: src 12: enabled tid: 0 hardintr 0 uart0: <16550 or compatible> mem 0x7f002100-0x7f00211f irq 6 (beripic0) on simplebus0 beripic0: mapping pin 6 to irq 0, tid 0 uart0: fast interrupt altera_jtag_uart0: mem 0x7f000000-0x7f00003f irq 0 (beripic0) on simplebus0 beripic0: mapping pin 0 to irq 1, tid 0 altera_jtag_uart1: mem 0x7f001000-0x7f00103f on simplebus0 simplebus0: no default resources for rid = 0, type = 1 altera_jtag_uart1: IRQ unavailable; selecting polled operation altera_jtag_uart2: mem 0x7f002000-0x7f00203f on simplebus0 simplebus0: no default resources for rid = 0, type = 1 altera_jtag_uart2: IRQ unavailable; selecting polled operation altera_sdcardc0: mem 0x7f008000-0x7f0083ff on simplebus0 altera_sdcardc0: 2021M SD Card inserted terasic_de4led0: mem 0x7f006000 on simplebus0 cfi0: mem 0x74000000-0x77ffffff on simplebus0 cfi0: [4x32KB,511x128KB] cfid0 on cfi0 atse0: mem 0x7f007000-0x7f0073ff,0x7f007500-0x7f007507,0x7f007520-0x7f00753f,0x7f007400-0x7f007407,0x7f007420-0x7f00743f irq 1,2 (beripic0) on simplebus0 atse0: MAC ctrl region at mem 0x7f007000-0x7f007400 atse0: RX FIFO at mem 0x7f007500-0x7f007508 atse0: RXC FIFO at mem 0x7f007520-0x7f007540 atse0: TX FIFO at mem 0x7f007400-0x7f007408 atse0: TXC FIFO at mem 0x7f007420-0x7f007440 miibus0: on atse0 e1000phy4: PHY 0 on miibus0 e1000phy4: OUI 0x000ac2, model 0x000c, rev. 2 e1000phy4: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseSX, 1000baseSX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto atse0: bpf attached atse0: Ethernet address: b6:a5:d1:d2:d2:85 beripic0: mapping pin 1 to irq 2, tid 0 beripic0: mapping pin 2 to irq 3, tid 0 atse1: mem 0x7f005000-0x7f0053ff,0x7f005500-0x7f005507,0x7f005520-0x7f00553f,0x7f005400-0x7f005407,0x7f005420-0x7f00543f irq 11,12 (beripic0) on simplebus0 atse1: MAC ctrl region at mem 0x7f005000-0x7f005400 atse1: RX FIFO at mem 0x7f005500-0x7f005508 atse1: RXC FIFO at mem 0x7f005520-0x7f005540 atse1: TX FIFO at mem 0x7f005400-0x7f005408 atse1: TXC FIFO at mem 0x7f005420-0x7f005440 atse1: Ethernet address not meeting our multi-MAC standards. Falling back to random hadware address. miibus1: on atse1 e1000phy5: PHY 1 on miibus1 e1000phy5: OUI 0x000ac2, model 0x000c, rev. 2 e1000phy5: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseSX, 1000baseSX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto atse1: bpf attached atse1: Ethernet address: 9e:19:c4:bf:57:e3 beripic0: mapping pin 11 to irq 4, tid 0 beripic0: mapping pin 12 to irq 0, tid 0 terasic_mtl0: mem 0x70400000-0x70400fff,0x70000000-0x70176fff,0x70177000-0x70178fff on simplebus0 terasic_mtl0: registers at mem 0x70400000-0x70401000 terasic_mtl0: pixel frame buffer at mem 0x70000000-0x70177000 terasic_mtl0: text frame buffer at mem 0x70177000-0x70179000 terasic_mtl0: rejecting invalid panel params width=800 height=480 terasic_mtl0: using default panel params fbd0 on terasic_mtl0 VT: initialize with new VT driver "fb". saf1761otg0: mem 0x7f100000-0x7f13ffff,0x7f140000-0x7f140003 irq 4,5 (beripic0) on simplebus0 beripic0: mapping pin 5 to irq 1, tid 0 usbus0 on saf1761otg0 saf1761otg0: usbpf: Attached altera_avgen0: mem 0x7f009000-0x7f009001 on simplebus0 berirom0: mem 0x7f00a000-0x7f00afff on simplebus0 berirom0: Built on 2015-06-10 at 13:36:14 (1433943374) berirom0: SVN revision: r18953 altera_avgen1: mem 0x7f00c000-0x7f00c007 on simplebus0 altera_avgen2: mem 0x7f00b080 on simplebus0 altera_avgen3: mem 0x7f00b000-0x7f00b007 on simplebus0 altpll0: mem 0x7f00e000-0x7f00efff on simplebus0 altpll0: registers at mem 0x7f00e000-0x7f00f000 pixelstream0: mem 0x7f00d000-0x7f00d027 on simplebus0 pixelstream0: registers at mem 0x7f00d000-0x7f00d028 pixelstream0: pixelstream vt(4) not selected by kern.vt.driver tunable clock0: on nexus0 Timecounter "MIPS32" frequency 100000000 Hz quality 800 Event timer "MIPS32" frequency 100000000 Hz quality 800 cryptosoft0: on nexus0 crypto: assign cryptosoft0 driver id 0, flags 100663296 crypto: cryptosoft0 registers alg 1 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 2 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 3 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 4 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 5 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 16 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 6 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 7 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 18 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 19 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 20 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 8 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 15 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 9 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 10 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 13 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 14 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 11 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 22 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 23 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 25 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 24 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 26 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 27 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 28 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 21 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 Device configuration finished. Timecounters tick every 5.000 msec crypto: tcp_init: net.inet.tcp.tcbhashsize auto tuned to 16384 lo0: bpf attached GEOM: new disk altera_sdcard0 GEOM: new disk cfid0 usbus0: 480Mbps High Speed USB v2.0 MAP: No valid partition found at altera_sdcard0 ugen0.1: at usbus0 uhub0: on usbus0 random: unblocking device. uhub0: 2 ports with 2 removable, self powered cfid0: slice 00000000-0001ffff: config (127KB) cfid0: slice 00020000-00c1ffff: fpga0 (12287KB) cfid0: slice 00c20000-0181ffff: fpga1 (12287KB) cfid0: slice 01820000-03fdffff: os (40703KB) cfid0: slice 03fe0000-03ffffff: boot (127KB) MAP: No valid partition found at cfid0 MAP: No valid partition found at cfid0s.config MAP: cfid0s.fpga0: 0xc00000, data=0xc00000 "/dev/map/fpga" MAP: No valid partition found at cfid0s.fpga1 MAP: cfid0s.os: 7e0000x1800000, data=0x1800000 "/dev/map/kernel" ugen0.2: at usbus0 uhub1: on usbus0 MAP: No valid partition found at cfid0s.boot Root mount waiting for: usbus0 uhub1: 3 ports with 3 removable, self powered Root mount waiting for: usbus0 Root mount waiting for: usbus0 ugen0.3: at usbus0 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0xc100 umass0:0:0: Attached to scbus0 Trying to mount root from ufs:/dev/da0 []... mountroot: waiting for device /dev/da0 ... pass0 at umass-sim0 bus 0 scbus0 target 0 lun 0 pass0: Removable Direct Access SPC-2 SCSI device pass0: Serial Number 001A4D5E84E6FE41594EB6EF pass0: 40.000MB/s transfers da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SPC-2 SCSI device da0: Serial Number 001A4D5E84E6FE41594EB6EF da0: 40.000MB/s transfers da0: 59006MB (120845300 512 byte sectors: 255H 63S/T 7522C) da0: quirks=0x3 da0: Delete methods: GEOM: new disk da0 MAP: No valid partition found at da0 warning: no time-of-day clock registered, system time will not be set accurately start_init: trying /sbin/init Setting hostuuid: edc4300a-f6e6-11e3-92f6-c5285a7fac82. Setting hostid: 0xb5ab46a9. No suitable dump device was found. Starting file system checks: /dev/da0: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0: clean, 59315721 free (553 frags, 7414396 blocks, 0.0% fragmentation) MAP: No valid partition found at da0 /dev/altera_sdcard0: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/altera_sdcard0: clean, 1365922 free (266 frags, 170707 blocks, 0.0% fragmentation) MAP: No valid partition found at altera_sdcard0 Mounting local file systems:. Writing entropy file:. Setting hostname: beri1. atse0: link state changed to DOWN atse0: link state changed to UP atse1: link state changed to DOWN Starting Network: lo0 atse0 atse1. lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 atse0: flags=8843 metric 0 mtu 1500 options=80048 ether b6:a5:d1:d2:d2:85 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active atse1: flags=8843 metric 0 mtu 1500 options=80048 ether 62:30:56:af:33:12 nd6 options=29 media: Ethernet autoselect (none) status: no carrier Starting devd. Starting dhclient. DHCPREQUEST on atse0 to 255.255.255.255 port 67 ip length 339 disagrees with bytes received 341. accepting packet with data after udp payload. DHCPACK from 128.232.18.7 bound to 128.232.18.71 -- renewal in 18000 seconds. Starting pflogd: add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Creating and/or trimming log files. Starting syslogd. ELF ldconfig path: /lib /usr/lib /usr/lib/compat Starting casperd. MAP: No valid partition found at md0 MAP: No valid partition found at md0 Clearing /tmp (X related). Updating motd:. Mounting late file systems:. Configuring syscons: blanktime. Performing sanity check on sshd configuration. Could not load host key: /etc/ssh/ssh_host_dsa_key Starting sshd. Could not load host key: /etc/ssh/ssh_host_dsa_key Starting cron. Starting de4_hdmi. Starting background file system checks in 60 seconds. atse0: flags=8843 metric 0 mtu 1500 options=80048 ether b6:a5:d1:d2:d2:85 inet 128.232.18.71 netmask 0xffffff00 broadcast 128.232.18.255 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active Wed Dec 31 03:29:01 UTC 2014 FreeBSD/mips (beri1) (ttyj0) login: From venture37 at gmail.com Sat Jun 20 22:16:40 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Sat, 20 Jun 2015 22:16:40 +0100 Subject: [Ukfreebsd] Beri dmesg In-Reply-To: <21193687-08CB-4195-8F7B-67779E7D67AB@FreeBSD.org> References: <21193687-08CB-4195-8F7B-67779E7D67AB@FreeBSD.org> Message-ID: On 20 June 2015 at 22:03, Robert N. M. Watson wrote: > The below is not quite stock FreeBSD booting on BERI ? it?s CHERI-extended FreeBSD (CheriBSD). However, close enough for this purpose? > > Robert Yes, thanks Robert :) http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2744 Sevan From venture37 at gmail.com Thu Jun 25 00:10:04 2015 From: venture37 at gmail.com (Sevan / Venture37) Date: Thu, 25 Jun 2015 00:10:04 +0100 Subject: [Ukfreebsd] Package mirrors Message-ID: Hi, The HardenedBSD project is looking for folks to mirror their 10-STABLE & 11-CURRENT pkg repos if anyone can help them out. https://hardenedbsd.org/article/shawn-webb/2015-06-24/seeking-package-mirrors Sevan / Venture37 From andrew at fubar.geek.nz Thu Jun 25 19:23:53 2015 From: andrew at fubar.geek.nz (Andrew Turner) Date: Thu, 25 Jun 2015 19:23:53 +0100 Subject: [Ukfreebsd] Cambridge BSD Pub evenings - June In-Reply-To: <20150618200323.GF451@halon.org.uk> References: <20150618200323.GF451@halon.org.uk> Message-ID: On 18 June 2015 21:03:23 BST, Vassilis Laganakos wrote: >Hello, > >It is time again for our monthly get together! > >So let's meet at Fort St George >(http://www.fortstgeorge-cambridge.co.uk) >next week at 19:00 on the 25th, hope for some good weather :) and >discuss >about having a standard pub to meet in Cambridge, the common pub night >out >with our friends in London, and any other suggestions (like having a >tech >meeting, that Sevan suggested). > >Hope to see you there! > >Cheers, >Vassilis > >-- > ?Prediction is very difficult, especially if it's about the future.? > ? Niels Bohr > > F5E2 30B5 72BB DB1E EB24 B06F 6986 DE46 E128 CC4A >_______________________________________________ >Ukfreebsd mailing list >Ukfreebsd at uk.freebsd.org >http://mailman.uk.freebsd.org/mailman/listinfo/ukfreebsd >UK BSD Groups http://www.bsdgroups.org.uk >Hosted by EXOnetric http://www.exonetric.net They have closed off part of the pub for midsummer fair so don't have any tables. We are moving to the Maypole. Andrew -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From jon at axismilton.ltd.uk Thu Jun 25 19:46:20 2015 From: jon at axismilton.ltd.uk (Jonathan Schneider) Date: Thu, 25 Jun 2015 19:46:20 +0100 Subject: [Ukfreebsd] Cambridge BSD Pub evenings - June In-Reply-To: References: <20150618200323.GF451@halon.org.uk> Message-ID: <32125534-0EB5-4EEB-977A-7F3537C42AB4@axismilton.ltd.uk> I would be there but am at a LISPy talk in town instead. Can we move the day around a bit please ? Jon On 25 Jun 2015, at 19:23, Andrew Turner wrote: > On 18 June 2015 21:03:23 BST, Vassilis Laganakos wrote: >> Hello, >> >> It is time again for our monthly get together! >> >> So let's meet at Fort St George >> (http://www.fortstgeorge-cambridge.co.uk) >> next week at 19:00 on the 25th, hope for some good weather :) and >> discuss >> about having a standard pub to meet in Cambridge, the common pub night >> out >> with our friends in London, and any other suggestions (like having a >> tech >> meeting, that Sevan suggested). >> >> Hope to see you there! >> >> Cheers, >> Vassilis >> >> -- >> ?Prediction is very difficult, especially if it's about the future.? >> ? Niels Bohr >> >> F5E2 30B5 72BB DB1E EB24 B06F 6986 DE46 E128 CC4A >> _______________________________________________ >> Ukfreebsd mailing list >> Ukfreebsd at uk.freebsd.org >> http://mailman.uk.freebsd.org/mailman/listinfo/ukfreebsd >> UK BSD Groups http://www.bsdgroups.org.uk >> Hosted by EXOnetric http://www.exonetric.net > > They have closed off part of the pub for midsummer fair so don't have any tables. We are moving to the Maypole. > > Andrew > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > Ukfreebsd mailing list > Ukfreebsd at uk.freebsd.org > http://mailman.uk.freebsd.org/mailman/listinfo/ukfreebsd > UK BSD Groups http://www.bsdgroups.org.uk > Hosted by EXOnetric http://www.exonetric.net