Bug#800844: ITP: bhyve -- hypervisor/virtual machine manager for FreeBSD

2015-10-04 Thread Christoph Egger 
Package: wnpp
Severity: wishlist
Owner: Christoph Egger 

* Package name: bhyve
  Version : 10.2
  Upstream Author : FreeBSD Foundation
* URL : http://bhyve.org/
* License : BSD
  Programming Lang: C / ASM
  Description : hypervisor/virtual machine manager for FreeBSD

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-04 Thread Steven Chamberlain 
Hi,

Matthias Klose wrote:
> question to the Hurd and KFreeBSD maintainers ... change that on
> these platforms too?

I have a fanatical preference for compatibility over performance.  So
I prefer not to lose support for 586, but I don't know how practical
it would be for libc maintainers to do that only for kfreebsd.

kfreebsd-i386 has 686 (with SMP) and 486 kernel flavours.

If maybe package libc0.1-i686 had to go away, then I'd still prefer we
target 586 by default.  (For some reason, the kfreebsd installer is
failing to install that package when it should;  I forgot to install it
on all my 686s).

I'd be curious to see numbers showing the performance impact, though.

I have some of these around for testing on;  I think this device was
manufactured as 'recently' as 2006.  It is similar to the Soekris which
can still be purchased new:

cpu0: Geode(TM) Integrated Processor by National Semi ("Geode by NSC" 
586-class) 333 MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,PGE,CMOV,MMX,MMXX,3DNOW2,3DNOW

kfreebsd-i386's particular niche is supporting ancient platforms like
these and making them still useful.  And that would be especially
important to me, if Debian GNU/Linux (and Ubuntu, Fedora etc.) no longer
worked on them.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-04 Thread Axel Beckert 
Hi,

Ben Hutchings wrote:
> We propose to drop support for i386 processors older than 686-class in
> the current release cycle.  This would include folding libc6-i686 into
> libc6, changing the default target for gcc, and changing the 586 kernel
> flavour to 686 (non-PAE).

Please don't. It already hurt that i486 support was dropped with
Jessie and i468SX (Vortex86 SX, http://www.vortex86.com/?p=145) with
IIRC Wheezy.

> Since the 686-class, introduced with the Pentium Pro, is now almost 20
> years old, we believe there are few Debian systems still running that
> have 586-class or hybrid processors.  The only such processors
> apparently still available for sale are the DM&P Vortex86 family, Intel
> Quark and Xeon Phi, of which we currently only support the Vortex86.

I own several of Vortex86 based machines and we also have some at work
as backend for some 40" displays which show upcoming events running
iceweasel in fullscreen mode and ratpoison as invisible window
manager, running Debian:
https://people.phys.ethz.ch/~abe/MicroClientJr/ (texts in German)

I also have a Thinkpad 760ED (Pentium 1) running Debian 8 Jessie. With
self-compiled X driver (xserver-xorg-video-trident), because it was
unfortunately RM'ed for no real reason (no RC bugs, nothing, the new
upstream releases still compile and work fine on Jessie) and I noticed
it only after the Jessie release.

> Indeed, the likely reasons for users to choose i386 over amd64 today
> are to reduce memory consumption or to run i386 binaries for which the
> source is not available - not because they're using 32-bit processors.

That's what x32 is meant for. Please keep i386 for legacy hardware and
propagate x32 for such purposes.

> * Can require user intervention to install optimised library packages
>   e.g. debootstrap does not install libc6-i686

That's a debootstrap issue then IMHO.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-04 Thread Mats Erik Andersson 
Söndag den 4:e october 2015, klockan 11:55, skrev Steven Chamberlain:
> 
> I have a fanatical preference for compatibility over performance.  So
> I prefer not to lose support for 586, but I don't know how practical
> it would be for libc maintainers to do that only for kfreebsd.
> 
> kfreebsd-i386 has 686 (with SMP) and 486 kernel flavours.
> 
> cpu0: Geode(TM) Integrated Processor by National Semi ("Geode by NSC" 
> 586-class) 333 MHz
> cpu0: FPU,DE,PSE,TSC,MSR,CX8,PGE,CMOV,MMX,MMXX,3DNOW2,3DNOW
> 
> kfreebsd-i386's particular niche is supporting ancient platforms like
> these and making them still useful.  And that would be especially
> important to me, if Debian GNU/Linux (and Ubuntu, Fedora etc.) no longer
> worked on them.

The PC Engines ALIX systems (http://www.pcengines.ch/alix.htm) are
still very much commercial. One system, presently running FreeBSD
in a very reliable manner, reports

  CPU: Geode(TM) Integrated Processor by AMD PCS (498.06-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x5a2  Family = 0x5  Model = 0xa  Stepping = 2
  Features=0x88a93d
  AMD Features=0xc040
  real memory  = 268435456 (256 MB)
  avail memory = 235163648 (224 MB)

It would be a sad thing to loose the possibility for running
contemporary Debian on such a system!

Best regards,
  Mats Erik Andersson

Bug#800897: ITP: zxcvbn.js -- JavaScript password strength estimator

2015-10-04 Thread Luke Faraone 
Package: wnpp
Severity: wishlist
Owner: Luke Faraone 

* Package name: zxcvbn.js
  Version : 3.5.0
  Upstream Author : Dan Wheeler 
* URL : https://github.com/dropbox/zxcvbn
* License : Expat
  Programming Lang: JavaScript
  Description : JavaScript password strength estimator

zxcvbn is a password strength estimator inspired by password crackers.
Through pattern matching and conservative entropy calculations, it
recognizes and weighs 10k common passwords, common names and surnames
according to US census data, popular English words, and other common
patterns like dates, repeats (aaa), sequences (abcd), keyboard patterns
(qwertyuiop), and l33t speak.

Motiviation for the design can be found detailed at:
   

zxcvbn detects and supports CommonJS (node, browserify) and AMD
(RequireJS). In the absence of those, it adds a single function
zxcvbn() to the global namespace.

NB: This is my first time packaging a JavaScript/AMD/Node package,
so I will probably be reaching out to the Debian JS maintainers for
help :)

Bug#800897: duplicate of Bug#726171 (ITP: libjs-zxcvbn -- realistic password strength estimation)

2015-10-04 Thread Ben Finney 
Control: forcemerge 726171 -1

On 04-Oct-2015, Luke Faraone wrote:

> NB: This is my first time packaging a JavaScript/AMD/Node package,
> so I will probably be reaching out to the Debian JS maintainers for
> help :)

Thanks for the interest in packaging this library.

I have packaged it and am awaiting a sponsor, see Bug#726171 and
Bug#747032. I look forward to working with you on this!

-- 
 \   “Imagine a world without hypothetical situations.” —anonymous |
  `\   |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-04 Thread Guillem Jover 
On Thu, 2015-10-01 at 19:15:54 +0200, Matthias Klose wrote:
> question to the Hurd and KFreeBSD maintainers ... change that on these
> platforms too?

As it currently stands, this is not a question when it comes to
dpkg, that specific change is all or nothing. The Debian ←→ GNU
cpu mapping is global for all architectures.

But as I've mentioned several times now, I think changing the GNU
triplet (only on i386) every time we bump the ISA is the wrong way
around this, and the above is another reason of why, but this has
been ignored in the past so… you'll have to sort this out.

Thanks,
Guillem

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-04 Thread Ben Hutchings 
On Sun, 2015-10-04 at 15:03 +0200, Axel Beckert wrote:
> Hi,
> 
> Ben Hutchings wrote:
> > We propose to drop support for i386 processors older than 686-class in
> > the current release cycle.  This would include folding libc6-i686 into
> > libc6, changing the default target for gcc, and changing the 586 kernel
> > flavour to 686 (non-PAE).
> 
> Please don't. It already hurt that i486 support was dropped with
> Jessie and i468SX (Vortex86 SX, http://www.vortex86.com/?p=145) with
> IIRC Wheezy.
[...]

I stopped reading here because this is incorrect (by 2 releases).

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.

signature.asc
Description: This is a digitally signed message part