Devin Teske wrote:
> >> So, just as the subject-line says, ... here's an efficient and robust
> >> spinner function compatible with many shells.
> >>DONE=$( /bin/sh -c 'read -t 0 DONE; echo $DONE' )
> >
> > Is this expected to be portable to other operating systems? The d
Gary Jennejohn wrote:
> csup already has a CVS mode, at least in 9-current. I don't use older
> versions of FreeBSD so I don't know whether it supports CVS there.
It does at least down to 7.x.
--
Christian "naddy" Weisgerber na...@mips.inka.de
___
Victor Sudakov wrote:
> I see nobody is ever going to fix this? Cvsup mails me a bunch of
> "Checksum mismatch" errors on every run, with a risk of overlooking
> real errors.
It is particularly egregious when a tag is laid down, like today.
csup(1) ends up refetching a big chunk of the tree from
Julian H. Stacey wrote:
> Problem: /usr/src/usr.bin/fmt/fmt.c is not 8 bit clean.
> (ie French or German etc text with accents in gets broken)
Can you provide an example where it fails?
It works fine for ISO 8859-1 and UTF-8 for me, *provided* the locale
is set correctly.
--
Christian "naddy"
Dag-Erling Smørgrav wrote:
> > > It has come to my attention that whereas with LANG=C "nroff -man"
> > > formats ".An name Aq email" as "name ", it uses different
> > > characters with LANG=en_GB.UTF-8 "name ⟨email⟩". These characters
> > > are appropriate, but a lot of unicode fonts don't seem t
Roman Divacky wrote:
> after addressing Simon's concerns here's a new patch:
>
> www.vlakno.cz/~rdivacky/cal2.patch
I'd simply use the so/se ("standout") capability rather than
specifically asking for reverse video. If you somehow end up on
an 1980s terminal where the two aren't synonymo
Bruce Cran wrote:
> I'm running 8.0-CURRENT amd64 here on a Turion64 X2 machine. Without
> malloc debugging (malloc.conf -> aj) 'make test' takes 25s; after
> removing malloc.conf thus turning on debugging, it takes over 10
> minutes.
Wow! That. Is. It.
Toggling malloc debugging option J mak
Nate Eldredge:
> It might be good first to rule out compiler / library differences.
Sure. Let's cut this short:
"Slow"
Athlon 64 X2 5200+ 2.6 GHz, FreeBSD 8.0-CURRENT amd64 ~60 min
Phenom 9350e 2.0 GHz,OpenBSD 4.4-CURRENT amd64 ~80 min
UltraSPARC-IIe 500 MHz (Blade
Mel wrote:
> If the program itself doesn't directly cause the system time, do interrupt
> rates give any hint as to what does?
systat -vmstat shows a conspicuously large number of traps, I think.
(I'm short on comparable FreeBSD machines.)
> And to rule out the obvious, you did check swapping?
The archivers/lzo2 port runs a series of regression tests after the
actual build. These tests show extremely divergent behavior on
different machines. There are two types of machines:
Type #1:
Running the tests takes roughly the same time as configure and
compile did, whether it's 30 seconds
Yony Yossef <[EMAIL PROTECTED]> wrote:
> Second, my NIC is capable of holding a vlan table on HW, filtering
> vlans on it's own, now I need to find a way to update that HW table
> with added/deleted VLANs in order to use that VLAN filtering offload.
If I may piggyback a question here: What is the
Julian Elischer <[EMAIL PROTECTED]> wrote:
> > My name is Ryan French. I am a Google Summer of Code participant this
> year, and for my project I will be implementing MPLS in FreeBSD.
FWIW, OpenBSD has just started on this:
Import MPLS (Multi Protocol Label Switching)
MPLS support partly bas
Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
> > What is the usual or minimum hardware requirement? Is soekris box
> > enough, or dual core or ASIC based platforms?
>
> A soekris box probably doesn't have the I/O bandwidth nor the CPU power
> to process a full BGP feed.
"Henning and [Bob] hol
Miguel Mendez <[EMAIL PROTECTED]> wrote:
> I've seen the OpenBSD guys have come up with a BSD-licensed CVS[1] that
> should be focused on security as well as features. Is there any chance
> that this could make it into FreeBSD's tree as well?
OpenCVS is very much a work in progress at this point.
Joe Schmoe <[EMAIL PROTECTED]> wrote:
> However, I wonder how well this relates to how many
> ssh sessions (scp file transfers, specifically) that a
> FreeBSD server can handle. Can anyone throw out some
> basic numbers for this ? Assuming a 1ghz p3 and 2gigs
> of RAM, and assuming that everyone
Tim Kientzle <[EMAIL PROTECTED]> wrote:
> The OpenBSD work on tightening up read/write/exec memory permissions
> looks interesting, but I wonder what impact it has on
> JIT technologies; do the current Java VMs or other incremental
> compilation engines require write+exec?
You can disable W^X for
Arjan van Leeuwen <[EMAIL PROTECTED]> wrote:
> It seems that OpenBSD now has BSD licensed versions of the gzip, grep and diff
> families (see
> http://marc.theaimsgroup.com/?l=openbsd-misc&m=105899089116252&w=2). Wouldn't
> it be a good idea to import them into FreeBSD?
Yes, maybe, no.
gzip s
Sean Farley <[EMAIL PROTECTED]> wrote:
> Reasons to consider for switching:
For whatever little it's worth, OpenBSD just switched to freegrep
(a somewhat modified version from NetBSD). They also dumped the
GNU gzip implementation, after extending compress to substitute as
/usr/bin/gzip.
--
Chr
In article <[EMAIL PROTECTED]>, Lars Eggert <[EMAIL PROTECTED]> wrote:
> for the last couple of days I've been unable to cvs update my sources,
> because anoncvs.freebsd.org is unreachable:
There are at least two other machines that offer this service:
anoncvs.de.freebsd.org
anoncvs2.de.freebsd
Chet Ramey:
> > Korn Shell, more likely.
> It's bash. The Korn shell doesn't have it.
ksh88 has a pre-defined alias local=typeset.
--
Christian "naddy" Weisgerber [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in t
Eugene Ossintsev <[EMAIL PROTECTED]> wrote:
> FreeBSD's sh has a builtin "local" for the functions. Is it a POSIX.2
> feature
No.
> or Bash influence?
Korn Shell, more likely.
> It supposes that the classical shell doesn't have "local" at all.
Correct.
--
Christian "naddy" Weisgerber
Dan Langille <[EMAIL PROTECTED]> wrote:
> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=292893+0+archive/2001/cvs-
> all/20010429.cvs-all
>
> In the log, the name "Matthias Kvppe" appears. Is that the correct name?
That is probably "Matthias Köppe" (ISO 8859-15) with the top bit
cut off. Or
Harti Brandt <[EMAIL PROTECTED]> wrote:
> Perhaps it makes sense to switch to star instead? The last version is
> Posix conform, supports extended headers and ACLs. According to the star
> developer (Joerg Schilling) GNU tar is severly broken.
Unfortunately, star has it's own share of problems:
Crist J. Clark <[EMAIL PROTECTED]> wrote:
> I cvsup(1) the FreeBSD CVS repository. I've noticed something that
> annoys me slightly, but also makes me worry if I am not doing
> something correctly. The CVS/Entries file does not seem to get updated
> when I do a 'cvs update.'
[...]
> It claims it
Gary Jennejohn <[EMAIL PROTECTED]> wrote:
> although I was using a Tekram 395 with the sym driver for a while.
I very much doubt that. The DC-395 series are based on the Tekram
S1040 chip which is not compatible with the Sym53C8xx chips. Maybe
you are confusing this with some other Tekram adap
Chris Costello <[EMAIL PROTECTED]> wrote:
>I've done some work on fdescfs in -CURRENT a while back [...]
While we are talking about fdesc(fs), how does it relate to devfs?
I.e. will devfs make fdesc useless, or require it, or...?
--
Christian "naddy" Weisgerber [EM
Rafael Barrero <[EMAIL PROTECTED]> wrote:
>
> 0) Are native binaries for OpenBSD different from FreeBSD?
Yes.
--
Christian "naddy" Weisgerber [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the mess
<[EMAIL PROTECTED]> wrote:
> I've already circulated this message to the OpenBSD
> 'tech' mailing list and the NetBSD 'security' mailing
> list.
Indeed. Please ignore him, he's a troll.
--
Christian "naddy" Weisgerber [EMAIL PROTECTED]
To Unsubscribe: send mail to
Matt Dillon <[EMAIL PROTECTED]> wrote:
> The default filesystem parameters are:
>
> newfs -f 1024 -b 8192 -i 8192 -c 16 ...
-i 4096
--
Christian "naddy" Weisgerber [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTE
Christian Weisgerber <[EMAIL PROTECTED]> wrote:
> I've appended a patch, partly based on a change in nvi 1.81 where
Actually, the NetBSD people have already fixed this, and in a much
better way. I'll submit a PR.
--
Christian "naddy" Weisgerber
There's a bug in nvi 1.79. The options "noprint", "print", and
"octal" don't work properly. When these options are changed, the
routine that evaluates them is called before the option has been
set.
Do we have any people who know their way around the guts of nvi?
I've appended a patch, partly ba
Brian Somers <[EMAIL PROTECTED]> wrote:
> > First, the things I am definitely going to do. Christian "naddy"
> > Weisgerber has taken on the task of porting mm to openbsd.
>
> I think it would be nice to aim to keep the two scripts exactly the
> same, using `uname` when it's really necessar
Arun Sharma <[EMAIL PROTECTED]> wrote:
> http://sharmas.dhs.org/~adsharma/projects/freebsd/truss-diff.gz
Those gratuitous whitespace and formatting changes are a pain...
Related question:
Currently, truss does very little parsing of syscall arguments.
That table in syscalls.c looks anemic. Is t
Garance A Drosihn <[EMAIL PROTECTED]> wrote:
> So, my dumb question is, how DO you pull patches out of a PR?
lynx -dump
vi to extract the relevant part
#!/usr/bin/sed -f
s/&/\&/g
s/>/>/g
s/
Sheldon Hearn <[EMAIL PROTECTED]> wrote:
> Given that having things move around in the base system carries with it
> varying degrees of pain, can you guys just explain why this is actually
> necessary?
Your tape drive has a quirk but no entry yet in the kernel quirk
table, (or you simply use non
Matthew Dillon <[EMAIL PROTECTED]> wrote:
> There's not much point statically linking mt if it's sitting in
> /usr/bin. On the face of it it does seem a good candidate to move
> to /bin.
As I suggested in PR #11205.
--
Christian "naddy" Weisgerber [EMAIL P
Matthew Dillon <[EMAIL PROTECTED]> wrote:
> -pipe makes a significant difference since without it every source
> file being compiled creates several files in /tmp.
Hasn't O'Brien recently said that in fact "-pipe" is already the
default for our cc, so explicitly specifying the option doe
W.H.Scholten <[EMAIL PROTECTED]> wrote:
> Btw, I don't see why I had to load the screenmap myself (unless I reboot
> of course). Why doesn't sysinstall do this when I tell it to use
> iso8859->ibm mapping?
I just tried the console configuration screen in sysinstall, and
it only adds the settings
Ollivier Robert <[EMAIL PROTECTED]> wrote:
> > > As there isn´t a dutch keymap for syscons,
> > ^
> > That's an acute accent (the same diacritic as in 'é'), not an
> > apostrophe.
>
> In 8859-1 yes but not in 8859-15 (aka Latin9)...
Well, the original message was in Latin 1. You r
(I think this should be taken to -questions.)
W.H.Scholten:
> As there isn´t a dutch keymap for syscons,
^
That's an acute accent (the same diacritic as in 'é'), not an
apostrophe.
> First, how do I enable/use dead keys?
Take a look at some of the provided *.acc.kbd keymaps.
The
Alex Belits <[EMAIL PROTECTED]> wrote:
> People with genuine i18n needs such as linguists or people with genuine
> i18n needs such as non-English users? Linguists don't see Unicode as being
> sufficient,
Linguists are interested in languages, not in computer character
set issues. They are just
Alex Belits <[EMAIL PROTECTED]> wrote:
> > Not so. Unicode is a character map. One of many. It just happens to be
> > the most inclusive one in existence.
>
> It is. However if you look at the current efforts of its "adoption", it
> is not used as one. It's touted as the solution to all langua
G. Adam Stanislav <[EMAIL PROTECTED]> wrote:
> >Of course, it still remains to be seen if having Unicode support on the
> >console is a Good Thing(TM).
>
> I don't see how it would be even possible, due to hardware limitations.
> The console can only support an 8-bit font (I mean 8-bit encoding)
I wrote:
> I also think the creating of a freebsd-i18n list is long overdue.
> I18N issues are largely lost among the traffic on -hackers and
> -questions, and it has become something of a specialty area
I just got a note from our dear postmaster that freebsd-i18n will
be created within the next
Alex Belits <[EMAIL PROTECTED]> wrote:
> I have just asked, who will benefit from it. No one answered "I will" --
I WILL.
I want to be able to mention Henry Charri{e grave}re and
Stanis{l stroke}aw Lem in a single document and spell those names
correctly. Actually, that's a real world example
Anatoly Vorobey <[EMAIL PROTECTED]> wrote:
> What do you think?
For what it's worth (me not being a committer and generally not on
the productive side of things), I morally support this idea.
To push certain buttons: what you are suggesting is to bring syscons
up to what the Linux console alrea
Doug Barton:
> In my mind there is a difference between items that are
> freebsd-exclusive (like set -o and alias) and items that we have unique
> implementations of, like export. The latter are available on other
> platforms, and therefore, IMO we should follow the more generally accepted
Doug Barton:
> > export VAR=value
> The problem with that option is that it's not portable.
It's just as portable as "set -o" and "alias". None of them are
available in the original Bourne shell, all of them in the POSIX
shell.
> > alias r='fc -s'
>
> Hrrmm... ok. I have no experience
Doug Barton <[EMAIL PROTECTED]> wrote:
> Commentary on my files. . . Using allexport instead of an explicit
> 'export' for every variable makes the file easier to read, and gives a
> novice user one less thing to worry about.
I think Sue has a made a good argument against allexport.
Also,
MikeM <[EMAIL PROTECTED]> wrote:
> Has anyone thought of Unicode support on FreeBSD?
It has crossed my mind...
> I think that it is inevitable that eventually FreeBSD
> will *need* to support unicode if it wants to continue
> as a viable operating system in the future.
Probably. The demand fo
Max Khon <[EMAIL PROTECTED]> wrote:
> However, under Solaris 2.6:
> clone$uname -a
> SunOS clone 5.6 Generic_105181-13 sun4u sparc SUNW,Ultra-1-Engine
> clone$/bin/ksh
> clone$for i in ; do echo $i; done
> /bin/ksh: syntax error: `;' unexpected
That's an old ksh88, which probably doesn't conform
Alan Batie <[EMAIL PROTECTED]> wrote:
> I just got an onstream scsi tape drive only to discover that I should've
> checked the archives because it don't work.
Depends on the drive. If you got an Echo drive (SCxx), you're right.
The ADR drives--yes, they all use ADR tape technology, but confusing
Jason Simms <[EMAIL PROTECTED]> wrote:
> On Solaris, I can see what choices I have by running 'locale -a'.
> However, all my attempts to find a similar function on FreeBSD 3.4
> have failed.
There is no locale(1) command, true.
You can find the available locales under /usr/share/locale.
> es_E
Sergey Babkin <[EMAIL PROTECTED]> wrote:
> At work I've got experience with 32-port D-Link 10/100 switched
> hub. It works fine except that it hangs occasionally (can be
> reset by power-cycling). So we don't buy them any more. Also
> at my pre-previous employer we had small 8-port 10Mpbs hubs
Kazutaka YOKOTA <[EMAIL PROTECTED]> wrote:
> In the past, it has been pointed out that some of the termcap entries
> needs updating.
Indeed. I just noticed that screen still has trouble in xterm, due
to a broken termcap entry. Would a committer please take care of
PR #12209?
--
Christian "nadd
Should we have a PAPERSIZE variable (A4 vs. letter) in /etc/make.conf?
- groff has the paper size set as compile time option.
- Various ports that now exist in two versions or require the
user to define the paper size at build time could automatically
pull the value in.
--
Christian "naddy"
Should we have a PAPERSIZE variable (A4 vs. letter) in /etc/make.conf?
- groff has the paper size set as compile time option.
- Various ports that now exist in two versions or require the
user to define the paper size at build time could automatically
pull the value in.
--
Christian "naddy
57 matches
Mail list logo
