Diskless boot troubles
The harddisk of mdesktop machine is no longer detected by my beastie
server (both are FreeBSD RELEASE 6.0 GENERIC).
So I want to perform a diskless boot. I've come to the point where I am
successfully booting by means of pxeboot and the isc-dhcp3-server: it
loads the kernel, shows the menu, I see the normal boot messages rolling
off the screen, it detects my local cd drive and then logs the mounting of
the root file system:
Trying to mount root from ufs:/dev/ads1a
Trying to mount root from nfs:
NFS ROOT: 192.168.1.10:/diskless_root
sis0: link state changed to UP
Interface sis0 IP-address 192.168.1.2 Broadcast 192.168.1.255
Mon Feb 27 20:11:30 UTC 2006
And this is where it stops. Nothing happens any more. I have no idea where
I could dig up some additional info.
Any suggestion or help would be most welcome.
BTW, I had to make some modifications to /usr/share/examples/clone_root to
create the diskless root file system.
1) The 3 'tar cvf | tar xvf constructs' caused an error messages
complaining about the differences in treatment of the -1 option between
bsd tar and gnu tar. Executing the script with -x and -v did not clarify
this situation: there is no such option used in this script; so I replaced
the tar constructs with 'find | cpio' constructs.
2) The 'TOCOPY' variable does omit the 'lib' and 'libexec' directories.
When these are absent in the diskless directory structure, the boot
process is interrupted as /bin/sh doesn't find some shared libraries. So I
added both dirs to the TOCOPY variable.
Here's the diff:
21:11:55 beastie:/usr/share/examples/diskless# diff clone_root.orig
clone_root
1a2
# $File: clone_root 2006-02-27 18:33 +0100 [EMAIL PROTECTED] $
80c81,82
< TOCOPY="bin boot compat etc modules sbin stand sys"
---
#TOCOPY="bin boot compat etc modules sbin stand sys"
TOCOPY="bin boot compat etc lib libexec modules sbin stand sys"
90c92,93
<(cd / ; tar -clf - ${TOCOPY} ) | (cd $DEST; tar xvf - )
---
#(cd / ; tar -clf - ${TOCOPY} ) | (cd $DEST; tar xvf - )
(cd / ; find -d ${TOCOPY} | cpio -pudm $DEST)
100c103,104
<(cd / ; tar clf - conf ) | (cd ${DEST}; tar xvf - )
---
#(cd / ; tar clf - conf ) | (cd ${DEST}; tar xvf - )
(cd / ; find -d conf | cpio -pudm $DEST)
102c106,110
<(cd /etc ; tar cvf - ${PWFILES} ) | (cd ${DEST}/etc ; tar xf - )
---
#(cd /etc ; tar cvf - ${PWFILES} ) | (cd ${DEST}/etc ; tar xf - )
for i in ${PWFILES}
do (cd /etc ; find $i | cpio -pudm $DEST/etc)
done
138a147
# $File: clone_root 2006-02-27 18:33 +0100 [EMAIL PROTECTED] $
21:12:55 beastie:/usr/share/examples/diskless#
(Forget about the 2 # $File:... lines, they are for local use only)
I am not sure whether these modifications should be officialised, so I
just submit them here to the user community for validation and/or comments.
But I'd be so happy to read any advice about how I could proceed with
diskless booting...
Guido
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
building for diskless support: unknown option mfs
Hi, I try to build a kernel that supports dsikless booting (on a FreeBSD-RELEASE-6.0). I have copied the GENERIC config file as DISKLESS and added following lines (as described in /usr/share/examples/diskless/clone_root: options MFS options BOOTP options BOOTP_NFSROOT options BOOTP_COMPAT When I start building the DISKLESS kernel, I get following output: 23:58:56 beastie:/usr/src# make buildkernel KERNCONF=DISKLESS -- Kernel build for DISKLESS started on Sun Feb 26 23:59:30 CET 2006 -- ===> DISKLESS mkdir -p /usr/obj/usr/src/sys -- stage 1: configuring the kernel -- cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/DISKLESS /usr/src/sys/i386/conf/DISKLESS /usr/src/sys/i386/conf/DISKLESS: unknown option "MFS" *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. 23:59:30 beastie:/usr/src# Did I overlook something? Is this option obsolete or so? It is not mentioned in the handbook. Please advise. TIA, Guido. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Default browser
On Wed, 08 Feb 2006 21:21:41 +0100, Tom Grove <[EMAIL PROTECTED]> wrote: Guido Van Hoecke wrote: Beto, I took your advice and solved the mess as you suggested. Did you get java working with opera? Yep, I am using linux-opera 8.51 and both linux-sun-jdk1.4.2 and linux-blackdown-jdk1.4.2 are working. I even managed to use them for my on-line banking here in Belgium, although my KBC bank does not support opera :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Default browser
Beto, I took your advice and solved the mess as you suggested. I just deinstalled both mozilla and firefox and symlinked /usr/X11R6/bin/linux-opera to /usr/X11R6/bin/mozilla and to /usr/X11R6/bin/firefox. Thanks, Guido ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Default browser
>What has to be done to change the default browser from mozilla into e.g. >opera or firefox (assuming that these are duly installed and operational)? > >The handbook talks about different browsers, but I have not been able to >find a section about changing the default browser. It guess I should have been more specific. I am using Window Maker as window manager. I know that KDE has the Component Chooser and Gnome has its gnome-control-center/preferred applications, but I have not found a window maker equivalent. Frankly, I do not know if there is such a thing. Both KDE and Gnome have been told that I'd like to use linux-opera. Still, when I click a link in bpm (bsd ports collection manager port), this event seems to disappear in the eternal bit bucket and nothing happens. When I click a link in a gaim chat window, mozilla gets launched. Openoffice.org insists upon firefox. Why is this so messy? How do I change it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Default browser
What has to be done to change the default browser from mozilla into e.g. opera or firefox (assuming that these are duly installed and operational)? The handbook talks about different browsers, but I have not been able to find a section about changing the default browser. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dvdwriter - icybox - usb problem
Fabian Keil wrote: Guido Van Hoecke <[EMAIL PROTECTED]> wrote: I have to connect my Plextor PX-716A dvd-writer via an external IDE-to-USB/1394 Icybox (IB-550UE-B-BL) to my freebsd-6.0-RELEASE pc. This pc is an IBuddy Desknote A928 without room for internal extra devices. So I bought an Icybox enclosure, put the plextor in it and connected the icybox through USB: umass0: vendor 0x0402 USB 2.0 Storage Device, rev 2.00/1.05, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 0MB (1 0 byte sectors: 0H 0S/T 0C) [EMAIL PROTECTED]:~> sudo cdrecord -scanbus Cdrecord-Clone 2.01 (i386-unknown-freebsd6.0) Copyright (C) 1995-2004 Jörg Schilling Using libscg version 'schily-0.8'. ... scsibus3: 3,0,0 300) 'USB 2.0 ' 'Storage Device ' '0111' Disk ... [EMAIL PROTECTED]:~> How do I tell FreeBSD that this is a DVD-writer rather than a hard disk? Have you tried to use it? Does cdrecord dev=3,0,0 -prcap show false information as well? No, I did not try it. Ms XP had the same problem when connecting over USB. However, connecting over firewire to XP was ok. Due to lack of time for further experimenting, the plextor is now built in into my freebsd server as a normal ide device. So this is now a non-problem. Thanks for your reply though, Guido. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dvdwriter - icybox - usb problem
I have to connect my Plextor PX-716A dvd-writer via an external IDE-to-USB/1394 Icybox (IB-550UE-B-BL) to my freebsd-6.0-RELEASE pc. This pc is an IBuddy Desknote A928 without room for internal extra devices. So I bought an Icybox enclosure, put the plextor in it and connected the icybox through USB: umass0: vendor 0x0402 USB 2.0 Storage Device, rev 2.00/1.05, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 0MB (1 0 byte sectors: 0H 0S/T 0C) [EMAIL PROTECTED]:~> sudo cdrecord -scanbus Cdrecord-Clone 2.01 (i386-unknown-freebsd6.0) Copyright (C) 1995-2004 Jörg Schilling Using libscg version 'schily-0.8'. ... scsibus3: 3,0,0 300) 'USB 2.0 ' 'Storage Device ' '0111' Disk ... [EMAIL PROTECTED]:~> How do I tell FreeBSD that this is a DVD-writer rather than a hard disk? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
kdm setup for remote login
Hi, I have been reading man pages, the freebsd manual, kde.org (now offline?) pages, I've been experimenting with different setups, but I do not manage to setup X as I wish. I have a server called beastie, and a desktop called wodan. Both machines start kdm on ttyv8 and allow for local login. When I use xfce4 on wodan (before I had ttyv8 on) and use xhost+, I can ssh to beastie, setup display=wodan:0 and start e.g. emacs, gnucash etc... When I use kdm/kde on wodan, xhost+ isn't enough. I can still ssh to beastie, but apps on beastie do not get acces to wodan:0, although I've done xhost+ on wodan. I do not know how to set up kde so that apps from another machine get access to the display. What I really would like, is to be able to login to beastie using the wodan kdm. I have not been able to figure out how to do this. Any help would be really appreciated. Guido ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Page fault in kernel mode, 6.0-RELEASE
Kris Kennaway <[EMAIL PROTECTED]> writes: > On Tue, Nov 15, 2005 at 11:48:15PM +0100, Guido Van Hoecke wrote: >> I am fairly new at FreeBSD. I installed a 'beastie' server with >> >> FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 >> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC >> >> but it traps immediately after the boot menu with following output >> immediately after the boot menu: >> >> /boot/kernel/acpi.ko text=0x40c2c data=0x2160+0x1090 \ >> syms=[0x4+0x7810+0x4+0xa292] >> >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0x8 >> fault code = supervisor read, page not present >> instruction pointer = 0x20:0xc079abb9 >> stack pointer = 0x28:0xc0c20d4c >> frame pointer = 0x28:0xc0c20d58 >> code segment= base 0x0, limit 0xf, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags= interrupt enabled, resume, IOPL = 0 >> current process = 0 () >> trap number = 12 >> panic: page fault >> Uptime: 1s >> >> Note that the /boot/kernel/acpi.ko line is absent if I boot with acpi >> disabled (menu option 2). But the trap info is not affected by slecting >> that boot option. > > Are you using other modules (e.g. nvidia driver)? No Kris, this is just when booting from the generic release cd's. I had an old Hercules 3d Prophet card and just used that, without loading anything special. > > Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Page fault in kernel mode, 6.0-RELEASE
I am fairly new at FreeBSD. I installed a 'beastie' server with FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC but it traps immediately after the boot menu with following output immediately after the boot menu: /boot/kernel/acpi.ko text=0x40c2c data=0x2160+0x1090 \ syms=[0x4+0x7810+0x4+0xa292] Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 fault code = supervisor read, page not present instruction pointer = 0x20:0xc079abb9 stack pointer = 0x28:0xc0c20d4c frame pointer = 0x28:0xc0c20d58 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 () trap number = 12 panic: page fault Uptime: 1s Note that the /boot/kernel/acpi.ko line is absent if I boot with acpi disabled (menu option 2). But the trap info is not affected by slecting that boot option. This is a 1.7 Ghz P4 with 1Gb mry and a fast 250Gb drive fully dedicated (using normal partition scheme, not 'dangourously dedicated') to FreeBSD. It has an MSI 845 Pro2 motherboard. I had this trap during the first install yesterday. So I restarted the installation and all went fine. After the installation, I rebooted beastie and had no problems. I was able to work on it locally as well as over an ssh connection to it. Some time late at night, beastie trapped as reported above. Since then, it never got beyond this trap. That's it. Full stop! I looked into the BIOS setup, trying to change default settings that might influence the kernel, such as disabling APIC mode. No success. I booted the machine from a memtest86 CD and had it testing the memory during several hours. No errors were detected. I ran all test programs I could find (a.o. using Hiren's boot cd), and didn't find any problems with the PC. Still, I am pretty sure there must be a problem with that PC. Booting from the FreeBSD-6.0-RC1 or FreeBSD-5.4R cd's causes the same trap at the same point. Well, right now they just reboot after the menu. And so does FreeSBIE 1.1 (FreeBSD 5.3 Live CD) I've been further experimenting with the BIOS, I have upgraded it to the latest version available from MSI. Bottom line is that now it does not trap anymore. After the boot menu, it goes a bit furthre. It shows the CopyRight and Release info and reboots automaticlally without any further info. Is there anything I can do to get more info about the reason for this frustrating behaviour? I do hope that more kernel-knowledgeable people will be able to point my nose in the proper direction, given the consistant moment where the error occurs. This is so frustrating, and I almost do feel ashame to dump this onto the FreeBSD community, but I am desperate to get this server installed and running! Guido. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i-buddie
i4o beke wrote: > Hi Guido. I've seen your question on freebsd-mobile, without answer. > I'd like to buy i-buddie, 3c or 4. So your problems with setup are > really interesting for me. > Is your sis network card working? Is it possible to > run XWin on i-buddie? Thank you for your answer. I am afraid I have had no luck with freebsd. My sis900 network card is recognized but fails with a 'MII without any PHY!', and 3 more devices are showing up as unknown: pci0 2.7 is a sis7012 audio driver pci0 5.0 is a conexant 56k modem pci0 7.0 ia a VIA OHCI Compliant IEEE1394 host controller Further more, XF86 as available in freebsd 4.6.2-RELEASE #0 does not recognize my lcd panel, so I can't run a desktop environment. I have not yet posted about the X problem, I wanted to have the sis900 network problem resolved first. FYI, I've installed mandrake 8.2 without a single hickup: all hardware recognized and configured properly in a very neat and smooth installation. Other distros which I've tried with less success are Red Hat 7.3, and Debian 3.0 I do like the iBuddy though! -- Guido Van Hoecke <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
sis900 : sis0 attach returned 6
Trying to install FreeBSD 4.6.2-RELEASE #0: Wed Aug 14 21:23:26 GMT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386 on a new ECS iBuddy4 desknote with sis900 fast ethernet card. The sis900 is never attached. When I look at dmesg output, I see repeated blocks about the sis900: => sis0: port 0xd400-0xd4ff mem 0xdfffb000-0xdfffbfff irq 5 at device 3.0 on pci0 => sis0: Ethernet address: (...mac address...) => sis0: MII without any PHY! => device_probe_and_attach: sis0 attach returned 6 I can use this device without problems under win2k. How can I proceed to get the sis900 working? -- Guido Van Hoecke <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: need help with pkg_add
TapRoot420 wrote: > Hello, I just installed FreeBSD 5.0 DP1 and everything is great with the system >except i cant get pkg_add to work via ftp. I am trying to install the current >afterstep package from the offical freebsd ftp server. > > Here is what i am trying per the handbook. > > # pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/5.0-CURRENT/p > ackages/afterstep/afterstep-1.8.11.tbz > Fetching ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/5.0-CURRENT/packages/af > terstep/afterstep-1.8.11.tbz... As mentionned earlier on this list, the 'tbz' format is the culprit. AFAIK, switchover to this format is being rolled back. -- Guido Van Hoecke <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: i-Buddie 4: Synaptics touch pad FreeBSD support?
> I specifically would like support for the Synaptics touch pad, but did > not find much in the FreeBSD documentation, nor in the ports collection. > > So I went to see at http://www.synaptics.com/support/downloads.cfm and > found a pointer to a linux 'tpconfig' touch pad driver available at > http://compass.com/synaptics/ which has not yet been ported to FreeBSD. Just for the record: the touchpad acts as a normal ps2 mouse and needs no special driver at all! (Thanx 2 hacker Brandon D. Valentine for the info) Hail FreeBSD! Guido. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
i-Buddie 4: Synaptics touch pad FreeBSD support?
I am experimenting with FreeBSD to be prepared when my new i-Buddie 4
arrives. (Specs at http://desknote.biz/sub/spec-i-buddie4.htm). I wonder
whether anybody has any experience with this new 'desknote' computer.
I specifically would like support for the Synaptics touch pad, but did
not find much in the FreeBSD documentation, nor in the ports collection.
So I went to see at http://www.synaptics.com/support/downloads.cfm and
found a pointer to a linux 'tpconfig' touch pad driver available at
http://compass.com/synaptics/ which has not yet been ported to FreeBSD.
So I tried to use this on my little FreeBSD testbox:
~/tpconfig-3.1.3 # ./configure
loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for fcntl.h... (cached) yes
checking for unistd.h... (cached) yes
updating cache ./config.cache
creating ./config.status
creating Makefile
~/tpconfig-3.1.3 # ./make
"Makefile", line 254: Need an operator
make: fatal errors encountered -- cannot continue
~/tpconfig-3.1.3 #
I used vim to add line numbers in the Makefile and copypasted the result:
1 # Generated automatically from Makefile.in by configure.
2 # Makefile.in generated automatically by automake 1.4 from Makefile.am
3
4 # Copyright (C) 1994, 1995-8, 1999 Free Software Foundation, Inc.
5 # This Makefile.in is free software; the Free Software Foundation
6 # gives unlimited permission to copy and/or distribute it,
7 # with or without modifications, as long as this notice is preserved.
8
9 # This program is distributed in the hope that it will be useful,
10 # but WITHOUT ANY WARRANTY, to the extent permitted by law; without
11 # even the implied warranty of MERCHANTABILITY or FITNESS FOR A
12 # PARTICULAR PURPOSE.
13
14 # Source: $Id: Makefile.am,v 1.2 2000/11/05 21:50:25 cph Exp $
15
16
17 SHELL = /bin/sh
18
19 srcdir = .
20 top_srcdir = .
21 prefix = /usr/local
22 exec_prefix = ${prefix}
23
24 bindir = ${exec_prefix}/bin
25 sbindir = ${exec_prefix}/sbin
26 libexecdir = ${exec_prefix}/libexec
27 datadir = ${prefix}/share
28 sysconfdir = ${prefix}/etc
29 sharedstatedir = ${prefix}/com
30 localstatedir = ${prefix}/var
31 libdir = ${exec_prefix}/lib
32 infodir = ${prefix}/info
33 mandir = ${prefix}/man
34 includedir = ${prefix}/include
35 oldincludedir = /usr/include
36
37 DESTDIR =
38
39 pkgdatadir = $(datadir)/tpconfig
40 pkglibdir = $(libdir)/tpconfig
41 pkgincludedir = $(includedir)/tpconfig
42
43 top_builddir = .
44
45 ACLOCAL = aclocal
46 AUTOCONF = autoconf
47 AUTOMAKE = automake
48 AUTOHEADER = autoheader
49
50 INSTALL = /usr/bin/install -c
51 INSTALL_PROGRAM = ${INSTALL} $(AM_INSTALL_PROGRAM_FLAGS)
52 INSTALL_DATA = ${INSTALL} -m 644
53 INSTALL_SCRIPT = ${INSTALL_PROGRAM}
54 transform = s,x,x,
55
56 NORMAL_INSTALL = :
57 PRE_INSTALL = :
58 POST_INSTALL = :
59 NORMAL_UNINSTALL = :
60 PRE_UNINSTALL = :
61 POST_UNINSTALL = :
62 CC = gcc
63 MAKEINFO = makeinfo
64 PACKAGE = tpconfig
65 VERSION = 3.1.3
66
67 AUTOMAKE_OPTIONS = "VERSION=1.2"
68 bin_PROGRAMS = tpconfig
69 tpconfig_SOURCES = tpconfig.c synaptics.c ALPS.c utils.c
70 MAINTAINERCLEANFILES = Makefile.in configure aclocal.m4
install-sh
missing mkinstalldirs COPYING INSTALL
71
72 # don't know why this is being omitted...
73 EXTRA_DIST = configure
74 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
75 mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
76 CONFIG_CLEAN_FILES =
77 PROGRAMS = $(bin_PROGRAMS)
78
79
80 DEFS = -DPACKAGE=\"tpconfig\" -DVERSION=\"3.1.3\" -DHAVE_FCNTL_H=1
-DHAVE_UNISTD_H=1 -I. -I$(srcdir)
81 CPPFLAGS =
82 LDFLAGS =
83 LIBS =
84 tpconfig_OBJECTS = tpconfig.o synaptics.o ALPS.o utils.o
85 tpconfig_LDADD = $(LDADD)
86 tpconfig_DEPENDENCIES =
87 tpconfig_LDFLAGS =
88 CFLAGS = -g -O2
89 COMPILE = $(CC) $(DEFS) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS)
$(AM_CFLAGS) $(CFLAGS)
90 CCLD = $(CC)
91 LINK = $(CCLD) $(AM_CF
hostname for a dhcpclient
My cable operator provides me with a dhcp service. I successfully configured my interface and got a valid IP address. However, do I really have to specify the cable operator's domain or can I put my own vanhoecke.org domain and a fixed node name, e.g, freebilly? My ISP provides me with a kabel.telenet.be domain name and a temporary node name Dxyz12ad. The latter is ugly and not fixed, and as such not worthy to identify my brand new machine. The interface configuration tool does allow freebilly.vanhoecke.org, but I am afraid this will complicate things somewhere down the line. The tool rewrites my /etc/hosts without any mention of the lovely freebilly node name (I presume it could have been generated as alias, but maybe it doesn't like its nickname): 127.0.0.1 localhost.vanhoecke.org localhost I am afraid that I need to tell the system somewhere that freebilly really is an alias for localhost. I will surely need this when I will configure nfs access from a couple of windoze workstations to freebilly. These machines are interconnected thru a small hub and used to find each other over the 'NWLink IPX/SPX/NetBIOS Compatible Transport Protocol'. I still have to figure out how I will integrate freebilly in this little network, but at the very leats, it will need a name of its own, I presume. Where and how do I permanently register freebilly's name without upsetting anything so that this is known by all applications inside freebilly (and possibly such that my windoze machines detect it it their 'neighborhood')? TIA, Guido. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
