02-14-2005
It might not be the burner, but how the burner is configured, etc.
Not all burners are created equal....
Some are easer than others, IYKWIM.
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
Hi, would anybody kindly help me as I am new in FreeBSD 4.4 (downloaded iso image from FreeBSD.org) and have installed it to an HP VEctra Pentium 1-166Mhz PC, have installled all the devices mouse,video card,monitor and some ports specifically to Xfree86 and all gnome related to "X" but when I type... (3 Replies)
Discussion started by: charlie499
3 Replies
2. Programming
I am trying to send a SIGUSR1 to a set of process. Please tell
me how to do. I've tried the system call raise(int sig) but it just
raise a signal of to the 'current process.'
My program is about a network chat server. When a client
connects in, The main process will fork a new process... (1 Reply)
Discussion started by: Namely
1 Replies
3. UNIX for Dummies Questions & Answers
I recently installed FreeBSD on my Dell Inspiron 1100 and it works fine. The problem is that I dont know how to connect it to the internet. I have a Linksys Wireless B Network Adapter but if I cant use that, I can use my internal 10/100 Ethernet card. I also use a Linksys Wireless B & G router. ... (1 Reply)
Discussion started by: Mincuslcd
1 Replies
4. UNIX for Dummies Questions & Answers
hi. I am newbie in Unix. I wanted to install Free BSD 5.2.1 to my computer which winXp was already installed. But i couldn't.
I chose Standard. Then it said you are going to use dos style fdisk partitioning. Then a window displayed begining like this.
WARNING: A geometry of 155127/16/63 for... (2 Replies)
Discussion started by: sualcavab
2 Replies
5. UNIX for Advanced & Expert Users
See below:
root#host:/home>ls -la | grep mirus
drwxr-xr-x 31 mirus staff 2048 Dec 30 11:01 mirus
root#host:/home>su mirus
su: /home/mirus/.bashrc: Permission denied
mirus#host:/usr/home>id
uid=1227(mirus) gid=20(staff) groups=20(staff)
mirus#host:/usr/home>cd ~/
su: cd:... (3 Replies)
Discussion started by: mirusnet
3 Replies
6. UNIX for Dummies Questions & Answers
i have installed freeBSD 7.0 using the 5 cds.
when i try to install the gnome or kde during the post-installation, the following error appears:
"ghost-script gpl-8.60 aborted error 1 ......."
Do u think that the cd(it's the second cd) is corrupted or i missed some steps which i should follow.
I... (1 Reply)
Discussion started by: solomonml
1 Replies
7. Filesystems, Disks and Memory
I am trying to setup 2 network shares that exist on a server. One of the shares is mounted but when i try to mount the second share I am greeted with:
# mount srv:/data/music /data/music
srv:/data/music: RPCPROG_NFS: RPC: Program not registered
Server Info:
name: srv
#cat /etc/exports:... (0 Replies)
Discussion started by: ezekiel61
0 Replies
8. BSD
Hello,
when I try to install freeBSD in Virtualbox it always reboots when copying the files for the OS.
Does anyone know what's wrong? It must be the VM Settings, but I can't seem to get behind it...
any help would be very nice.
I have to old and new freeBSD Versions. (new = downloaded... (1 Reply)
Discussion started by: Dr. Nick
1 Replies
9. UNIX for Dummies Questions & Answers
Hello everybody.
I have a problem of this kind: After installation of FreeBSD, my Windows XP became unreachable. Boot from CDROM is impossible. The conclusion: BIOS was damaged by GParted or some other program. Question:
Are there any Unix means of updating (repairing) BIOS ?:wall: (11 Replies)
Discussion started by: prabux
11 Replies
10. UNIX for Dummies Questions & Answers
I created a VM for FreeBSD on hyper-v and i am having trouble connecting it to the internet. My virtual machine config are as below:
100 GB HD
1GB RAM
Generation 1
Two Network adapters
1. Legacy Network Adapter
2. Network Adapter
both are connected to network switch "Internet" which... (2 Replies)
Discussion started by: Vishawdeep
2 Replies
AOUT(4) BSD Kernel Interfaces Manual AOUT(4)
NAME
aout -- kernel support for executing binary files in legacy a.out format
SYNOPSIS
kldload a.out
DESCRIPTION
The a.out(5) executable format was used before the release of FreeBSD 3.0. Since i386 was the only supported architecture at that time,
a.out(5) executables can only be activated on platforms that support execution of i386 code, such as i386 and amd64.
To add kernel support for old syscalls and old syscall invocation methods, place the following options in the kernel configuration file:
options COMPAT_43
options COMPAT_FREEBSD32
The COMPAT_FREEBSD32 option is only required on 64-bit CPU architectures.
The aout.ko module needs to be loaded with the kldload(8) utility in order to support the a.out(5) image activator:
kldload aout
Alternatively, to load the module at boot time, place the following line in loader.conf(5):
aout_load="YES"
The a.out(5) format was mainstream quite a long time ago. Reasonable default settings and security requirements of modern operating systems
today contradict the default environment of that time and require adjustments of the system to mimic natural environment for old binaries.
The following sysctl(8) tunables are useful for this:
security.bsd.map_at_zero Set to 1 to allow mapping of process pages at address 0. Some very old ZMAGIC executable images require
text mapping at address 0.
kern.pid_max Old versions of FreeBSD used signed 16-bit type for pid_t. Current kernels use 32-bit type for pid_t, and
allow process id's up to 99999. Such values cannot be represented by old pid_t, mostly causing issues for
processes using wait(2) syscalls, for example shells. Set the sysctl to 30000 to work around the problem.
kern.elf32.read_exec Set to 1 to force any accessible memory mapping performed by 32-bit process to allow execution, see mmap(2).
Old i386 CPUs did not have a bit in PTE which disallowed execution from the page, so many old programs did
not specify PROT_EXEC even for mapping of executable code. The sysctl forces PROT_EXEC if mapping has any
access allowed at all. The setting is only needed if the host architecture allows non-executable mappings.
SEE ALSO
execve(2), a.out(5), elf(5), sysctl(8)
HISTORY
The a.out(5) executable format was used on ancient AT&T UNIX and served as the main executable format for FreeBSD from the beginning up to
FreeBSD 2.2.9. In FreeBSD 3.0 it was superseded by elf(5).
AUTHORS
The aout manual page was written by Konstantin Belousov <kib@FreeBSD.org>.
BUGS
On 64bit architectures, not all wrappers for older syscalls are implemented.
BSD
August 14, 2012 BSD