Re: Recommended desktop environment?
On 05.09.2018 12:04, Wean Irdeh wrote: Hi all mailing list members! What is your recommended desktop environment for NetBSD? I used xfce for years and I spend lot of time just rearranging window with the mouse pointer, positioning for example a Firefox window next to xterm terminals. I was getting mad! For 2 weeks I switched to i3w, a tilling wm. I fount it intuitive and I don't care anymore to window positioning. just my 2 cents -- xpetrl.
Re: Recommended desktop environment?
On Wed, 5 Sep 2018 17:31:00 +0200 Martin Husemann wrote: > On Wed, Sep 05, 2018 at 04:28:11PM +0100, Sad Clouds wrote: > > Which hardware platform? If it's x86 then anything you can find in > > pkgsrc will probably work. I tend to use xfce on x86, but on > > sparc64 it had issues, so I used simple window manager like > > windowmaker. > > FWIW, I am typing this on a sparc64 machine using XFce4 4.10 > (and yes, it had a few issues in the past but they should be resolved > now). > > Martin Sounds good, I'll give it another go at some point.
Re: Recommended desktop environment?
On Wed, Sep 05, 2018 at 05:04:08PM +0700, Wean Irdeh wrote: >Hi all mailing list members! What is your recommended desktop environment >for NetBSD? What do you mean by "for NetBSD"? I do not think (barring availability) OS has any bearing on choice of wm. "recommendation" is difficult. It's quite subjective. Personally I prefer ratpoison - irrespective of OS. Main reason is to get full screen applications free of pop up menace (with a certain rudeness setting). Mayuresh
Re: Recommended desktop environment?
On Wed, Sep 05, 2018 at 04:28:11PM +0100, Sad Clouds wrote: > Which hardware platform? If it's x86 then anything you can find in > pkgsrc will probably work. I tend to use xfce on x86, but on sparc64 it > had issues, so I used simple window manager like windowmaker. FWIW, I am typing this on a sparc64 machine using XFce4 4.10 (and yes, it had a few issues in the past but they should be resolved now). Martin
Re: Recommended desktop environment?
On Wed, 5 Sep 2018 17:04:08 +0700 Wean Irdeh wrote: > Hi all mailing list members! What is your recommended desktop > environment for NetBSD? Which hardware platform? If it's x86 then anything you can find in pkgsrc will probably work. I tend to use xfce on x86, but on sparc64 it had issues, so I used simple window manager like windowmaker. Not used Gnome and Kde for years, from what I remember they were just awful and bloated.
Re: Recommended desktop environment?
On Wed, Sep 5, 2018 at 3:09 AM Wean Irdeh wrote: > > Hi all mailing list members! What is your recommended desktop environment for > NetBSD? This should be fun. I'm way behind the times in this area. Way back in the early 2000s or so I was using KDE3 on NetBSD quite happily. I haven't used a desktop a whole lot since then for the usual boring reasons. I use blackbox if I need to use a desktop on any of the BSDs but it's not got a lot of features. It works fine though. Andy
Re: Recommended desktop environment?
Recomended, I don't know. Most probably you are going to get quite a lot of different answers here. But,... Personally, I only run awesome wm on my systems. Started using it a couple of years ago and can not think about using something else. If you're curious about it check my screenshots on https://unitedbsd.com/t/what-does-your-bsd-look-like-screen-shots/109/9 Regards Den ons 5 sep. 2018 12:09Wean Irdeh skrev: > Hi all mailing list members! What is your recommended desktop environment > for NetBSD?
Re: cvs broken pipe
On Wed, Sep 5, 2018 at 12:09 PM wrote: > Your PC close the connexion (FIN flag at 20:35:14.633195). > > Generaly, multiple lines with same ack and sequence may indicate packet loss. > It may also indicate a busy line or busy hosts on one end. Could it be that you need to lower MTU on the connection? -- Benny
Re: cvs broken pipe
> Le 5 sept. 2018 à 06:07, Germain Le Chapelain
> a écrit :
>
> On 09/04/18 15:06, Germain Le Chapelain wrote:
>> I will try another one as well as the tcp-dump.
>
> Well this is what I got:
>
> 20:35:14.631696 IP 192.168.0.129.58621 > anoncvs.netbsd.org.ssh: Flags [.],
> ack 89814420, win
> 14375, options [nop,nop,TS val 290 ecr 289], length 0
> 20:35:14.632415 IP anoncvs.netbsd.org.ssh > 192.168.0.129.58621: Flags [.],
> seq 89814420:89815868,
> ack 645939, win 4197, options [nop,nop,TS val 289 ecr 290], length 1448
> 20:35:14.632419 IP anoncvs.netbsd.org.ssh > 192.168.0.129.58621: Flags [.],
> seq 89815868:89817316,
> ack 645939, win 4197, options [nop,nop,TS val 289 ecr 290], length 1448
> 20:35:14.632423 IP anoncvs.netbsd.org.ssh > 192.168.0.129.58621: Flags [.],
> seq 89817316:89818764,
> ack 645939, win 4197, options [nop,nop,TS val 289 ecr 290], length 1448
> 20:35:14.632426 IP anoncvs.netbsd.org.ssh > 192.168.0.129.58621: Flags [.],
> seq 89818764:89820212,
> ack 645939, win 4197, options [nop,nop,TS val 289 ecr 290], length 1448
> 20:35:14.632429 IP anoncvs.netbsd.org.ssh > 192.168.0.129.58621: Flags [.],
> seq 89820212:89821660,
> ack 645939, win 4197, options [nop,nop,TS val 289 ecr 290], length 1448
> 20:35:14.632433 IP anoncvs.netbsd.org.ssh > 192.168.0.129.58621: Flags [.],
> seq 89821660:89823108,
> ack 645939, win 4197, options [nop,nop,TS val 289 ecr 290], length 1448
> 20:35:14.632454 IP 192.168.0.129.58621 > anoncvs.netbsd.org.ssh: Flags [.],
> ack 89817316, win
> 14075, options [nop,nop,TS val 290 ecr 289], length 0
> 20:35:14.632466 IP 192.168.0.129.58621 > anoncvs.netbsd.org.ssh: Flags [.],
> ack 89820212, win
> 13713, options [nop,nop,TS val 290 ecr 289], length 0
> 20:35:14.632477 IP 192.168.0.129.58621 > anoncvs.netbsd.org.ssh: Flags [.],
> ack 89823108, win
> 13351, options [nop,nop,TS val 290 ecr 289], length 0
> 20:35:14.632496 IP 192.168.0.129.58621 > anoncvs.netbsd.org.ssh: Flags [.],
> ack 89823108, win
> 14375, options [nop,nop,TS val 290 ecr 289], length 0
> 20:35:14.633184 IP anoncvs.netbsd.org.ssh > 192.168.0.129.58621: Flags [.],
> seq 89823108:89824556,
> ack 645939, win 4197, options [nop,nop,TS val 289 ecr 290], length 1448
> 20:35:14.633188 IP anoncvs.netbsd.org.ssh > 192.168.0.129.58621: Flags [.],
> seq 89824556:89826004,
> ack 645939, win 4197, options [nop,nop,TS val 289 ecr 290], length 1448
> 20:35:14.633191 IP anoncvs.netbsd.org.ssh > 192.168.0.129.58621: Flags [.],
> seq 89826004:89827452,
> ack 645939, win 4197, options [nop,nop,TS val 289 ecr 290], length 1448
> *20:35:14.633195 IP anoncvs.netbsd.org.ssh > 192.168.0.129.58621: Flags
> [FP.], seq
> 89830348:89830816, ack 645939, win 4197, options [nop,nop,TS val 289 ecr
> 290], length 468**
> *20:35:14.633215 IP 192.168.0.129.58621 > anoncvs.netbsd.org.ssh: Flags [.],
> ack 89826004, win
> 14075, options [nop,nop,TS val 290 ecr 289], length 0
(...)
> 20:42:41.865753 IP 192.168.0.129.58621 > anoncvs.netbsd.org.ssh: Flags [.],
> seq 646451:646463, ack
> 89827452, win 14437, options [nop,nop,TS val 1184 ecr 289,nop,nop,sack 1
> {89830348:89830817}],
> length 12
> 20:43:45.903023 IP 192.168.0.129.58621 > anoncvs.netbsd.org.ssh: Flags [R.],
> seq 651663, ack
> 89827452, win 14437, options [nop,nop,sack 1 {89830348:89830817}], length 0
>
> I have no idea what to make of that .
Your PC close the connexion (FIN flag at 20:35:14.633195).
Generaly, multiple lines with same ack and sequence may indicate packet loss.
It may also indicate a busy line or busy hosts on one end.
But I would rather look for something wrong in your PC:
- Do you have the same result with
CVSROOT="anon...@anoncvs3.de.netbsd.org:/cvsroot » ?
- Add "-t" to your cvs update command to see more about cvs exchanges
> Now I am doing a tcpdump -w
> :|
>
> Kind regards;
>
> --
> Germain Le Chapelain
> Director / Software Engineer
> Lanvaux Computer Games Limited
> http://lanvaux.fr
Recommended desktop environment?
Hi all mailing list members! What is your recommended desktop environment for NetBSD?
