On 5/24/2013 1:33 PM, Brian Reichert wrote:
On Fri, May 24, 2013 at 04:57:44PM +, Welcome, Traiano wrote:
Hi Julian
Thanks, any response is appreciated, here's mine:
I typed into Google: "how to write an OS", and got lots of hits.
Have you explored them?
http://www.acm.uiuc.edu
If you're just doing virtualization and not worrying about security,
there's a simple test. Don't set "devfs_enable" in rc.conf, and instead
add a devfs line to the jail's fstab file. It should give full access
to everything in the host's /dev.
On 5/9/2013 4:07 AM, Alexander Leidinger wrote:
On 4/26/2013 7:23 AM, Eitan Adler wrote:
Yes, rm's functionality can be fully replicated by find.
As well as anything using -R.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, se
On 4/25/2013 3:35 PM, Tuc wrote:
Hi,
Figured this might be a bit more than -questions worthy...
I was following some instructions online about upgrading 7 to 8...
And... Well... Something went horribly wrong during "make installworld".
I lost my ssh session (Mistake 1 - Console dummy!) and now
On 4/19/2013 8:48 PM, Jeremy Chadwick wrote:
I'm happy to open up a ticket with VMware about the issue as I'm a
customer, but I find it a little odd that other operating systems do not
exhibit this problem, including another BSD. Ones which reboot just
fine from their bootloaders:
- Linux -- so
Basically, the loader finds a simple safe way to reboot that's worked
since the 286, and VMWare doesn't like it. It's called a triple fault.
FreeBSD and Linux even use it to reboot as a fail safe. Read
sys/i386/i386/vm_machdep.c and cpu_reset_real to see how FreeBSD handles
it. VMWare at le
On 4/16/2013 3:40 AM, Hans Petter Selasky wrote:
On 04/15/13 22:14, Joshua Isom wrote:
On 4/15/2013 5:41 AM, Hans Petter Selasky wrote:
Hi,
What does dmesg say about your printer.
Is cups hooked up the correct /dev/uxxx device ?
--HPS
Here's what I got the last time I plugged it in.
On 4/15/2013 5:41 AM, Hans Petter Selasky wrote:
Hi,
What does dmesg say about your printer.
Is cups hooked up the correct /dev/uxxx device ?
--HPS
Here's what I got the last time I plugged it in.
Apr 13 07:38:17 jri root: Unknown USB device: vendor 0x040a product
0x4043 bus uhub7
Apr 13
I've got my printer to finally work, now that I got around to hooking it
up again and trying. It's a Kodak AiO, and there's a driver that's been
around for a few years and works under Linux. It doesn't work properly
under FreeBSD, or a Debian/kFreeBSD jail, but does work under a Linux
jail.
On 4/10/2013 9:43 AM, Jonathan Anderson wrote:
The last I heard, LTO on the kernel required something like 16 GB of RAM and
produced a not-quite-working image.
Jon
I upgraded my system with 32Gb for a reason.
___
freebsd-hackers@freebsd.org maili
On 4/9/2013 1:47 PM, Edward Tomasz Napierała wrote:
In order to optimize - in this case for size - we need a way to measure
what should we focus on, and it looks like we don't have it yet.
Would it be possible to write a tool - e.g. by instrumenting LLVM - that
would make it possible to calculat
On 4/1/2013 11:45 AM, Kimmo Paasiala wrote:
On Mon, Apr 1, 2013 at 7:30 PM, Chris Rees wrote:
On 1 April 2013 17:13, wrote:
Try "DESTDIR='/usr/TZ\ ONE'; export DESTDIR".
You need to escape the space.
This is '#!/bin/sh' scripting.
Doing so "fixes" *.mk, but breaks sh => dir simply doesn't
Try "DESTDIR='/usr/TZ\ ONE'; export DESTDIR".
You need to escape the space.
On 3/31/2013 8:38 AM, rank1see...@gmail.com wrote:
Under 9.0-RELEASE-p6
--
#!/bin/sh
# Contains 9.0 world
DESTDIR='/usr/TZ ONE'; export DESTDIR
cd /usr/ports/benchmarks/unixbench
/usr/bin/make showconfig
--
Errors
On 3/25/2013 2:41 AM, Andriy Gapon wrote:
on 25/03/2013 02:19 Joshua Isom said the following:
I thought the debugger would have worked regardless.
No, kgdb and libkvm have to be in sync with kernel.
Unfortunately.
Is it a bug or necessity
So far they've been out of sync. I'd done it once before with a 6 base
and 7 kernel to get some hardware to work. I installed world in a
chroot and kgdb seems to be working fine in the chroot. I thought the
debugger would have worked regardless.
On 3/24/2013 4:49 PM, Adrian Chadd wrote:
Hi
Backtrace gives me an error. The only backtrace I'm given is from the
kernel message while it's crashing. After it's crashed I'm getting nothing.
[jri:~] root# kgdb -q /boot/kernel/kernel /var/crash/vmcore.30
Reading symbols from /boot/kernel/zfs.ko...Reading symbols from
/boot/kernel/zfs.ko.
I have several core dumps that need debugged. All are the same problem.
The debugging problem is when I fire up kgdb, I have to backtrace even
though the kernel message buffer contains a back trace. If I try to set
the frame with "frame 0xff8020bddb30" I get an error "Cannot access
memor
On 2/12/2013 10:20 AM, Kevin Day wrote:
I'm not sure if this is the right place to post this, so if you know of anyone
who may be interested in this please forward to them. Right now my company
(your.org) does the free amd64/i386 VMs for FreeBSD developers.
For an unrelated project, we're try
On 3/25/2012 11:10 AM, Alfred Perlstein wrote:
It's kind of insane how much memory the compiler uses these days.
Any other options?
Switch to clang which uses less memory, or use a smaller jobs number.
Memory use is inevitable, but the benefit is more efficient binaries.
On 3/3/2012 6:30 PM, Dimitry Andric wrote:
Huh, that's weird. I see no reason that it wouldn't install cc during
the cross-tools stage, unless you have WITHOUT_GCC in your src.conf (and
aren't using WITH_CLANG_IS_CC at the same time).
Can you post your src.conf file, please?
I've had this ha
On 2/14/2012 10:57 AM, Julian Elischer wrote:
On 2/14/12 6:23 AM, Maninya M wrote:
For multicore desktop computers, suppose one of the cores fails, the
FreeBSD OS crashes. My question is about how I can make the OS tolerate
this hardware fault.
The strategy is to checkpoint the state of each cor
On 9/11/2010 10:18 AM, Aryeh Friedman wrote:
ys of work and as I said the only reason
for all this is to make the client comfortable and not that I do not
trust the team (I do trust them)
Write a script that gets executed in the background once you log in that
will periodically check to make s
On Apr 26, 2008, at 4:35 PM, Romain Tartière wrote:
Hello FreeBSD hackers!
I'm using avr-gcc from the ports and relying on the 0b prefix notation
for binary constants, that is:
foo = 0b00101010;
Thanks to /usr/ports/devel/avr-gcc/files/patch-0b-constants this is
possible :-)
But I w
Instead of all the debate about GNU compatibility and the fact that the
patch adds a feature not readily available, why not improve FreeBSD's
find without caring about GNU's find? I have not seen a way to capture
output from a command and compare it to another command. Imagine
something conce
On Feb 20, 2008, at 3:44 PM, Marcel Moolenaar wrote:
That would be possible. But then there will be other
problems. For example, lets say that the i386 loader
decides to use 640x480 @4bit, and the sparc64 loader
decides that 1152x900 @8bit is "best".
The Forth code clearly needs a way to que
On Jan 19, 2008, at 10:03 AM, Doug Barton wrote:
Yuri wrote:
I tried to make a backup copy of one DVD that I own and 'dvdbackup'
always fails at a particular point.
Would the dvds in question happen to be Sony movies? If so a web
search might be useful to you.
Doug
Not only that, but d
On Jan 8, 2008, at 9:25 PM, Bharma Ji wrote:
Thanks for the response. I am hoping to keep some memory aside
specifically
for handling out of memory allocation situations. Yes the real fix is
to
avoid out of memory allocation. Thanks for the patch. Will try that.
As a
first cut I am just t
Redirected from freebsd-questions after no reply.
I currently have an SATA DVD-RW drive for my computer. I have to boot
using a CURRENT kernel to get the drive recognized, and dmesg lists it
as running at 3.3MB/s. Running mplayer -dumpstream gets around 3 megs
a second. Copying off a data d
I think some mention of ATAPI SATA drives should be mentioned. I have
an SATA DVD-RW drive that needs a 7.0 kernel to be recognized, and
given some comments on the list, the problem seems to be have been
support for ATAPI SATA drives on FreeBSD 6.x(it's not in -STABLE). The
chipset on the mot
As some may remember, about a month ago I asked a question about my dvd
drive, apparently an sata atapi drive. Updating to a 7.0-current/amd64
kernel did allow it to be recognized and I've been able to use it. But
recently I'd been noticing a kernel crash I could create. My computer
is h
On Jul 25, 2007, at 2:05 PM, Andrey V. Elsukov wrote:
25.07.07, 22:07, Joshua Isom <[EMAIL PROTECTED]>:
Can you try the last CURRENT snapshot with your drive?
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/
I guess the problem is with a SATA controller support...
--
WBR, Andrey V. E
I've reposted this from freebsd-questions, and added some minor details.
Yesterday I bought and installed a Lite-ON SATA DVD Writer for my
computer. But FreeBSD fails to recognize it at all. I'd wondered if
something was broken on the motherboard or the drive or if something
wasn't hooked
32 matches
Mail list logo
