ntor of such a system, I'd just leave it undefined.
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Folks,
although there was much rejoicing, I think there's no need for a
new option to cp. Just use the toolbox, it's not too hard:
(cat bigfilelist; echo destdir) | xargs cp
Or even
echo destdir >>bigfilelist
xargs cp < bigfilelist
should do the trick.
Regards,
ion for me when I
found xargs would by default use 5000 arg chunks and not all in one go.
I'd rather get rid of kern.argmax and the limitations of the exec familiy.
Yes, I'm dreaming :-)
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ave a look at
what needs to be done. Thanks!
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
./contrib/ipfilter/ip_fil.c: * Try to detect the case when compiling for NetBSD with
pseudo-device
./contrib/libpcap/inet.c:
et 15)
Apr 23 22:24:08 hal9000 /boot/kernel/kernel: cd0: Attempt to query device size failed:
NOT READY, Medium not present - tray closed
Apr 23 22:26:44 hal9000 /boot/kernel/kernel: i4b: unit 0, assigned TEI = 126 = 0x7e
Apr 23 22:27:08 hal9000 /boot/kernel/kernel: [agree]
Regards,
Jen
g the load significantly (about 1 or more),
isdnd seems to take a nap. No more packets transmitted. If I
suspend the running programs, isdnd awakes and continues.
Is anybody else observing the same behavior?
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signatur
On Thu, May 03, 2001 at 01:39:50PM +0200, Alexander Leidinger wrote:
# On 2 Mai, Jens Schweikhardt wrote:
#
# [Ruslan: I CCed you because of the second part of the mail]
#
# > I've seen some recent mails related to rtprio oddity which seemed
# > to also affect the isdnd. My
lags}
# + fi
...
# ---snip---
# (I think the isdn_ttype part isn't needed anymore, someone committed
# something like this already, but the screenflags part is useful for me)
Yup, that was me :-)
Can you provide a patch against -current and also a patch adding
isdn_screenflags to /e
tmask 255.255.0.0
and later made the default route.
The address 194.95.228.253 in /etc/hosts belongs to another statically
assigned interface, i.e.
isp0: flags=a011 mtu 1500
inet 194.95.228.253 --> 194.95.242.2 netmask 0xff00
ether 00:00:00:00:00:00
isp1: flags=a011 mtu 1
process owns a mutex
Debugger("panic")
>trace
Debugger(...)
panic()
propagate_priority()
_mtx_lock_sleep()
ffs_write()
vn_write()
writev()
syscall()
syscall_with_err_pushed()
Anything else I can do to track this down?
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.
client);
I'm not sure if XmuGetHostname could be the culprit.
[Setting up a caching-only server]
Before I do that I want to track down what has changed. I still believe
that when my DNS works properly with 4.3 it should as well with 5.0
without jumping through this hoop.
Regards,
eout_flush
vm_object_page_clean
vfs_msync
sync
syscall
syscall_with_err_pushed
Is there anything else I can do to track this down?
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTE
s empty:
>Quarter:
Whazzat?
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
SY in case someone tries to delete a mounted
md device?
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
anyone reproduce this?
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
late in this thread, so I don't know what has been discussed before,
but if this means to use protocol version one, scp does this already
with
scp -o Protocol=1 ...
That's what I use since freefall has implemented this POLA-violation^Wnew
philosophy.
Regards,
Jens
--
Jens Schweik
ounted properly.
Does anyone see similar behavior? Any clues?
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
st driver. If you're lucky (pun intended :-)
it may do the trick for you if you hack the stage_[12].sh scripts.
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
files I receive as attachments.
Corporate windows environment, you know :-)
It's a bitch to configure and integrate with mutt. And all the messages
about font diddling look scary, but it does what I want, viewing the
files without rebooting or buying vmware.
Regards,
Jens
--
ch! Commited. Thanks!
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
source tree.
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
is a char* or other depends on
what you want to do.
Some compilers by default assume sizeof(void) = 1 (e.g. the same as
char in all its qualifications) for simplicity, but this is far from
portable.
Regards,
Jens
--
Jens Schweikhardt htt
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscrib
c/share/misc/reorder
#
# Any ideas?
Please use plain TERM=xterm which now has color support. If any problems
remain, please let me know.
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [E
Sheldon,
On Wed, Aug 28, 2002 at 07:35:32PM +0200, Sheldon Hearn wrote:
# On (2002/08/28 19:04), Jens Schweikhardt wrote:
#
# > Yes, use plain TERM=xterm. It's got color now as it should. I'm thinking
# > of removing xterm-color if I can't resolve the enter_alt_charset_m
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Aug 29, 2002 at 05:03:17PM +0400, Vladimir B. Grebenschikov wrote:
# ? Wed, 28.08.2002, ? 23:46, Bruce A. Mah ???:
# > If memory serves me right, Jens Schweikhardt wrote:
# >
# > > # Do you have time to commit mention of it to UPDATING? If so, please
# > >
$ xfd -fn whateverfont
and look at the first 32 characters.
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
80 (active)
beg: cyl 1022/ head 254/ sector 63;
end: cyl 1022/ head 254/ sector 63
# disklabel da4s2
disklabel: ioctl DIOCGDINFO: Invalid argument
Am I trying something that is not supported? If yes, are there any
plans to support our brother BSD's disklabels?
Regards,
On Sun, Oct 13, 2002 at 05:20:11PM +0200, Poul-Henning Kamp wrote:
# In message <[EMAIL PROTECTED]>, Jens Schweikhardt writes:
# >Poul-Henning et al,
# >
# >recently I've tried installing NetBSD on a new disk. I'm not sure if the
# >following is a coincidence (because
David et al,
# So what broke this?
# -- David ([EMAIL PROTECTED])
Has this been fixed? I observe the same on FreeBSD 5.0-CURRENT #4: Fri
Mar 8 19:51:15 CET 2002 and am wondering if a make world would fix this.
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG
netmap # netmap(4) support
device crypto # Required by IPSEC
options EXT2FS
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=100
options IPDIVERT
Regards,
Jens
ommit the fix.
I can confirm that this patch fixes it! Please commit. Many thanks!
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
___
freebsd-current@freebsd.org mailing list
y. If I want to sleep longer than 3
digit amount in secs, I do the math. The POSIXly *portable* way to do
this and document it for the mathematically challenged is
sleep $((2*60*60))# 2h
sleep $((7*24*60*60)) # 1w
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
Alexander,
it would seem that
find /usr/local/*bin* /usr/local/lib* -type f \
| xargs ldd -f '%p|%A\n' 2>/dev/null \
| grep '^not found' | cut -d '|' -f2 \
| xargs pkg which -q | sort -u
is prone to false positives, since ldd is sensitive to LD_LIBRARY_PATH, viz.:
$ find /usr/local/*bin* /usr/l
Identifier confusion? You use _rc_svcs and _rc_svcj in your description.
Jens
Hello *,
Looks like a semicolon is missing after the "fi".
Jens
- Ursprüngliche Mail -
Von: "Ed Maste"
An: "FreeBSD User"
CC: "freebsd-current"
Gesendet: Freitag, 1. April 2022 15:50:31
Betreff: Re: CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file
or directory *** Error
ss:esp=45 b8 03 00 f0 0c d4 bs-00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
BTX halted
Is that related to recent loader crash reports?
How can I recover?
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core
38 matches
Mail list logo