Originally posted by cbkihong I do understand there can be more problems if I don't stick to ports/packages and compile everything myself. I compiled xfree86 4.3.0 from sources as I can't find that version from my ports. My compiled x-windows works perfectly. But it seems by doing so I can no longer use ports/packages for any x applications as the ports assume xfree86 4.2.0 instead of 4.3.0. if I use those ports/packages then xfree 4.2.0 would be fetched and installed, and that is definitely not what I want.
I compiled XFree86 4.3.0 on my FreeBSD 5.1-BETA installation from the ports tree this past weekend. Is your ports tree up to date?
I normally install from the ports tree, update the ports tree via cvsup and use `portupgrade --all` to recompile all the ports that I have installed.
Many of the ports have ./configure style options that you can use on the make command line in the form of:
or
The FreeBSD handbook has all the nitty gritty details.
question:
i just installed FreeBSD 4.7 on my laptop, when i log in as root, i can startx no problem at all but when i try to start it as a user, i can't. otiginally it told me i needed to be a member of the group 'wheel' to do startx, no problem, added myself in /etc/group, but for some reason i... (1 Reply)
i'm following the, "How to setup and secure Snort, MySQL and Acid on FreeBSD 4.6 Release" off of the snort.org website.
in the documentation it says snort should be installed through the following:
-----
make -DWITH_MYSQL -DWITH_FLEXRESP ; make install
-----
later it says to do the... (13 Replies)
All,
I am a bit of a BSD newbie and haven't really played with it for years, but I have had a recent situation whereby someone attempted to load a custom kernel module and ended up breaking my BSD server.
I managed to fix it by doing the following:
Booting into loader mode:
unload
set... (3 Replies)
Hello there,
My mulithreaded application (which is too large to represent the source code here) is crashing after installing FreeBSD 7.1-RELEASE/amd64.
It worked properly on others machines (Dual Cores with 4GB of RAM - FreeBSD 6.2-RELEASE/i386).
The current machine has 2x Core 2 Duo... (1 Reply)
Server: FreeBSD 7.2-RELEASE
MYSQL Version: MYSQL 5.1.36
PHP Version: 5.2.10 (apache2handler)
IP.Board Version: v3.0.2
Safe Mode: OFF
For the most part previously IP.Board, forum software, has run fine without any issues. Regular web pages and .php pages seem to load fine without any issues.... (2 Replies)
I wrote a script to batch-create directories with .htaccess and .htpasswd files.
I am using the following line to create the .htpasswd file:
htpasswd -cb .htpasswd $USER $PASS
However, I keep getting this message in return:
Usage: htpasswd passwordfile username
The -c flag creates a new... (1 Reply)
Hi!
I have a major issue with FreeBSD 7.1 i386.
We did a change in our Unix env where we exchanged home storage from a NetAPP running udp to a NetAPP running tcp.
Now I cant mount homedirs since NFS/AMD seem to fallback to udp :(
Trying to force it with amd options nfs_proto=tcp and so on.
... (0 Replies)
(1) Hi, Am working on FreeBSD 7.4/i386 and installed Opera 11.01 through ports collection manually... But when I run first time am getting "opera: cannot connect X server. Error: Unknown error: 0" What is this error all about???? Please help me to sort out this issue!!!
(2) Hi, currently am... (12 Replies)
Hello,
I'm attempting to setup a test network with a client-server based architecture using a proprietary application. The client works by communicating with the server on separate links (typically cellular connections) and then initiates a tunnel over each active link. However, in place of the... (0 Replies)
I just got FreeBSD up and running with an XFCE desktop on an old Gateway laptop. It works great, except the wireless setup is scaring me. I can connect to my home WiFi fine most of the time, but I'm concerned about other WiFi that I will need to connect to away from home.
I understand that I can... (1 Reply)
Discussion started by: BrentBANKS
1 Replies
LEARN ABOUT SUSE
aconnect
aconnect(1) General Commands Manual aconnect(1)NAME
aconnect - ALSA sequencer connection manager
SYNOPSIS
aconnect [-d] [-options] sender receiver
aconnect -i|-o [-options]
aconnect -x
DESCRIPTION
aconnect is a utility to connect and disconnect two existing ports on ALSA sequencer system. The ports with the arbitrary subscription
permission, such as created by aseqview(1), can be connected to any (MIDI) device ports using aconnect. For example, to connect from port
64:0 to 65:0, run as follows:
% aconnect 64:0 65:0
The connection is one-way, and the whole data to the sender port (64:0) is redirected to the receiver port (65:0). When another port (e.g.
65:1) is attached to the same sender port, the data is sent to both receiver ports. For disconnection, use -d option.
% aconnect -d 64:0 65:0
The address can be given using the client's name.
% aconnect External:0 Emu8000:1
Then the port 0 of the client matching with the string "External" is connected to the port 1 of the client matching with the "Emu8000".
Another function of aconnect is to list the present ports on the given condition. The input ports, which may become sender ports, can be
listed with -i option.
% aconnect -i
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 64: 'External MIDI-0' [type=kernel]
0 'MIDI 0-0 '
Similarly, to see the output ports, use -o flag.
You can remove all existing exported connections using -x option. This function is useful for terminating the ALSA drivers, because the
modules with sequencer connections cannot be unloaded unless their connections are removed.
OPTIONS
CONNECTION MANAGEMENT
-d, --disconnect
Disconnect the given subscription.
-e, --exclusive
Connect ports with exclusive mode. Both sender and receiver ports can be no longer connected by any other ports.
-r, --real queue
Convert time-stamps of event packets to the current value of the given real-time queue. This is option is, however, not so useful,
since the receiver port must use (not necessarily own) the specified queue.
-t, --tick queue
Like -r option, but time-stamps are converted to the current value of the given tick queue.
LIST PORTS
-i, --input
List existing input (readable) ports. This option is exclusive to -o.
-o, --output
List existing output (writable) ports. This option is exclusive to -i.
-l, --list
List the current connection status. The connected and connecting ports from/to each port are listed together. The suffix flag [ex]
means the connection is exclusive. The suffix flag [real:#] and [tick:#] mean the connection includes real-time and tick conversion
on the listed queue, respectively.
REMOVE ALL CONNECTIONS
-x, --removeall
Remove all exported connections.
SEE ALSO aseqnet(1), aseqview(1)AUTHOR
Takashi Iwai <tiwai@suse.de>
August 31, 2000 aconnect(1)