I have my .cshrc file run some basic netstat and 'w' commands so that when I
log
in, I can see at a glance what is going on on the system and notice any unusual
login activity, etc.
However this completely breaks both scp and rsync - they cannot function at all
(apparently) with any kind of st
It appears that many PCMCIA network cards no longer work in FreeBSD - this is
documented here:
http://www.freebsd.org/cgi/query-pr.cgi?pr=115623
However there appears to be a workaround, wherein one sets their
hw.cbb.start_memory value manually. Suggested values for xircom cards are:
sysctl h
Most modern IP KVMs allow you to specify a ISO image, and they will feed it to
the computer via USB and allow you to boot arbitrary "cds".
However, I notice problems in both standard FreeBSD install discs and
FreeBSD-based live CDs, wherein the CD will boot and run just fine, but when it
comes
A 3ware raid5 array I had died.
It looks like the data is intact, and there are two good recovery methods:
1) a toolchain from 3ware that, if it doesn't work, will destroy the data.
This method is free, and I can do it myself.
2) professional forensic services. Costs a lot.
I'm going to st
Hello,
I am using a particular program that has a command line option to "chroot to
the current directory".
But I would like to make sure ... I want to be sure what directory the
executable is actually rooted in.
How can I do this ? Perhaps with lsof ?
I don't see any information from the 'p
I have added a very standard, very common regex line to my .procmailrc to
filter character sets I can't read:
UNREADABLE='[^?"]*big5|iso-2022-jp|ISO-2022-KR|euc-kr|gb2312|ks_c_5601-1987|ks_c_5601|3Deuc-kr|koi8'
:0:
* ^Content-Type:.*multipart
* B ?? $ ^Content-Type:.*^?.*charset="?($UNREADABLE
> Virgin 7.2-RELEASE install.
>
> I run:
>
> csup -h cvsup4.freebsd.org -i ports/lang/python26 -g -L 2
> /usr/share/examples/cvsup/ports-supfile
>
> and now I have a /usr/ports/lang/python26/distinfo that looks like:
>
> MD5 (python/Pyt
Virgin 7.2-RELEASE install.
I run:
csup -h cvsup4.freebsd.org -i ports/lang/python26 -g -L 2
/usr/share/examples/cvsup/ports-supfile
and now I have a /usr/ports/lang/python26/distinfo that looks like:
MD5 (python/Python-2.6.4.tgz) = 17dcac33e4f3adb69a57c2607b6de246
SHA256 (python/Python-2.6.4.
I see these two entries in my /var/log/messages:
Nov 24 18:08:41 hostname kernel: pid 25901 (try), uid 0: exited on signal 10
(core dumped)
Nov 24 18:10:29 hostname kernel: pid 35359 (try), uid 0: exited on signal 10
(core dumped)
But I've never heard of a "try" binary, and 'which try' shows
I do some automated account creation on a FreeBSD 6.x system ... and
unbeknownst to me, the '/' filesystem was completely full when I did my last
account creation, resulting in:
/: write failed, filesystem is full
pwd_mkdb: /etc/pwd.db to /etc/pwd.db.tmp: No space left on device
pw: passwd fil
- Original Message
> From: Gary Gatten
> To: George Sanders ; freebsd-questions@freebsd.org
> Sent: Wed, October 28, 2009 11:01:35 AM
> Subject: RE: How do I replace the built-in OpenSSL with a source tarball ?
>
> Maybe remove the existing package first? And t
I would like to:
- upgrade the built-in OpenSSL that comes with FreeBSD (in my case, 6.4-RELEASE)
- replace it with OpenSSL that I build myself from the source tarball
If I do this with a plain old: ./config ; make ; make install
OpenSSL does indeed build and install, but it installs in an
I've been doing this dance:
../configure ; make ; make install
for about ten years now. Sometimes there are some little issues, but nothing
too crazy.
I tried to build 'git' from source today, however, and it doesn't behave like
anything I've ever seen...
I do the ./configure and it comple
13 matches
Mail list logo
