, at least
openbox, fvwm and xfce. Not sure how up-to-date they are.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana
to the bits on
OpenIndiana.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
to an accurate manual for the 151a5 ipadm manual?
You can try the one that ships in SmartOS:
https://raw.github.com/joyent/illumos-joyent/master/usr/src/man/man1m/ipadm.1m
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss
read around 250MB from it into RAM *once* per boot.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
available you might give that a try -- I'm
pretty sure there's a binary package in the repository.
e.g.
http://embeddedfreak.wordpress.com/2008/08/12/using-gnu-screen-to-debug-your-serial-port/
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
automatically export during shutdown, or
somehow flag it so the system will never try to import or mount it during
bootup.
Depending on at shutdown behaviour can never be correct. You cannot
guarantee a clean shutdown.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
ISO, which
is also easy to create with the distribution constructor. Some
rough-draft information about that is here:
http://blog.sysmgr.org/2010/10/openindiana-automated-install-server.html
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
in
enterprise but let people like me worry about that.
I'm glad that people like you are worrying about it, but I think I'll
continue to worry about it as well if that's perfectly alright.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
On Mon, Oct 25, 2010 at 3:09 PM, Albert Lee tr...@opensolaris.org wrote:
On Sun, Oct 24, 2010 at 1:17 AM, Joshua M. Clulow j...@sysmgr.org wrote:
http://blog.sysmgr.org/2010/10/openindiana-automated-install-server.html
I love this solution! It makes AI so much more reasonable. Even if
you're
on the user/sysadmin/etc having
an existing OI install to make more OI installs.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo
similar attack styles.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
know that I don't.
If we can be terse while remaining legible and filterable then I'm all for it.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http
that services the search requests needs to be (re)indexed?
(URLs shortened as the full query string is quite long)
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http
months since I read through the RFC (and a
bunch of code) while chasing down similar issues at a University.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http
ai_x86_image_JMC_151a.xml
which will, by default, be in:
/rpool/dc/media
I've used the ISO I created with this process to install at least one
machine so far, so it appears to work well enough.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
to find time, but perhaps this week.
Immediately, though, the XML in the gist should let you create an ISO.
That ISO ought, then, to work with the official AI server bits.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana
for these simple cases.
At least one tool like this does exist. I've used this one before:
http://code.google.com/p/manifold/
The tool may require some polish, or it may just serve as inspiration
for writing a better one. Either way it would be a good idea to
include a tool.
--
Joshua M. Clulow
to more hardware. :)
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
would still be in the ARC and you could send them without reading back
from disk.
We used to do this every 15 minutes on a pair of thumpers at the Uni I
worked at. Has anybody done this with a shorter period? You may get
more traction with the question on a ZFS mailing list.
--
Joshua M. Clulow
On 6 December 2011 00:34, Geoff Flarity geoff.flar...@gmail.com wrote:
On Dec 4, 2011 7:21 PM, Joshua M. Clulow j...@sysmgr.org wrote:
On 5 December 2011 10:41, Geoff Flarity geoff.flar...@gmail.com wrote:
Stay away from AMD if you're hoping to use this system with KVM.
There's no AMD
On Dec 14, 2011 5:54 AM, Mark Creamer white...@gmail.com wrote:
The thing that is interesting about trying to set up the zones in OI is
that it *always* fails on the same package (python-26), so it's not a
bandwidth issue, or a problem where the connection drops.
Is it also always the exact
On Dec 14, 2011 8:32 AM, Mark Creamer white...@gmail.com wrote:
Exactly the same URL. I just tried it again to be sure.
What happens if you try and wget the file? Does it work? Does the shasum of
the file then match the filename?
___
| sha1sum -
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
(or OpenIndiana) in the future.
I think we've covered this in just about every possible phrasing by
now, and it would be best to lay it to rest permanently. No good can
come from the leak itself, or from talking about it any more.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http
/illumos-misc
These scripts are identical to the ones I've been using to deploy OI
151a at work, so I'm reasonably sure they work as intended.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
/72e6c91
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
of the last interval where _at least one disk_ had _at least one
inflight I/O operation_.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman
of work around
that I am not up to speed on? or should I file a bug report?
Are you running tcpdump/iftop within a zone, or in the global zone?
What is the exact command you are running, and the error output
generated by the tool?
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
are they
for?
As described in pkg(5), this is publisher-specific metadata for the
Image Packaging System.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org
changes to the Driver
book specifically. It's up with some other books here:
http://illumos.org/books/
The source for the Writing Device Drivers (WDD), from which we build
the above site, is here:
https://github.com/rmustacc/illumos-docbooks
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
of the files that I work with.
What model of CPU(s) do you have in this machine? You can find out
with psrinfo -vp.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss
>>> what speaks against using OI in server use?
>> Security updates.
> Good point, indeed. Just curious: But isn't that something all Illumos
> distributions have in common?
No. SmartOS and OmniOS get prompt security updates as CVEs and other
announcements become ava
n order for your messages to the illumos
developer@ and discuss@ list to be accepted.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
bytes.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
n
> update about 1 week old?
I think this illumos bug made some changes in that area:
https://www.illumos.org/issues/9664
Cheers.
--
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-di
1920x1080 panel, or a much higher resolution
3840x2160 panel.
Cheers.
--
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/op
easily enable us to see if the
problem you're experiencing is already fixed in illumos, and you just
need fresh OI install media.
Cheers.
--
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-d
documentation that's definitely
good, rather than a sprawling mess of things which are old and thus
actively misleading. The wiki model seems to have lead us down the
latter path, so we're trying the docs site approach.
It seems like a good approac
Cheers.
--
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
t can
> help you find the problematic part.
You might want to have a look in the FMA error log; e.g., via "fmdump
-e". If that contains records that look interesting, you can ask for
more details with various flags.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
_
et better -- or at least a greater number of --
responses in venues where the community tends to congregate. I'm
unlikely to ever visit Reddit with any regularity, for instance, but I
am on our mailing lists and in our IRC channels a lot.
Cheers.
--
Joshua M. Clulow
http://blog.s
which you
should be able to run on both the Linux machine (I believe) and the
server. It ought to print out a summary of what is currently exported,
and will probably include the list of properties (rw, root, etc)
currently in effect.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
the new property is off,
the file systems are unshared.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
based on your experience with the system is a
great way to get started as a contributor.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
On Sun, 19 Jul 2020 at 17:24, Judah Richardson
wrote:
> On Sun, Jul 19, 2020 at 7:18 PM Joshua M. Clulow wrote:
> > On Sun, 19 Jul 2020 at 16:52, Judah Richardson
> > wrote:
> > > # zfs set sharenfs='rw=@ClientIPAddress/32,root=@ClientIPAddress/32'
> > r
ral, anything that needs to be
"worked around" is a bug and it can almost certainly be fixed -- but
only if it gets reported!
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@o
s OK. What we should focus on is reducing the effort to keep the
common software up-to-date just once, where possible, without
requiring everybody to agree on what makes our distributions unique.
I am happy to help anybody who wants to get a common repository
started under the illumos organisatio
versions up at:
https://illumos.org/downloads/
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
On Thu, 7 Jan 2021 at 23:34, Carsten Grzemba via openindiana-discuss
wrote:
> > >On 07.01.21 23:47, Joshua M. Clulow via openindiana-discuss wrote:
> > >>If you hit any trouble with Rust, I'd love to hear about it! We have
> > >>a good relationship with the
On Thu, 7 Jan 2021 at 19:06, Till Wegmueller wrote:
> On 07.01.21 23:47, Joshua M. Clulow via openindiana-discuss wrote:
> > On Thu, 7 Jan 2021 at 13:57, Till Wegmueller wrote:
> > https://fosshost.org
> >
> > It seems they will provide one or more v
r to build rust software and rust itself.
If you hit any trouble with Rust, I'd love to hear about it! We have
a good relationship with the Rust project itself, so we should be able
to get things fixed as they arise, without needing to float additional
patches.
Cheers.
--
Joshua
solves a problem for you to the extent that it's worth your
engaging with that community and helping to maintain the software,
we're here to help.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discu
included in the "illumos/sysroot"
repository, with minor configuration or modification, to make your own
sysroot from any built copy of illumos.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
did the system panic, or was the power
to the system interrupted, or did the USB cable become disconnected at
any point?
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openin
On Mon, 25 Jan 2021 at 11:52, Chris wrote:
> On 2021-01-24 23:10, Joshua M. Clulow via openindiana-discuss wrote:
> > # dtrace -x stackframes=100 -n '
> > profile-997 /arg0/ { @[stack()] = count(); }
> > tick-60s { exit(0); }' -o out.kern_stacks
> >
s file, does the
build run any faster?
At any rate, lots to explore. I would start by looking at what the
computer is actually doing, rather than exploring replacement shells.
Once you get some preliminary results, I am sure folks will be
interested in your findings.
Cheers.
--
Joshua M. Clulow
hat's relatively busy, I would next use DTrace to
profile the kernel. You can get a flamegraph of the same 20 seconds
of busy work:
https://github.com/brendangregg/FlameGraph#dtrace
Profiling data like that should let us know where the kernel is
spending its time, and may give pointers for opt
On Sun, 24 Jan 2021 at 21:13, Chris wrote:
> On 2021-01-24 18:53, Chris wrote:
> > On 2021-01-24 17:48, Joshua M. Clulow via openindiana-discuss wrote:
> >> On Sun, 24 Jan 2021 at 17:27, Chris wrote:
> > All the reports I've seen thus far, indicate 800x600.
> &
th all software, the only way to know if it meets your needs is
to give it a try with your intended workload.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindi
o, as
there can still be incompatible on-disk format changes and bug fixes
after things land in OpenZFS master but before a release. I would
also recommend coordinating on the illumos lists and/or in #illumos
IRC with other folks that have been porting changes from OpenZFS.
Cheers.
--
https://illumos.topicbox.com/groups/developer/T3f72cd35e06c75bd/ipd-19-sunset-sparc
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
ation today. We're just a self-organising
project team.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
round in place to stop the panics:
13908 disable kernel FPU by default until it is stable
https://www.illumos.org/issues/13908
https://code.illumos.org/c/illumos-gate/+/1573
You'll want to make sure you upgrade your system so that it includes
this workaround.
Cheers.
--
Joshua
On Sat, 1 May 2021 at 10:05, Reginald Beardsley via
openindiana-discuss wrote:
> How about a pkg or explicit instructions (e.g. a shell script) for setting up
> to be able to generate an ISO?
http://docs.openindiana.org/dev/distribution-constructor/
Cheers.
--
Joshua M. Clulo
are related to missing device drivers.
I would not assume that. What are the fabric events? Can you get
more detail with "fmdump -eVp"?
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
initiative in sifting through the build system and the files.
Things are a bit cryptic sometimes, but it's all in there; by reading
the source you will be able to find it.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss ma
hell
script that may not have both its arms completely around the problem.
It'd be good to get an illumos bug logged with the issue you've
described, including the sequence of ZFS/NFS operations you've used to
get the system into this state so that whatever the fix is can be
tested well.
reach
> them?
>
> Shooting in the dark here; that's the only thing I can come up with.
I think it would be easiest to take a look at the shell script and see
what it gets out of sharetab and what it does with find.
Cheers.
--
Joshua M. Clulow
ebruary about
where to find the installer source, and how to contribute:
https://openindiana.org/pipermail/openindiana-discuss/2021-February/023944.html
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
open
ding it correctly, it trapped in strlen()).
It does look that way. If you add a "-v" to ::findstack you might see
arguments, which can be helpful. If there aren't arguments this
program may need to be built with -msave-args.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
imit there makes the system
behave a bit more like Linux, and is probably unlikely to have a
practical impact on your software: it still equates to ~128TB of
address space for each 64-bit process.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
software won't fix
itself, and we're all in this together.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
0, 0, 0, 0, 0)
> root@openindiana:/jack#
Those other threads, beyond the main thread from format that is
crashing, are almost certainly from libsysevent on behalf of the disk
management library. They are an implementation detail of the door
calls it uses to subscribe to events about
lumos/metadata-agent
This agent is a very basic, illumos-specific replacement for
cloud-init. It configures networking, expands the root disk,
optionally runs a user-provided start script, etc. It is included by
the scripts in my "omnios-image-bui
pool label and did
> a more surgical elimination. That was actually because the problem was the
> duplicate label at the end of the disk.
I believe you want "zpool labelclear", as per: https://illumos.org/man/1M/zpool
--
Joshua M. Clulow
http://blog.sysmgr.org
ways best to file and fix the underlying bug where we can,
rather than propagate workarounds like this.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
ow about it.
I would recommend keeping things civil, as much as possible. Remember
that the folks here are volunteers. I totally understand that it's
frustrating when things are broken, but it's also really draining to
receive a lot of cranky e-mails.
ew disk array.
Out of interest, why not just "zfs create -o mountpoint=/export
rpool/export" to get a separate /export file system, instead of the
slices and separate pools?
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
open
reports to emit,
and how much detail to display:
https://illumos.org/man/1M/fmdump
The combination "-eVp" may well be helpful, if you want to dig in on
all the data we stored for each report.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
__
ntfs
/etc/svc/volatiletmpfs
/lib/libc.so.1 lofs
/net autofs
/procproc
/system/boot bootfs
/system/contract ctfs
/system/object objfs
/tmp tmpfs
/var/run
d be able
to easily verify that it had backed everything up without an extensive
ongoing restore testing programme.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openin
at
alias to the package in illumos:
https://www.illumos.org/projects/illumos-gate/issues/new
e.g., a similar recent bug for adding an alias for an ahci card:
https://www.illumos.org/issues/13599
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
_
t so slow I can't work with it. :-)
> So a HUGE thanks go out to everyone here on the list, that chimed in
> to help out -- THANK YOU! :-)
Does that mean loader is, on at least this machine, struggling with
writes to a serial port which isn't there, perhaps? (More concretely:
why does t
t;
> I will use the linker scripts in a non-interactive shell script so I don't
> want it to print this version info every time it runs.
Are you passing the -V or --version flag to ld somehow?
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
__
pool, and has enabled us to create virtual machine images that work
under a variety of hypervisors -- the OS just finds the correct path
on first boot.
I haven't personally tried, but I would hope this might make USB pools
work better as well. If not, b
> itself.
>
> Any logs or anything like that in particular I should take a look at?
What driver is in use? What model of NIC is it?
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindi
On Mon, 20 Dec 2021 at 22:26, Judah Richardson
wrote:
> On Tue, Dec 21, 2021 at 12:23 AM Joshua M. Clulow via openindiana-discuss
> wrote:
>> > Any logs or anything like that in particular I should take a look at?
>> What driver is in use?
> How do I determine this?
W
OI package.
> I may continue to use that product.
You may wish to investigate "zrepl" as well, which has some neat features:
https://zrepl.github.io/
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mail
diagnostic tools; e.g.,
$ routeadm
$ netstat -rnv
$ ipadm show-addr
$ nwamadm list
$ netstat -D
$ cat /etc/resolv.conf
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-
ting service. In fact, in my over 3 decades
> of experience with Sun machines, I only once have seen that the routing
> service had to be active. That one case was when I experimented with the
> COMSTAR network simulation tools to play with virtual switches and
> routers.
Goodness, wh
is specific machinery in
the OS to enable ipv4-routing under some conditions when a specific
policy has not been specified by routeadm that will need to be
unwound; e.g., see "cmd/svc/milestone/net-routing-setup" where it
mentions "routeadm/ipv4-routing-set".
Cheers.
--
Joshua
ribution-level question, but unrelated to how it works when
it is installed.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
tor settings.
>
> Sorry for the inconveniences.
Thanks for fixing it up!
Is there some way that we can gate future publishing to the public
repository on a successful test install/update?
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindia
On Thu, 30 Jun 2022 at 12:32, Andreas Wacknitz wrote:
> Am 30.06.22 um 20:56 schrieb Joshua M. Clulow via openindiana-discuss:
> > Is there some way that we can gate future publishing to the public
> > repository on a successful test install/update?
> We need more volunteers a
uot;
Can you suggest updates to the official gate building documents where
they cover OpenIndiana?
https://illumos.org/docs/developers/build/#openindiana_1
The source for this documentation is in a GitHub repository:
https://github.com/illumos/docs/blob/master/docs/developers/build.md#ope
s and laptops and even single-
homed servers with simple DHCP addresses.
- If you want to be in more control, or to have
things be more static, disable NWAM. Use ipadm.
You will know when this is you, because your
needs will
drives on SATA and connected another
> drive via SATA to USB adaptor, would ZFS still handle it and slow down,
> or would it throw a fit?
As long as the devices are merely slow, and not throwing actual
errors, then I would expect that the pool would just exhibit similarly
limited performance
On Wed, Oct 5, 2022, 00:28 david allan finch wrote:
> Not quite sure what has broken it but, I installed the latest version of
> VirtualBox 6.1.38 and updated the client extension into my OpenIndiana
> VM client (it was the last build 2021Oct from the ISO). Around the same
> time I did a pkg
ant to include more developer-focused tools like
cscope. If vim depends on cscope, even though its use is optional,
that is no longer possible.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
___
openindiana-discuss mailing list
openindiana-disc
g outside
> the "__main__" block.
>
> So there's no need to prevent connections - the daemon will never call
> sock.accept()
Could it not just create a file in /tmp and flock it then? The socket
business seems a touch circuitous...
--
Joshua M
1 - 100 of 107 matches
Mail list logo
