Re: [gentoo-user] Boot situation
On 12.09, Colleen Beamer wrote: Block dev sda3 is not a valid root device The root block device is unspecified or not detected. Does it say anything beyond that? I'd expect it to continue with: Please specify a device to boot, or shell for a shell.. boot() :: The previous error message as well as this prompt are output by the init script in your initrd, created by genkernel. At the boot() :: prompt you should be able to enter shell as a value, in order to enter a shell. Could you try this, then do an ls on the /dev directory to verify what devices have been created at this stage? Maybe you have an sdb in addition to the sda, or maybe it's called hda? (The former could happen if you have an external USB drive plugged in, the latter if you've configured the wrong driver for your disk controller). Of course, there's also the possiblity that you don't see any obvious disk devices at this stage. If that's the case, you haven't configured your kernel with any device drivers that can handle your drive, and need to have another look at the kernel config. Also, while running the livecd, if you know which device is the root device as found by the livecd, you could label it, then use the label when naming the root device instead of the device name. Labels are more stable than device names... To label a file system on a device if you're using ext2/ext3, use the command e2label -L label device, eg: e2label -L ROOT /dev/sda3 You should then change grub.conf to read: real_root=LABEL=ROOT instead of real_root=/dev/sda3 And last, specify LABEL=ROOT for root device in /etc/fstab on the root device as well: LABEL=ROOT / ext2 defaults 0 1 ... or something like that. -- Jo. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] bind zone.file won't load
On 04.03, Harry Putnam wrote: db.192.168.1 8 snip = $TTL 1D @ IN SOA reader.local.lan. reader.reader.local.lan. ( 200405190 ; serial 28800 ; refresh (8 hours) 14400 ; retry (4 hours) 2419200; expire (4 weeks) 86400 ; minimum (1 day) ) ; ; Name servers (The name '@' is implied) ; IN NS reader ; ; Addresses point to canonical names ; 192.168.1.2 IN PTRrdmz.local.lan. 192.168.1.1 IN PTRfwdmz.local.lan. == 8 snip === I just went through this myself, having a few false tries before getting it right. From this experience, here's my understanding of how zone files work: - The general syntax for lines in the zone files: key ttl class type value - You may leave out one or more of these fields, which means they inherit the value that field had in the previous line. - You may use parenthesis to break long entries into several lines. This is mostly done for the SOA line, but should worlk for other lines as well. - The ';' character means the rest of the line is a comment. - You may use the special value '@' to mean the origin, which initially is the value from the 'zone' entry in the named.conf file, with a '.' appended. An $ORIGIN entry redefines the origin for subsequent entries in the file. You may put in several $ORIGIN entries. - A $TTL entry sets the default value of the 'ttl' field from that line on. - Where names are used -- eg. the 'key' field of an 'IN A' entry, or the 'value' field of an 'IN PTR' entry -- you may specify the full name by ending it with a '.'. Names with no '.' at the end have the origin appended. Now, if you look at your 'IN NS' line (which specifies the authorative name server for your reverse domain), it translates into: key ttl class type value 1.168.192.in-addr.arpa. 1DIN NS reader.1.168.192.in-addr.arpa. Which is not what you want. Instead, try the following line: IN NS reader.local.lan. In addition, 'reader' should have an 'IN A' entry in the 'local.lan' zone file. The 'dig' command from 'bind-tools' comes in handy when debugging bind setups. Some handy commands: dig reader.local.lan dig local.lan any dig local.lan axfr dig -x 192.168.1 axfr dig -x 192.168.1 any Given like this, 'dig' contacts the name servers from '/etc/resolv.conf'. You may also append '@name-server-name' to a 'dig' command in order to specify directly which name server to contact. -- Jo. pgpTGVXZAYd7r.pgp Description: PGP signature
Re: [gentoo-user] Re: bind zone.file won't load
On 05.03, Harry Putnam wrote:
Following Alexanders example I tried to redefine $ORIGIN near the top
since as you point out `@' contains whatever is in named.conf to start.
$TTL 1D
$ORIGIN 0.168.192.IN-ADDR.ARPA. ;; RESET ORIGIN HERE SO THAT
;;THE SOA line won't be rejected for being `out of zone'
@ IN SOA reader.local.lan. reader.reader.local.lan. (
200405190 ; serial
28800 ; refresh (8 hours)
14400 ; retry (4 hours)
2419200; expire (4 weeks)
86400 ; minimum (1 day)
)
;
; Name servers (The name '@' is implied)
;;; $ORIGIN shoud still hold here RIGHT?
INNSreader.local.lan. ;; CORRECTED no uses Canonical form
$ORIGIN 1.168.192.IN-ADDR.ARPA. ;; RESET to handle 192.168.1
;
; Addresses point to canonical names
;
2 INPTR rdmz.local.lan.
1 INPTR fwdmz.local.lan.
Hmm. I guess you could try to define the zone 168.192.in-addr.arpa instead.
Then you'd have this in named.conf:
zone 168.192.in-addr.arpa IN { type master; file pri/168.192.zone;
notify no; };
And in pri/168.192.zone:
@ IN SOA reader.local.lan. reader.reader.local.lan. (
200405190 ; serial
28800 ; refresh (8 hours)
14400 ; retry (4 hours)
2419200; expire (4 weeks)
86400 ; minimum (1 day)
)
IN NS reader.local.lan.
1.0 IN PTR fwdmz.local.lan.
2.0 IN PTR rdmz.local.lan.
1.1 IN PTR a.local.lan. ; whatever: some host name in 192.168.1.0/24
2.1 IN PTR b.local.lan. ; whatever: some host name in 192.168.1.0/24
$TTL 1D
$ORIGIN 0.168.192.IN-ADDR.ARPA.
lan.local.IN-ADDR.ARPA.IN SOA reader.local.lan. reader.reader.local.lan.
(
This is definitely wrong:
- the 'IN SOA' entry should have the origin as key
- it doesn't make any sense to use anything but reverse IP network addresses off
the in-addr.arpa domain
It should not be necessary to set the $ORIGIN to the same value you defined in
the named.conf file.
If you try to put two zones inside one file, as you do in your reverse zone,
in addition to redefining $ORIGIN, you need to put in an additional 'IN SOA'
entry. I believe the missing 'IN SOA' for your second reverse zone is the
reason bind complains about 'no owner'.
And again: it's really no reason why you can't put all of this into one zone
instead.
--
Jo.
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] bind zone.file won't load
On 04.03, Harry Putnam wrote: $TTL 1D @ IN SOAreader.local.lan. hostmaster ( 200405191 ; serial 8H; refresh 4H; retry 4W; expire 1D ) ; minimum ;; Nameserver (The name '@' is implied) IN NS reader ;; smtp hub (The name '@' is implied) IN MX10 reader ;; addresses for the canonical names localhost IN A 127.0.0.1 ansil IN A 192.168.0.21 bjpIN A 192.168.0.16 fw IN A 192.168.0.20 fwobsd IN A 192.168.0.19 IN A 192.168.1.1 harvey IN A 192.168.0.22 mob2 IN A 192.168.0.3 reader IN A 192.168.0.4 IN A 192.168.1.2 wapIN A 192.168.0.50 ;; aliases smtp IN CNAME reader wwwIN CNAME reader ticIN CNAME reader ;; interface specific addresses fwdmz IN A 192.168.1.1 rdmz IN A 192.168.1.2 Just a few additional comments on this: Your entries for 'reader' and 'fwobsd' are probably not what you really want. By defining several 'IN A' entries for the same host name, you effectively get bind to serve these addresses in 'round robin' fashion whenever a client looks up that name. Another way to look at this is that you don't name hosts in DNS, you name IP addresses. If a host has several IP addresses, eg. because it has several NIC's, you should give a separate name to each IP address. In your case, you could do something like this: reader IN A 192.168.0.4 reader0 IN A 192.168.0.4 reader1 IN A 192.168.1.2 or reader0 IN A 192.168.0.4 reader1 IN A 192.168.1.2 reader IN CNAME reader0 Note that you may define as many names for an IP address as you like. A case where you'd definitely want to do this, is with the name for the name server host itself. Put in something like this: ns IN A 192.168.0.4 Then you may use 'ns.local.lan.' in all your 'IN SOA' entries instead of the name for the actual host. Then you only need to change one entry in case you want to change to another name server host. Also, note that this has to be an 'IN A' entrym not an 'IN CNAME' entry, as the name in the SOA has to be an 'IN A' entry. -- Jo. pgpWctwjUd1k4.pgp Description: PGP signature
Re: [gentoo-user] dual nic cards
On 12.02, Dan Sheffner wrote: I'm trying to setup dual nics on my server but I seem to be doing something wrong. Below is my /etc/conf.d/net file. As you can see my public address pointing to the web is 70.88.74.105 and the local one is 10.1.10.5. As soon as I enamble eth1 eth0 won't ping out from another box. It may be something simple but I don't know what I'm doing wrong. Please help. This blank configuration will automatically use DHCP for any net.* # scripts in /etc/init.d. To create a more complete configuration, # please review /etc/conf.d/net.example and save your configuration # in /etc/conf.d/net (this file :]!). config_eth0=( 70.88.74.105 netmask 255.255.255.0 broadcast 70.255.255.255) config_eth1=( 10.1.10.5 netmask 255.255.255.0 broadcast 10.1.10.255) # Here's how todo routing if you need it - the below sets the default gateway routes_eth0=( default via 70.88.74.110 ) Your eth0 broadcast address is obviously wrong, it should be 70.88.74.255 according to the netmask you've specified. How did you come up with these values? Were they given to you from your ISP? Anyway, by using the following, alternative (and shorter) syntax you're more likely to set the different parameters correctly: config_eth0=( 70.88.74.105/24) config_eth1=( 10.1.10.5/24) Also, but possibly depending on what you're going to use this box for, you need to at leat: - enable ip forwarding in /etc/sysctl.conf - activate iptables or something like it to protect the Internet facing interface from unwanted attention Have a look at the following guide, if you didn't already: http://www.gentoo.org/doc/en/home-router-howto.xml -- Jo. pgpbO03WFZ66d.pgp Description: PGP signature
