Re: Window Managers / Desktops
Just to thank everyone for their help & suggestions. It took me a couple of re-installs to get it right, but I'm sitting here at a nice icewm desktop writing an email in a ssh shell in xterm on NetBSD 8.1. I just got it running, so I need to install firefox, some text editor, etc, but the terminal works fine. Thanks, Clay Daniels clays.sh...@sdf.org SDF Public Access UNIX System - http://sdf.org
Re: Window Managers / Desktops
On Wed 13 Nov 2019 at 21:14:24 +, Clay Daniels wrote: > I'm new to NetBSD, coming from FreeBSD. I got tired of Google mail and found > a nice real unix shell/mail account at SDF.org. In the process it was > pointed out to me that they run their servers on NetBSD. So I've started on > a fresh install of NetBSD. I'm sure I did not make all the right choices in > the install, but it works and I found it easy to configure a ~/.xinitrc file > that loads the TDM Window Manager, you know the real primitave page with the I guess you mean TWM. NetBSD also comes with ctwm which is a development based on twm. Most notably it supports workspaces, but the version in pkgsrc is a bit newer than the version in base and also supports some of the Enhanced Window Manager Hints. -Olaf. -- Olaf 'Rhialto' Seibert -- rhialto at falu dot nl ___ Anyone who is capable of getting themselves made President should on \X/ no account be allowed to do the job. --Douglas Adams, "THGTTG" signature.asc Description: PGP signature
Re: [users] Window Managers / Desktops
I only use tiling wms. Awesome on Voidlinux running on top of musl-libC and spectrwm (configured with the same keybindings of Awesome) on NetBSD. Awesome started as a fork of dwm, but its today an advanced framework to develop and configure "your own" wm extensible with lua. spectrwm is simple to configure on the fly and has sane defaults. Perfect on a smaller screen where tiling layouts are kind of restricted. I'd recommend awesome if you want a feature rich, modular wm and spectrwm if you want to keep it simple, offering some flexibility. Den tors 14 nov. 2019 kl 15:06 skrev Luis P. Mendes : > Although not with NetBSD, as I only use NetBSD for non-X systems, up > until now, but after a lot of changes I, too, have settled with IceWM > for stack window managers, even after years of using fluxbox. > > Although I had it customized and working very well I was still looking > for something better. Better in the sense that I could arrange > windows more rapidly. > Thought of some manual tiling window managers until a person wrote a > message that made me think. He said that the arrangement of the > screen should be left to the window manager and that I could try dwm. > I did it and it's what I use nowadays. When I want to increase or > decrease the amount of screen state for some window it's fast to do > it, but many times it's not even necessary. > > Just my experience. > > -- > > > Luis Mendes > > > On 20191113 21:14:24 +, Clay Daniels wrote: > >I'm new to NetBSD, coming from FreeBSD. I got tired of Google mail and > >found a nice real unix shell/mail account at SDF.org. In the process > >it was pointed out to me that they run their servers on NetBSD. So > >I've started on a fresh install of NetBSD. I'm sure I did not make all > >the right choices in the install, but it works and I found it easy to > >configure a ~/.xinitrc file that loads the TDM Window Manager, you > >know the real primitave page with the 3 xterms & a clock. It's > >actually ok like that for a while, and the first thing I did was to > >ssh into sdf and write an email in good old Alpine to the guy who > >recommended sdf to me. > > > >Well, moving ahead, I've been reading the documentation, and used ftp > >to get the 2019Q3 pkgsrc. I look in /urs/pkgsrc/x11 and see the list > >of choices if I want to move beyond TDM, or maybe just improve on it a > >wee bit. I've intalled NetBSD on my older machine, a 2014 HP > >Pavillion, so I want a fairly light user of resources. I've got 465 Gb > >disk space, which is ok, but it's real slow compared to the new > >home-build Ryzen 7 3700x machine. On the other hand, the old machine > >at one time held three operating systems: Windows 10, MX Linux, and > >FreeBSD, using Rod Smith's Refind boot manager. Oh well, time marches > >on. > > > >My question is what x11 desktop / window manager would anyone recommend? > > > >Clay Daniels > > > >clays.sh...@sdf.org > >SDF Public Access UNIX System - http://sdf.org > >
Re: [users] Window Managers / Desktops
Although not with NetBSD, as I only use NetBSD for non-X systems, up until now, but after a lot of changes I, too, have settled with IceWM for stack window managers, even after years of using fluxbox. Although I had it customized and working very well I was still looking for something better. Better in the sense that I could arrange windows more rapidly. Thought of some manual tiling window managers until a person wrote a message that made me think. He said that the arrangement of the screen should be left to the window manager and that I could try dwm. I did it and it's what I use nowadays. When I want to increase or decrease the amount of screen state for some window it's fast to do it, but many times it's not even necessary. Just my experience. -- Luis Mendes On 20191113 21:14:24 +, Clay Daniels wrote: I'm new to NetBSD, coming from FreeBSD. I got tired of Google mail and found a nice real unix shell/mail account at SDF.org. In the process it was pointed out to me that they run their servers on NetBSD. So I've started on a fresh install of NetBSD. I'm sure I did not make all the right choices in the install, but it works and I found it easy to configure a ~/.xinitrc file that loads the TDM Window Manager, you know the real primitave page with the 3 xterms & a clock. It's actually ok like that for a while, and the first thing I did was to ssh into sdf and write an email in good old Alpine to the guy who recommended sdf to me. Well, moving ahead, I've been reading the documentation, and used ftp to get the 2019Q3 pkgsrc. I look in /urs/pkgsrc/x11 and see the list of choices if I want to move beyond TDM, or maybe just improve on it a wee bit. I've intalled NetBSD on my older machine, a 2014 HP Pavillion, so I want a fairly light user of resources. I've got 465 Gb disk space, which is ok, but it's real slow compared to the new home-build Ryzen 7 3700x machine. On the other hand, the old machine at one time held three operating systems: Windows 10, MX Linux, and FreeBSD, using Rod Smith's Refind boot manager. Oh well, time marches on. My question is what x11 desktop / window manager would anyone recommend? Clay Daniels clays.sh...@sdf.org SDF Public Access UNIX System - http://sdf.org
Re: pkgsrc net/mldonkey (is broken)
On 14/11/2019 01:01, Greg Troxel wrote: o I would say: if you download the upstream release corresponding to what's packaged, and build it from source, following its instructions, does it build and work? If not, upstream is broken, and you should address the problems there. Speaking as the OCaml guy (sort of) for pkgsrc, it looks like the latest stable release of mldonkey is five years old; that's a long time in the OCaml world. Along with Unison, mldonkey is one of the OCaml programs I don't use personally, so updates may not be as frequent as for, say, Coq. Looking at the PR, this seems to be about ocaml. ocaml seems to be a language family with effectively frequent changes in language specification. This in my view imposes a duty on programs that are written in ocaml to have new releases that are buildable with upcoming compiler versions, while still building with the old ones, and to have these new versions be sufficiently compatible that the updates are trivial. In practice, this doesn't happen :-( Now, one could argue that pkgsrc should have N versions of ocaml at once, and be able to build everything with different ones, like python. That's a vast amount of work, and if you want to start trying to support that in pkgsrc-wip, we hand out commit privileges there pretty easily. But really you are running into a problem in ocaml culture. Well put :) Some projects are really good about this, others, not so much. Over the last few years, quite a few improvements have been made in inserting layers between the compiler and the code so that there is a cushion for all-too-frequent changes in the internals. But breakage still occurs; the change from 4.07 to 4.08 was particularly painful, 4.09 (which is available in wip already) seems reasonably smooth so far (still working things out on that one). best Jaap
