Re: "hg clone https://anonhg.netbsd.org/src/" still aborts, but...
On Fri, Jun 12, 2020 at 12:26:26AM -0700, Greg A. Woods wrote: > OK, so the initial "hg clone" equivalent took almost exactly 3 hrs. > > 17:46 [663] $ ftp > https://cdn.NetBSD.org/_bundles/src/77d2a2ece3a06d837da45acd> > Requesting > https://cdn.NetBSD.org/_bundles/src/77d2a2ece3a06d837da45acd0fda80086ab4113c.zstd.hg > 100% |***| 1285 MiB6.86 MiB/s00:00 > ETA > 1347521045 bytes retrieved in 03:07 (6.84 MiB/s) > 17:49 [664] $ > > 17:55 [669] $ hg init h-NetBSD-src > 17:55 [668] $ cd h-NetBSD-src > 17:55 [669] $ hg unbundle > /build/work-tmp/77d2a2ece3a06d837da45acd0fda80086ab4> > adding changesets > adding manifests > adding file changes > added 931876 changesets with 2425841 changes to 439702 files (+417 heads) > new changesets 8cec458d70ff:77d2a2ece3a0 > (run 'hg heads' to see heads) > 20:48 [670] $ > > > The final "hg checkout trunk" took almost exactly 2 hrs: > > 20:48 [671] $ time hg checkout trunk > 171685 files updated, 0 files merged, 0 files removed, 0 files unresolved > 7204.00s real 501.37s user 1645.00s system > 22:48 [672] $ > > > So, that's 5hrs total to do an "hg clone". > > Wow. Well, you're asking to fetch all the history for all the sources to an actively developed operating system project running since at least 1993 (27 years). With git, you can use --depth=1 when cloning to create a shallow clone. This would limit the amount of data fetched. I imagine Mercurial has some similar option (but I don't really know). Regards, > Now this was to an NFS-hosted filesystem, and there was another "rsync > && cvs update" running during some of that time on the NFS server, but > still (the rsync and other cvs activity normally only occupies > about 1/2 or less of the file server's capacity according to sysstat). > > > I'll now fire up a new "git clone" next for a more up-to-date > comparison. There will be another rsync && cvs start during this, just > to be fair. :-) > > -- > Greg A. Woods > > Kelowna, BC +1 250 762-7675 RoboHack > Planix, Inc. Avoncote Farms > -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
Re: logout delay
On Mon, Apr 20, 2020 at 02:06:23AM +0500, Vitaly Shevtsov wrote: > Hello! > > Does anybody know why there is about 1 second delay before OS exited > from the shell? There is no such issue on FreeBSD for example - it > quits immediately when you type 'exit' or press ^D. How do you run the shell session (and what shell)? Is it in a terminal (which one), or in a tmux pane, or a GNU screen window? I can see the same sort of delay on OpenBSD when exiting a shell when that also means closing a tmux pane. -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
Re: Changes to PERL
On Mon, Apr 13, 2020 at 08:11:39PM -0400, Todd Gruhn wrote: > I looked at perldelta -- Nothing useful there. > I am mainly interested in changes to system vars, and syntax. > Well, perl5280delta mentions that "delete" can be used on key/value hash slices, and also mentions new syntax for some regular expression stuff. perl5260delta also mentions some syntax changes to regular expressions and some modifications to how here-documents work. perl5240delta mentions some new formatting support for printf and sprintf, and again, more regular expression support. I'm not entierly sure I understand what you're after. > At least I know my books are still useful. > > Thanks > > On Mon, Apr 13, 2020 at 6:29 PM Andreas Kusalananda Kähäri > wrote: > > > > On Mon, Apr 13, 2020 at 05:10:41PM -0400, Todd Gruhn wrote: > > > Where is a good place to look for current PERL syntax and examples? > > > (been about 10yrs). > > > > > > Which books should be updated first? > > > (I have 4 of the O'Reilly PERL books) > > > > The perldelta manuals comes to mind: > > > > perldoc perldelta > > > > This will show you the changes between the current and the last release > > of Perl. It will also tell you (in the DESCRIPTION section) what the > > previous perldelta manual is called (something like perl5301delta, for > > the changes between Perl 5.30.0 and 5.30.1 for example). > > > > This might not be exactly what you were looking for, but it's what > > popped up in my mind at least. Apart from that, "perldoc perl" contains > > the list of other Perl manuals, for example perlintro. > > > > -- > > Andreas (Kusalananda) Kähäri > > SciLifeLab, NBIS, ICM > > Uppsala University, Sweden > > > > . -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
Re: Changes to PERL
On Mon, Apr 13, 2020 at 05:10:41PM -0400, Todd Gruhn wrote: > Where is a good place to look for current PERL syntax and examples? > (been about 10yrs). > > Which books should be updated first? > (I have 4 of the O'Reilly PERL books) The perldelta manuals comes to mind: perldoc perldelta This will show you the changes between the current and the last release of Perl. It will also tell you (in the DESCRIPTION section) what the previous perldelta manual is called (something like perl5301delta, for the changes between Perl 5.30.0 and 5.30.1 for example). This might not be exactly what you were looking for, but it's what popped up in my mind at least. Apart from that, "perldoc perl" contains the list of other Perl manuals, for example perlintro. -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
Re: Linux-Netbsd huge difference of speed, same hardware
On Wed, Mar 04, 2020 at 10:07:29AM +0100, Pierre Dupond wrote: > Thanks for the tip. It is a little bit faster now > but still much less fast than with Linux. Why the use > of the raw device makes a difference. > > The transcript of the commands when using > the raw device is: > > oche# dd if=/dev/urandom of=/dev/rld0f bs=32k count=1000 > 1000+0 records in > 1000+0 records out > 32768000 bytes transferred in 7.726 secs (4241263 bytes/sec) > oche# dd if=/dev/urandom of=/dev/rld0f bs=32k count=1 > 1+0 records in > 1+0 records out > 32768 bytes transferred in 90.755 secs (3610599 bytes/sec) > oche# ^C > oche# dd if=/dev/urandom of=/dev/rld0f bs=2m count=100 > 100+0 records in > 100+0 records out > 209715200 bytes transferred in 45.064 secs (4653719 bytes/sec) Are you using the same implementation of dd(1) on both systems? As was previously mentioned, GNU dd may return before all data has actually been written to disk. Also, it's not clear whether you're actually testing the speed of the /dev/urandom device here. Maybe use a more neutral device such as /dev/zero or a static file? In the end, if Linux seems to be faster and better for doing what you need to do, then maybe do that thing on Linux? > > Le 04.03.20 à 08:20, Martin Husemann a écrit : > > On Wed, Mar 04, 2020 at 08:08:34AM +0100, Pierre Dupond wrote: > >> I try to execute the command "dd if=/dev/urandom of=/dev/ld0f bs=2m" (or > >> "bs=32k" but > >> this make no difference). > > > > You want of=/dev/rld0f here. > > > > Also I dimly remember gnu dd not flushing the output or something unless > > some special option is given, but that should not make a real difference for > > huge transfers. > > > > Martin > > -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden
Re: green lines hell
On Wed, Feb 26, 2020 at 11:33:05AM +0100, Benny Siegert wrote: > On Tue, Feb 25, 2020 at 9:36 PM Andrei M. wrote: > > In all recent major versions of NetBSD/amd64, incl. NetBSD 9.0 error > > notifications from the kernel are forwarded in green colour to the > > first vt. In my case it mostly concerns notifications about hardware > > probing going on or when a connection change happens to the net card > > (I use an ASUS K70ID laptop). It happens every few minutes, looks > > terrible from the aesthetic point of view, when you're typing > > something and then this breaks your line, even within vi, and can even > > be some sort of security threat when it messes up the password prompt. > > When I last installed OpenBSD, it did the same, except in white on > blue. Worse, it would print it onto whichever console you were on (I > think). FWIW, no, OpenBSD works more or less exactly as NetBSD in this regard, apart from the specific colouring. > > In NetBSD, kernel messages go to a VT called "console", which is the > first VT by default. Once you finish the installation, you can edit > /etc/ttys, set console to "off" and ttyE0 to "on". This turns the > first VT into a regular VT, and kernel messages go nowhere by default. > Or you could connect the console to a serial port. Or if you run X, > Xconsole is typically able to show kernel messages in a window. -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
Re: How do you set $PS1 on /bin/ksh
On Fri, Jan 24, 2020 at 07:05:29PM +, Ottavio Caruso wrote: > On Fri, 24 Jan 2020 at 18:57, Robert Elz wrote: > > > > There are a zillion different things called ksh, I'm not > > sure which version OpenBSD have as ksh > > Strangely enough, both OSes report exactly the same version: > > KSH_VERSION='@(#)PD KSH v5.2.14 99/07/13.2' That's because both are based on that version of pdksh. mksh is based on OpenBSD's ksh, not the other way around if I recall correctly. There was a flurry of activity on the OpenBSD side of the fence some time ago, when things these (backslash escapes for prompts) were added. (Actually, looking at it in CVS, that was 16 years ago now. Time flies.) -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
Re: Where is "hash?"
On Sun, May 05, 2019 at 05:46:35PM -0400, Bob Bernstein wrote:
> Not too long ago a resident of this venue shared a
> wonderful document describing how to set up sasl for
> postfix. For today's purpose, here is the pertinent
> snippet:
>
> --chomp--
>
>/etc/postfix/sasl_passwd (for security set ownership to
> root:wheel, permissions to 600) [mx.sdf.org]:submission
> sdf_login.sdf.org:smtp_passwd
>
> hash /etc/postfix/{generic,sasl_passwd}, then check
>and reload configs:
>
> --chomp--
>
> You'll note that word, "hash." I don't have a "hash" on
> mynew NetBSD install, and I cannot determine what I must
> install to obtain one!
>
> The document is here:
> https://sdf.org/?tutorials/smtpauth#postfix-netbsd6
>
>
>
> Thank you,
>
> --
> "In our age there is no such thing as ‘keeping out of
> politics’. All issues are political issues, and politics
> itself is a mass of lies, evasions, folly, hatred, and
> schizophrenia."
>
> George Orwell "Politics and the English Language" (1946)
The word "hash" is not a command, it's what happening next in the
tutorial. Hashing is done by the postmap command. This is shown on the
lines following that text:
% cd /etc/postfix/
% sudo postmap generic sasl_passwd # creates generic.db & sasl_passwd.db
Regards,
--
Kusalananda
Sweden
Re: Please recommend office package on NetBSD
On Fri, Oct 30, 2015 at 02:04:55PM -0600, Swift Griggs wrote: > On Fri, 30 Oct 2015, Mayuresh wrote: > >>Minimal == antiword (converts word docs to text) > >Tried. Cute one, but seems to say "is not a Word Document." for just too > >many files. > > It only works on doc (Word 97 or before, I think) files not the newer DOCX > files (which are really zip files full of MS garbage). > > >>Small == abiword (standalone word processors that supports MS DOC[X] files) > >Trying. Would abiword-plugins improve compatibility with MS/Open/Libre? > > They do improve it's import/export functionality quite a bit. I can tell you > right now that Abiword doesn't do as good a job rendering as libre/open > office does. However, it's great if you just need to read a word document > someone sent you at work. Abiword also works pretty well if you can keep the > document in Abiword the whole time and just export Word 97 format at the > end. Why would you open up a big clunky *editor* to read a document? Get back to them and tell them to send you a PDF version of the thing instead. The option to export to PDF is right there, in the menu. Works for me... ... sometimes. -- :: Andreas Kusalananda Kähäri, Bioinformatics Developer, BILS, :: Uppsala University, Sweden ::-- :: My other car is a cdr.
