Re: 9.1-RCs issues
On Sunday 07 October 2012 01:42:33 Jin Guojun wrote: > 1) moused stops functioning on 9.1-RC2. Neither PS2 nor USB mouse can work. > 9.1-RC1 has no such problem. > > 2) All i386 / amd64 of 9.1-RC1/RC2 have USB read failure -- see dmesg > output at end of this email. > ada0 is internal SATA drive for system disk -- s# partitions: /, /tmp, > /var, /usr > s1 -- 6.4-Release > s2 -- 8.3-Release > s3 -- 9.1-RC2 amd64 > s4 -- 9.1-RC2 i386 -- This slice also contains /home > da0 is external USB2 drive (300GB) plugged in USB2 port -- mounted on /mnt > Regarding USB, it might be some patches did not reach it for the RC's. Have you tried 9-stable, or any 10-current snapshots? --HPS ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
machine/cpu.h in userland
I noticed that couple of our userland file include machine/cpu.h for no apparent
good reason. It looks like at least amd64 cpu.h has no userland serviceable
parts inside.
Maybe its content should be put under _KERNEL ?
Also:
--- a/sbin/adjkerntz/adjkerntz.c
+++ b/sbin/adjkerntz/adjkerntz.c
@@ -51,7 +51,6 @@ __FBSDID("$FreeBSD$");
#include
#include
#include
-#include
#include
#include "pathnames.h"
diff --git a/usr.bin/w/w.c b/usr.bin/w/w.c
index 8441ce5..9674fc2 100644
--- a/usr.bin/w/w.c
+++ b/usr.bin/w/w.c
@@ -57,7 +57,6 @@ static const char sccsid[] = "@(#)w.c 8.4 (Berkeley) 4/16/94";
#include
#include
-#include
#include
#include
#include
--
Andriy Gapon
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: 9.1-RCs issues
On Sunday 07 October 2012 12:42:11 Hans Petter Selasky wrote: > On Sunday 07 October 2012 01:42:33 Jin Guojun wrote: > > 1) moused stops functioning on 9.1-RC2. Neither PS2 nor USB mouse can > > work. > > > > 9.1-RC1 has no such problem. > > > > 2) All i386 / amd64 of 9.1-RC1/RC2 have USB read failure -- see dmesg > > output at end of this email. > > ada0 is internal SATA drive for system disk -- s# partitions: /, /tmp, > > /var, /usr > > > > s1 -- 6.4-Release > > s2 -- 8.3-Release > > s3 -- 9.1-RC2 amd64 > > s4 -- 9.1-RC2 i386 -- This slice also contains /home > > > > da0 is external USB2 drive (300GB) plugged in USB2 port -- mounted on > > /mnt > > Regarding USB, it might be some patches did not reach it for the RC's. Have > you tried 9-stable, or any 10-current snapshots? > > --HPS s/reach/make --HPS ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: machine/cpu.h in userland
On Sun, Oct 07, 2012 at 03:17:30PM +0300, Andriy Gapon wrote:
>
> I noticed that couple of our userland file include machine/cpu.h for no
> apparent
> good reason. It looks like at least amd64 cpu.h has no userland serviceable
> parts inside.
> Maybe its content should be put under _KERNEL ?
>
> Also:
>
> --- a/sbin/adjkerntz/adjkerntz.c
> +++ b/sbin/adjkerntz/adjkerntz.c
> @@ -51,7 +51,6 @@ __FBSDID("$FreeBSD$");
> #include
> #include
> #include
> -#include
> #include
>
> #include "pathnames.h"
> diff --git a/usr.bin/w/w.c b/usr.bin/w/w.c
> index 8441ce5..9674fc2 100644
> --- a/usr.bin/w/w.c
> +++ b/usr.bin/w/w.c
> @@ -57,7 +57,6 @@ static const char sccsid[] = "@(#)w.c 8.4 (Berkeley)
> 4/16/94";
> #include
> #include
>
> -#include
> #include
> #include
> #include
Both proposals are obviously fine. Some research with git blame traces
the include presence in the w.c to the 4.4 Lite import.
What I do not understand is why do you spam lists instead of
commmitting the obvious changes ?
pgpzUWzFXZ6GB.pgp
Description: PGP signature
Re: machine/cpu.h in userland
On 7 October 2012 10:11, Konstantin Belousov wrote: > What I do not understand is why do you spam lists instead of > commmitting the obvious changes ? It is not spam to ask for review. He was uncertain, and asked for some clarification. -- Eitan Adler ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: SMP Version of tar
I would be willing to work on a SMP version of tar (initially just gzip or something). I don't have the best experience in compression, and how to multi-thread it, but I think I would be able to learn and help out. gzip cannot - it is single stream. bzip2 - no idea grzip (from ports, i use it) - can be multithreaded as it packs using fixed large chunks. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: SMP Version of tar
On Oct 7, 2012, at 10:00 AM, Wojciech Puchar wrote: >> I would be willing to work on a SMP version of tar (initially just gzip or >> something). >> >> I don't have the best experience in compression, and how to multi-thread it, >> but I think I would be able to learn and help out. > > gzip cannot - it is single stream. gunzip commutes with cat, so gzip compression can be multi-threaded by compressing separate blocks and concatenating the result. For proof, look at Mark Adler's pigz program, which does exactly this. GZip decompression is admittedly trickier. > bzip2 - no idea bzip2 is block oriented and can be multi-threaded for both compression and decompression. Tim ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: SMP Version of tar
On Sun, 7 Oct 2012 19:00+0200, Wojciech Puchar wrote: > > I would be willing to work on a SMP version of tar (initially just gzip or > > something). > > > > I don't have the best experience in compression, and how to multi-thread it, > > but I think I would be able to learn and help out. > > gzip cannot - it is single stream. > > bzip2 - no idea Check out archivers/pbzip2. > grzip (from ports, i use it) - can be multithreaded as it packs using fixed > large chunks. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: SMP Version of tar
gzip cannot - it is single stream. gunzip commutes with cat, so gzip compression can be multi-threaded by compressing separate blocks and concatenating the result. right. but resulting file format must be different. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
