The nosh package is now up to version 1.40 .
*
http://jdebp.eu./Softwares/nosh/
*
http://jdebp.info./Softwares/nosh/
*
https://github.com/freebsd/freebsd-quarterly/blob/master/2018q4/nosh.md
This version sees changes to the doco, improvements to network
configuration
The nosh package is now up to version 1.39 .
* http://jdebp.eu./Softwares/nosh/
*
https://www.freebsd.org/news/status/report-2017-07-2017-09.html#The-nosh-Project
* http://jdebp.info./Softwares/nosh/
I missed announcing 1.38, so this announcement will cover both versions.
These versions
The blue/green problem only manifested itself with certain terminal
types, which I was not regularly using.
Since you have 1.39 built, and as long as you built from today's
snapshot, you can be the second person in the world to enjoy this:
while true ; do printf '\f' ; top -b -n 1 | sed
Guillermo:
The combination of vboxvideo with |console-fb-realizer| was explosive,
I got a (guest) kernel panic.
|console-fb-realizer| does not employ the arcana of framebuffer I/O, it
just using little more than the mode setting API and memory mapped I/O,
so I'm initially going to lay that
Hello,
So, I've gotten around to testing user-space VTs with nosh tools on
Gentoo, as described in the nosh Guide. Mostly console-fb-realizer,
but I also tested console-termio-realizer on a kernel VT for
comparison. This was in a VirtualBox VM, so there were two framebuffer
devices available
2018-07-01 8:38 GMT-03:00 Jonathan de Boyne Pollard:
>
> For the sake of other readers: note that it is not the build system that
> employs the wall program. (That would be bizarre.) It is the shutdown
> program, at runtime, as described in its manual.
Yep, that is a runtime dependency rather
ent values of those fields.
They are used by redo to build some service bundle directories (nosh's
native format of a 'service definition') and components of the
configuration import subsystem, and are detailed in the aforementioned
"Packages and Ports" chapter of the nosh Guide. If you
Guillermo:
*
There is a |curses.h| file in both Void's 'standard' headers
directory and in a subdirectory named '|ncursesw|' (for the narrow
character and wide character versions of the library,
respectively). Normally, that would be |/usr/include/curses.h| and
| program. (That would be bizarre.) It is the
|shutdown| program, at runtime, as described in its manual. This is not
a requirement specific to the nosh toolset's |shutdown| program. The old
|shutdown| program in FreeBSD and OpenBSD has the same requirement, for
example, as did the |shutdown
As someone porting to another operating system, you need also to pull up
the /_nosh Guide_/ <http://jdebp.info./Softwares/nosh/guide.html> and
read the _Packages and Ports_ chapter. There is a section in that
chapter of things that require attention (in addition to figuring out
your ope
Guillermo writes:
> Hi,
>
> The nosh-1.37 source package? If you unpacked the source tarball in a
> directory named 'nosh-1.37', you have a 'source' and a 'package'
> subdirectory, you ran package/compile, but it *did not* create a
> subdirectory named 'build', then, as peop
Hi,
2018-06-30 5:44 GMT-03:00 Chris Brannon:
>
> When I run package/compile from the root of the unpacked source tree, I
> get:
> redo: ERROR: all: Cannot find .do file to use.
>
> -- Chris
The nosh-1.37 source package? If you unpacked the source tarball in a
directory name
Chris Brannon:
When I run package/compile from the root of the unpacked source tree,
I get:
redo: ERROR: all: Cannot find .do file to use.
You need to make your operating system POSIX-conformant. I make fairly
liberal use of some standard utilities in the build process including
|pax
On Sat, Jun 30, 2018 at 01:44:45AM -0700, Chris Brannon wrote:
> When I run package/compile from the root of the unpacked source tree, I
> get:
> redo: ERROR: all: Cannot find .do file to use.
>
> -- Chris
Do you have pax installed? As I recall, not having pax is a common
stumbling block when
2018-03-11 20:57 GMT-03:00 Jonathan de Boyne Pollard:
>
> The macro generates no warning in the GNU C library in Debian 9, but I
> should have caught that overload that was not passing by reference. It is
> fixed now, thank you. The in-development source archive for 1.38 is in the
> usual place.
The macro generates no warning in the GNU C library in Debian 9, but I
should have caught that overload that was not passing by reference. It
is fixed now, thank you. The in-development source archive for 1.38 is
in the usual place.
be just on the shoulders of the person doing the porting to
the operating system in question and making the relevant operating
system packaging.
There's one more to go. Have a look at the Packages and Ports chapter
on the copy of the nosh Guide on the WWW site. (I might move this doco.)
2018-02-20 16:13 GMT-03:00 Jonathan de Boyne Pollard:
>
> Guillermo:
>>
>> redo-ifchange[2]: ERROR: services/dbus-broker.service: Not done.
>> redo-ifchange[2]: ERROR: services/dbus-daemon.service: Not done.
>> redo-ifchange[2]: ERROR: services/system-wide.conf: Not done.
>> redo-ifchange[2]:
It isn't very portable. But you are
> misidentifying what it is.
> [...]
> Guillermo:
>
>> Additionally, the convert/per-user/*.do scripts' 'read_os' function calls
>> 'exec' via absolute path /bin/exec instead of relative path ../../exec,
>> which is not go
:
Additionally, the convert/per-user/*.do scripts' 'read_os' function
calls 'exec' via absolute path /bin/exec instead of relative path
../../exec, which is not going to work if nosh isn't already installed
(chicken and egg).
There's no chicken and egg problem. The external formats
2018-02-18 3:49 GMT-03:00 Jonathan de Boyne Pollard:
>
> The nosh package is now up to version 1.37 .
> [...]
>Per-user management has been augmented, finally fixing the problem
>of |system-control| locating the per-user manager by giving the
>per-user manager an
*' [-fpermissive]
>s = tigetstr(setaf);
> [...]
> This is on CentOS7 build platform.
This should be fixed in nosh 1.37. So, unless there were other
compiler errors (warnings are nonfatal), nosh binaries should now
build on CentOS too.
G.
The nosh package is now up to version 1.37 .
*
http://jdebp.eu./Softwares/nosh/
*
https://www.freebsd.org/news/status/report-2017-07-2017-09.html#The-nosh-Project
*
http://jdebp.info./Softwares/nosh/
Some of the changes in this release are works in progress, that you will
see
On Thu, 18 Jan 2018, Guillermo wrote:
> And
>
> $ grep 'define NCURSES_CONST' /usr/include/curses.h
>
> probably says:
>
> #define NCURSES_CONST /*nothing*/
>
> Correct?
Correct.
bash-4.2$ grep 'define NCURSES_CONST' /usr/include/curses.h
#define NCURSES_CONST /*nothing*/
bash-4.2$
On Tue, 16 Jan 2018, Jonathan de Boyne Pollard wrote:
> This is a problem that I thought was confined to OpenBSD, and its
> not-|const|-correct ncurses library. Certainly this has never been a problem
> on Debian nor on FreeBSD, and M. Caravia did not report any lack of
> |const|-correctness on
Guillermo:
Jonathan de Boyne Pollard:
What does line 843 of your |/usr/include/curses.h| actually say?
Because that's not the location of that function declaration in that
header in either Dickey ncurses or Acton pdcurses as far as I can
see. So what curses are you actually using?
Dickey
2018-01-16 17:51 GMT-03:00 Jonathan de Boyne Pollard:
>
> Charlie Brady:
>
>> /usr/include/curses.h:843:31: error: initializing argument 1 of 'char*
>> tigetstr(char*)' [-fpermissive]
>>
>> service-status.cpp:148:21: error: invalid conversion from 'const char*' to
>> 'char*' [-fpermissive]
>>
OK, with pax installed, but gets a lot further.
Now seeing these many times:
/usr/include/curses.h:843:31: error: initializing argument 1 of 'char*
tigetstr(char*)' [-fpermissive]
service-status.cpp:148:21: error: invalid conversion from 'const char*' to
'char*' [-fpermissive]
s =
On Mon, 15 Jan 2018, Charlie Brady wrote:
> > 1) package/compile: you'll need "redo" to build
>
> Sorry, doesn't work for me:
>
> bash-4.2$ package/compile
> redo: ERROR: all: Cannot find .do file to use.
> bash-4.2$ sh -ex package/compile
> + '[' '!' -d package ']'
> + '[' '!' -d source ']'
The nosh package is now up to version 1.36 .
*
http://jdebp.eu./Softwares/nosh/
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
*
http://jdebp.info./Softwares/nosh/
More Java tools
This release comes with the |find-default-jvm| and |find
For a wider readership:
>
> I recently had issues where Firefox and the SpaceFM file manager would
> hang when started. Apparently they were calling dbus-launch.
>
If they were calling dbus-launch, that means that they were unable to contact a
Desktop Bus broker and tried to run their own
Hello,
Integration for nosh service management has been added to the "system"
modules of Ansible's development branch[1].
The nosh module can set running and enabled state for user or
system-wide services[2], in a similar fashion to other service
management modules.
Testin
Guillermo:
>
> So, system-control has a new but undocumented 'is-service-manager-client'
> subcommand?
>
Yes. It's part of an incomplete to-do list item; and might change.
Suggestions are welcome. You can put them on the Supervision mailing list if
you like. Please bear in mind the design principles laid out in the Guide
http://jdebp.eu./Softwares/nosh/guide.html , though.
Bug reports and real world experiences are also welcome, and in fact more
interesting
Hi,
2017-07-05 17:41 GMT-03:00 Jonathan de Boyne Pollard:
>
> The nosh package is now up to version 1.34 .
So, system-control has a new but undocumented
'is-service-manager-client' subcommand?
G.
The nosh package is now up to version 1.34 .
* http://jdebp.eu./Softwares/nosh/
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
* http://jdebp.info./Softwares/nosh/
Once again, there are a few more service bundles. The most interesting ones in
this version
Talking of Gentoo, Guillermo:
The Gentoo people have been inspired by Archnosh, but it looks like they could
benefit from your experience.
* https://wiki.gentoo.org/wiki/Nosh
2017-04-09 16:52 GMT-03:00 Jonathan de Boyne Pollard:
>
> The nosh package is now up to version 1.33 .
>
> [...]
>
> More packages
> -
>
> There are now four more -shims packages, for commands whose names conflict
> with
> commands from other package
e:
versiontag=1.2.3
git archive --format=tar --prefix=nosh-${versiontag}/ ${versiontag} | gzip
-n9 > nosh-${versiontag}.tgz
hth,
--dkg
I purge the directories of these from time to time, as I have just done again.
But they tend to very slowly accrue, for one reason or another. It's not a
major worry. Anyway, better that the archive have everything including some
harmless text editor temporary files than that it have one vital
Hello,
The archnosh repository[1] provides the build files necessary to
integrate the nosh[2] system and service manager with Archlinux package
management, as of version 1.33[3].
The nosh toolset is part of the daemontools family of managers, several
of which are already packaged[4
Guillermo:
One could instead attach controllers to the hierarchy rooted in
/sys/fs/cgroup/systemd, for example by mounting it with 'mount -t
cgroup -o cpu,name=systemd cgroup /sys/fs/cgroup/systemd' (not with
system-manager as process 1), and things would appear to be OK:
It's tempting to
not quite sure how that
interacts with nosh.
This is a good example for general consumption.
The maintenance script for the package is trying to enable the "sysstat"
service using the "update-rc.d" command. You've installed the shim for
this command from the nosh-debi
Someone:
I am trying to create one or multiple packages for Archlinux to
install nosh
This has come up several times with multiple people, now.
I have no Arch Linux machines, and I am entirely dependent from Arch
Linux people for the packaging part. As I already told one person back
2017-01-22 14:29 GMT-03:00 Guillermo:
>
> $ tai64nlocal /run/system-manager/log/current
> [...]
> 2017-01-21 22:11:17.709678664 system-manager: ERROR:
> /sys/fs/cgroup/systemd//cgroup.subtree_control: No such file or
> directory
> 2017-01-21 22:11:17.709683364 system-manager: ERROR:
>
The nosh package is now up to version 1.30 .
* http://jdebp.eu./Softwares/nosh/
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
* http://jdebp.info./Softwares/nosh/
service bundles
---
As usual, there are more service bundles, including
Guillermo:
for some reason 'service-control --exit' doesn't unload a service that
is already in the 'stopped' state.
I'll look into it for 1.31. You won't see a fix in 1.30 because that is
coming out ... well ... now.
Hello,
2016-08-06 14:30 GMT-03:00 Jonathan de Boyne Pollard:
>
> svc -x
> ==
>
> The -x option to service-control, a.k.a. svc, is no longer defunct. It does
> what unload-when-stopped does.
There is a minor difference: for some reason 'service-control --exit'
doesn't unload a service that is
I understand your point. But it is not practical, as it requires users
to become system administrators, which makes no sense. I am not
speaking of access rights in the operating system, but of the
knowledge and experience that is required by user to set such a
service.
While it may be easy for
Jean Louis:
So, placing user daemons into system supervision may not be the best
option, due to so many customization that have to be done for the
user, especially for GNU Emacs -- as one cannot know which programming
languages and their variables are required.
I just explained that these
Bloody Thunderbird! Here's that again, I hope without the surprise
reformatting after pressing "send" this time:
The nosh package is now up to version 1.29.
* http://jdebp.eu./Softwares/nosh/
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Proje
probably successfully get nosh service management, UCSPI support,
and log management working on Ubuntu on Windows NT; although obtaining
an actual daemon context is still problematic.
(https://news.ycombinator.com/item?id=11416376)
Moreover: UbuntuBSD and Debian FreeBSD shouldn't have
>
> I'm going to be very naughty and patch 1.28 post-release. It's a minor
> change.
>
I've changed my mind. I'm going to point the two of you at a potential version
1.29 and see how you get on.
This is because I have ended up doing slightly more than a 2-line script patch.
Hi,
2016-08-06 14:30 GMT-03:00 Jonathan de Boyne Pollard:
>
> The nosh package is now up to version 1.28 .
Could the plain 'setlock' invocation in script source/default.html.do
be changed to './exec setlock', as in scripts source/default.1.do and
source/default.8.do, please? Otherwise w
The nosh package is now up to version 1.28 .
* https://jdebp.eu./Softwares/nosh/
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
* http://jdebp.info./Softwares/nosh/
There's a lot in this one: MySQL and MariaDB changes; more prophylaxis
for Desktop Bus bus
about the MySQL/MariaDB changes. Enjoy a peek at one of the
new pages already written:
*
http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/italics-in-manuals.html
Guillermo:
So, the convert-systemd-units tool recognizes the systemd 'StandardInput=tty'
unit file directive, and translates it to a vc-get-tty + open-controlling-tty
sequence in the 'run' file of the generated bundle directory. Which does more
than just redirecting stdin to the appropriate
The nosh package is now up to version 1.27 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
In fact, it is soon to be version 1.28. This is a somewhat delayed
notice for 1.27
The nosh package is now up to version 1.25 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
As you may have noticed from discussions elsewhere, a new
oom-kill-protect utility has
.
As Guillermo said, the instructions for building from source are right
there on the WWW pages whence one downloads the source package.
*
http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/source-package.html
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/redo.html
Thanks Guillermo and Jonathan, your tips got me where I needed to be.
--
fREW Schmidt
https://blog.afoolishmanifesto.com
Nosh only has binaries compiled for 64 bit and my linode is sadly
still 32 bit. So I'm trying to build nosh for 32 bit, but I'm running
into trouble.
First off, there's no README or anything, so I sorta have to guess.
I tried running source/all.do and got an error about about
redo-ifchange
Guillermo:
It seems that the 'unload-when-stopped' and 'version' subcommands of
system-control are not mentioned in the documentation.
They both should be. I've added the latter to the doco ready for the
next version. The former I'm wavering about. I've had a to-do item for
some time to
Guillermo:
So I looked at the source/targets/virtualbox-host.target file from
which the bundle is created, and, IMHO, there are some issues with it.
That's not surprising. Running as a virtualbox host is not something
that is well tested. As you can see from the roadmap WWW page, there
2015-12-17 10:50 GMT-03:00 Jonathan de Boyne Pollard:
>
> The nosh package is now up to version 1.23 .
Hi,
It seems that the 'unload-when-stopped' and 'version' subcommands of
system-control are not mentioned in the documentation. They are listed
in the output of 'system-control --help',
The nosh package is now up to version 1.23 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
There is one major item in this release.
* I've adjusted console-fb-realizer's keyboard
On 2015-11-05 01:29, Guillermo wrote:
So problem solved. Thank you, this is a major improvement.
Brill. Thank you for the confirmation.
2015-07-06 22:01 GMT-03:00 Guillermo:
>
> I wanted to try out nosh daemontools-style, i.e. using
> service-dt-scanner and launching service-manager "by other means"
> [...]
> However, under certain circumstances service-dt-scanner receives a
> SIGABRT signal and dies
The nosh package is now up to version 1.22 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
There are several things in this release:
* a new binary package for FreeBSD
The nosh package is now up to version 1.21 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
console-terminal-emulator now has a mouse input event protocol, and
speaks both the DEC VT Locator protocol and the xterm Private Mode 1006
protocol over the terminal
Joe Maloney:
do you have a source code repository somewhere for nosh?
*
http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/source-package.html
The source package and how to build from source are here.
Guillermo:
Hi, I had some issues with the source package I thought I should mention:
As I said I intended to a while back, I incorporated fixes for these
into version 1.20. This is now out.
The nosh package is now up to version 1.20 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
It's worth noting that the WWW site has gained some more pages, an
installation how-to and a quick look at user-space virtual terminals.
*
http://homepage.ntlworld.com
Guillermo:
Colin Booth:
As it stands, nosh is playing in the same space as upstart, launchd, and
systemd.
If you don't look too closely, you could also say nosh without the userspace
terminal and login services stuff more or less covers the same ground as s6,
s6-rc and a small subset
Colin Booth:
I mean't more in the "one stop low-level system management" sense.
Also in the design of the nosh unit files (which may be a case of
parallel evolution, my knowledge of the history of nosh is limited at
best). Pholosophicaly it's definitely coming from the daemont
2015-08-22 15:04 GMT-03:00 Jonathan de Boyne Pollard:
>
> nosh is now up to version 1.19
Hi, I had some issues with the source package I thought I should mention:
* source/common-manager.cpp wouldn't compile on my Gentoo system,
because this new version calls setrlimit(), and makes use of
Guillermo:
Have you ever considered just writing a BSD backend using kqueue /
kevent, and a Linux backend using epoll / inotify or whatever native
Linux mechanism is available to suit nosh's needs? I believe you
mentioned there's quite a few conditional compilation already to work
around
/master/src/linux/platform.c#l181
nosh code never calls abort(), never calls raise(SIGABRT), and would
have printed some kind of message if an unhandled exception had led to
an abort being raised by the C++ library.
The output that you are seeing from service-dt-scanner is because
2015-07-08 5:30 GMT-03:00 Jonathan de Boyne Pollard:
If there's no error output, crank up strace and see what the last few system
calls are. It's probably worthwhile doing that anyway, in fact.
Here are the last system calls shown by an strace of
service-dt-scanner before the SIGABRT, with
library version has a rather nasty open file
descriptor security vulnerability, and a sneaky doco change to cover up
a difference in signal semantics, both of which are the cause of the
majority of the conditional compilation in nosh. But you'll notice that
I've not needed to write a fghack
Hello,
I tried to build nosh 1.16 from source code [1]. But some programs
fail to compile, complaining about a missing header, sys/event.h.
Which is true: there's no event.h file on /usr/include/sys, or
anywhere else on my system. Since nosh is supposed to build and run at
least on Debian 7
nosh is now up to version 1.16
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
As you'll see, the WWW pages have expanded a bit. In part this is
because of the Big News, which is the arrival of FreeBSD packages,
bringing FreeBSD up to par with Debian. The old box
82 matches
Mail list logo
