No colours at all with ncurses and urxvt on FreeBSD 9.0-RC2

2011-11-25 Thread Moritz Wilhelmy
Hello,

I can't get colours to work with urxvt (the normal urxvt, that is, not
the 256-color one) over ssh. Google doesn't come up with any usable
results for this particular case.. What bothers me is that a termcap
entry for rxvt-unicode is present on the termcap file FreeBSD came
with. I'm really clueless here, can someone give me a hint?

Best,

Moritz
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Quick build of stripped-down kernel

2011-11-25 Thread Alexander Best
On Fri Nov 25 11, Thomas Mueller wrote:
 from b. f. bf1...@googlemail.com:
 
  If you are going to build most of the modules, but only want to
  exclude a few, then add the directories of the modules to be excluded
  (relative to /usr/src/sys/modules) to WITHOUT_MODULES, for example in
  /etc/make.conf. If you are only going to build a few modules, and want
  to exclude the majority of the modules, then add the directories of
  the modules that are to be built to MODULES_OVERRIDE.  For no modules
  at all, set NO_MODULES.  See /usr/src/sys/modules/Makefile and
  /usr/src/sys/conf/kern.post.mk for details. You may also save some
  time by using one of your faster machines to build the OS for the
  slower machines.
 
 Suppose you want to build more than one kernel so as to be able to choose at 
 boot time.
 
 Then you might not want to build modules redundantly.  So how would you make 
 the modules from /boot/kernel accessible when booting /boot/kernel2?

irrc there was a patch posted on some of the mailinglists not a long time ago,
which added support for building only those modules, which aren't part of the
kernel. this might be a good alternative, if you want a small footprint, but
want to take advantage of all the freebsd kernel drivers/etc.

cheers.
alex

 
 Tom
 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: No colours at all with ncurses and urxvt on FreeBSD 9.0-RC2

2011-11-25 Thread Moritz Wilhelmy
On Fri, Nov 25, 2011 at 06:37:18 -0500, Thomas Dickey wrote:
 On Fri, Nov 25, 2011 at 11:59:01AM +0100, Moritz Wilhelmy wrote:
  I can't get colours to work with urxvt (the normal urxvt, that is, not
  the 256-color one) over ssh. Google doesn't come up with any usable
  results for this particular case.. What bothers me is that a termcap
  entry for rxvt-unicode is present on the termcap file FreeBSD came
  with. I'm really clueless here, can someone give me a hint?
 
 setting TERM to rxvt-256color looks like the way to fix that issue.

Indeed, setting TERM to either rxvt-256color or rxvt gives me
colours.  The remaining question is, why doesn't it work with
rxvt-unicode, which is also in the termcap file?

I'd prefer not working around the issue anymore by conditionally setting
TERM on all my FreeBSD boxes, but fixing it once and for all...

Nevertheless, thanks for your quick reply. Your help is appreciated :-)


Best regards,

Moritz
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: No colours at all with ncurses and urxvt on FreeBSD 9.0-RC2

2011-11-25 Thread Thomas Dickey
On Fri, Nov 25, 2011 at 11:59:01AM +0100, Moritz Wilhelmy wrote:
 Hello,
 
 I can't get colours to work with urxvt (the normal urxvt, that is, not
 the 256-color one) over ssh. Google doesn't come up with any usable
 results for this particular case.. What bothers me is that a termcap
 entry for rxvt-unicode is present on the termcap file FreeBSD came
 with. I'm really clueless here, can someone give me a hint?

setting TERM to rxvt-256color looks like the way to fix that issue.

-- 
Thomas E. Dickey dic...@invisible-island.net
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature


Re: No colours at all with ncurses and urxvt on FreeBSD 9.0-RC2

2011-11-25 Thread Thomas Dickey
On Fri, Nov 25, 2011 at 01:02:15PM +0100, Moritz Wilhelmy wrote:
 On Fri, Nov 25, 2011 at 06:37:18 -0500, Thomas Dickey wrote:
  On Fri, Nov 25, 2011 at 11:59:01AM +0100, Moritz Wilhelmy wrote:
   I can't get colours to work with urxvt (the normal urxvt, that is, not
   the 256-color one) over ssh. Google doesn't come up with any usable
   results for this particular case.. What bothers me is that a termcap
   entry for rxvt-unicode is present on the termcap file FreeBSD came
   with. I'm really clueless here, can someone give me a hint?
  
  setting TERM to rxvt-256color looks like the way to fix that issue.
 
 Indeed, setting TERM to either rxvt-256color or rxvt gives me
 colours.  The remaining question is, why doesn't it work with
 rxvt-unicode, which is also in the termcap file?

well... rxvt-unicode-256color was the effect of the checkins for termcap.src
for conf/152713 and conf/153164

The earlier one suggests that the naming came from rxvt-unicode's sources.
Checking that, it seems that the rxvt-unicode entry specifies 88 colors,
while the rxvt-unicode-256color entry (close to rxvt-256color) does 256.

However, the rxvt-unicode entry in FreeBSD was added for conf/117323,
which equated it to rxvt-mono (no color), with some changes for function-keys.

On the other hand, the rxvt entry uses color, which was overlooked in
conf/117323:

# Termcap entry for rxvt-unicode, taken from 
http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.html#I_need_a_termcap_file_entry
rxvt-unicode|rxvt-unicode terminal (X Window System):\
:SF=\E[%dS:SR=\E[%dT:bw:ec=\E[%dX:kb=\177:kd=\EOB:ke=\E[?1l\E:\
:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:lm#0:te=\E[r\E[?1049l:\
:ti=\E[?1049h:tc=rxvt-mono:

rxvt|rxvt terminal emulator (X Window System):\
:pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:tc=rxvt-mono:

Following the clue from the comment, the example using no color was present
in rxvt.7 until it was removed in version 9.05 of rxvt-unicode.  The current
documentation contains no examples (the termcap/terminfo are only separate
files).

-- 
Thomas E. Dickey dic...@invisible-island.net
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature


RE: Quick build of stripped-down kernel

2011-11-25 Thread Brett Glass

At 10:39 AM 11/24/2011, Terrence Koeman wrote:


Add

makeoptions NO_MODULES=yes

to your KERNCONF.


Thank you (and thanks also to the other folks who responded in 
private e-mail). It also has a second advantage: besides disabling 
generation of the .ko files, it also suppresses compilation of 
drivers that are not going to be linked statically into the kernel. 
Build on an older Pentium II server took about 10-12% of the time! 
Worth knowing about.


--Brett Glass

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Quick build of stripped-down kernel

2011-11-25 Thread b. f.
On 11/25/11, Thomas Mueller mueller6...@bellsouth.net wrote:
 from b. f. bf1...@googlemail.com:

 If you are going to build most of the modules, but only want to
 exclude a few, then add the directories of the modules to be excluded
 (relative to /usr/src/sys/modules) to WITHOUT_MODULES, for example in
 /etc/make.conf. If you are only going to build a few modules, and want
 to exclude the majority of the modules, then add the directories of
 the modules that are to be built to MODULES_OVERRIDE.  For no modules
 at all, set NO_MODULES.  See /usr/src/sys/modules/Makefile and
 /usr/src/sys/conf/kern.post.mk for details. You may also save some
 time by using one of your faster machines to build the OS for the
 slower machines.

 Suppose you want to build more than one kernel so as to be able to choose at
 boot time.

 Then you might not want to build modules redundantly.  So how would you make
 the modules from /boot/kernel accessible when booting /boot/kernel2?


If the kernel versions were compatible, and the set of modules were
the same, I suppose you could set MODULES_WITH_WORLD and
KODIR=/boot/modules during buildworld and installworld, to build the
modules as part of buildworld and install them in /boot/modules during
installworld, rather than in /boot/kernel or /boot/kernel2.  Then you
could build and install both of your kernels with NO_MODULES, as
previously discussed, and with your  different choices of KODIR for
each kernel.  Because /boot/modules is part of the default module_path
defined in /boot/defaults/loader.conf, the modules ought to load as
usual for either kernel.  If you wanted to place them in a different
directory, you could alter KODIR during buildworld and installworld,
and add the directory to module_path in /boot/loader.conf.  I haven't
tested this, but I think that it will work, and I'd be interested to
hear whether it does. There are of course alternative methods.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: options atapicam and/or device ATA_CAM in kernel config?

2011-11-25 Thread Lowell Gilbert
Thomas Mueller mueller6...@bellsouth.net writes:

 What is the role of options atapicam and device ATA_CAM in kernel config 
 file?

 Are they redundant?  Kernel will build with both these options, but will it 
 make things go awry?  Is ATA_CAM deprecated?

As far as I can see, ATA_CAM isn't currently documented.
Just ignore it.

 I am trying to burn a CD (or DVD) on a SATA DVD-RW drive, but cdrtools don't 
 work.

 Also, how do I build and install a kernel to some name other than 
 /boot/kernel, and not build all modules in duplicate?

 I might want to try kernels with some differences in options, but with the 
 same modules.

 NetBSD and Linux make it easy to choose a non-default name for the kernel, so 
 I can have multiple kernels and choose one at boot.

The usual way is to have a separate config file for each, although you
can come up with other ways if you feel like being clever.  The config
files support an include functionality, so working through the files is
pretty easy.

As for leaving out modules, there are a number of options documented for
make.conf(5) and src.conf(5) that give you various kinds of control.

 In Linux, beginning with kernels 2.6.*, cdrtools work without the ATA-SCSI 
 dance.

You don't say what version of FreeBSD you're on. I'm still using
RELENG_8, so I may be missing some choices for later versions, where I
understand that the CAM code has been significantly reworked.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Invalid fdisk partition table found

2011-11-25 Thread Lowell Gilbert
Robert travelin...@cox.net writes:

 Greetings

 [robert@dell64] ~ uname -a
 FreeBSD dell64.shasta204.local 8.2-STABLE FreeBSD 8.2-STABLE #34: Fri
 Nov 18 06:43:01 PST 2011
 root@dell64.shasta204.local:/usr/obj/usr/src/sys/GENERIC  amd64 

 I have two Lexar Professional 600X 16GB compact flash cards that are
 unusable. fdisk shows:

 [robert@dell64] ~ fdisk /dev/da1
 *** Working on device /dev/da1 ***
 parameters extracted from in-core disklabel are:
 cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)

 parameters to be used for BIOS calculations are:
 cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)

 fdisk: invalid fdisk partition table found
 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS bootblock is:
 The data for partition 1 is:
 sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
 start 32, size 59360 (28 Meg), flag 80 (active)
   beg: cyl 0/ head 1/ sector 1;
   end: cyl 28/ head 63/ sector 32
 The data for partition 2 is:
 UNUSED
 The data for partition 3 is:
 UNUSED
 The data for partition 4 is:
 UNUSED

 It shows only 28 MB instead of 16GB. I have tried to change the type
 from 165 (FreeBSD) to msdosfs types 6 11 or 12 using fdisk -u and fdisk
 -i and also sade. I do not get an error but when finished it still
 shows the same data. 

 I have tried to zero it out using  dd if=/dev/zero of=/dev/da1 bs=1m
 and nothing changes. I have tried different block sizes and counts to
 no avail.

If you zero it out and fdisk still sees a partition table, the write
probably didn't really happen. [Modulo some possible issues with the
kernel caching the disk parameters.] fdisk is sometimes a bit quiet
about its errors, but dd isn't...

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Invalid fdisk partition table found (fwd)

2011-11-25 Thread Robert
On Thu, 24 Nov 2011 13:45:37 -0700 (MST)
Warren Block wbl...@wonkity.com wrote:

 On Thu, 24 Nov 2011, Robert wrote:
 
  [robert@dell64] ~ sudo gpart destroy -F da1
  da1 destroyed
 
  [robert@dell64] ~ fdisk /dev/da1
  *** Working on device /dev/da1 ***
  parameters extracted from in-core disklabel are:
  cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)
 
  parameters to be used for BIOS calculations are:
  cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)
 
  fdisk: invalid fdisk partition table found
 
 The partition table was cleared.
 
  Media sector size is 512
  Warning: BIOS sector numbering starts with sector 1
  Information from DOS bootblock is:
  The data for partition 1 is:
  sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
 start 32, size 59360 (28 Meg), flag 80 (active)
  beg: cyl 0/ head 1/ sector 1;
  end: cyl 28/ head 63/ sector 32
 
 And it starts with a default table equal to the size of the drive.

Is it supposed to still show sysid 165 ?

I was under the impression that dd if=/dev/zero would clean out
everything including sector 1.

 
  I see the flashing lights like it is writing to the CF card but
  nothing changes.
 
  More suggestions welcome. These are quite expensive CF cards.
 
 The dd/fdisk and gpart results show the same problem, so it likely
 isn't in the partitioning.
 
 Do both cards report the same size?

Yes..sort of 28, 29 MB

 
 I found recently that there is some oddness with certain Sandisk
 flash memory that made it non-responsive to anything.  FreeBSD
 couldn't do a thing with it.  Before throwing it away, I tried it on
 a Windows Vista system... which recognized and formatted it without a
 complaint.  Now it works on everything.  Special vendor-specific code
 in Windows?

XP Pro shows and error that the disk cannot be formatted. I tried it in
the wifes Windows 7 and it shows no drive attached.

 
 Another option would be to attempt formatting the cards with a camera.

I'll have to ask the camera owner if she tried that.

OT. The last 2 times that I have sent replies to two list regarding this
question, I have not seen it come through to me. Julian's relies as
well as yours come through.

Robert
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: No colours at all with ncurses and urxvt on FreeBSD 9.0-RC2

2011-11-25 Thread Moritz Wilhelmy
On Fri, Nov 25, 2011 at 08:19:15 -0500, Thomas Dickey wrote:
 well... rxvt-unicode-256color was the effect of the checkins for termcap.src
 for conf/152713 and conf/153164
 
 The earlier one suggests that the naming came from rxvt-unicode's sources.
 Checking that, it seems that the rxvt-unicode entry specifies 88 colors,
 while the rxvt-unicode-256color entry (close to rxvt-256color) does 256.
 
 However, the rxvt-unicode entry in FreeBSD was added for conf/117323,
 which equated it to rxvt-mono (no color), with some changes for function-keys.
 
 On the other hand, the rxvt entry uses color, which was overlooked in
 conf/117323:
 
 # Termcap entry for rxvt-unicode, taken from 
 http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.html#I_need_a_termcap_file_entry
 rxvt-unicode|rxvt-unicode terminal (X Window System):\
   :SF=\E[%dS:SR=\E[%dT:bw:ec=\E[%dX:kb=\177:kd=\EOB:ke=\E[?1l\E:\
   :kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:lm#0:te=\E[r\E[?1049l:\
   :ti=\E[?1049h:tc=rxvt-mono:

And I already wondered why it was so short..

 rxvt|rxvt terminal emulator (X Window System):\
   :pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:tc=rxvt-mono:
 
 Following the clue from the comment, the example using no color was present
 in rxvt.7 until it was removed in version 9.05 of rxvt-unicode.  The current
 documentation contains no examples (the termcap/terminfo are only separate
 files).

This sounds like a bug in FreeBSD's default termcap. Should I file a PR?

Moritz
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


buildkernel not honoring WITH_MODULES from make.conf ? (was: Re: Quick build of stripped-down kernel)

2011-11-25 Thread Damien Fleuriot
On 11/24/11 4:17 PM, b. f. wrote:
 
 If you are going to build most of the modules, but only want to
 exclude a few, then add the directories of the modules to be excluded
 (relative to /usr/src/sys/modules) to WITHOUT_MODULES, for example in
 /etc/make.conf. If you are only going to build a few modules, and want
 to exclude the majority of the modules, then add the directories of
 the modules that are to be built to MODULES_OVERRIDE.  For no modules
 at all, set NO_MODULES.  See /usr/src/sys/modules/Makefile and
 /usr/src/sys/conf/kern.post.mk for details. You may also save some
 time by using one of your faster machines to build the OS for the
 slower machines.
 
 b.


Hijacking this thread to report what might or might not be a problem on
my part.


On a 8.2-RELEASE box, I have set the following in /etc/make.conf:
KERNCONF=MULTI
WITH_MODULES=geom_label if_lagg linprocfs linsysfs linux mfi_linux


I have then run, from /usr/src :
make buildkernel
make installkernel

I notice, at the end of installkernel:
[snip]
=== xl (install)
install -o root -g wheel -m 555   if_xl.ko /boot/kernel
install -o root -g wheel -m 555   if_xl.ko.symbols /boot/kernel
=== zfs (install)
install -o root -g wheel -m 555   zfs.ko /boot/kernel
install -o root -g wheel -m 555   zfs.ko.symbols /boot/kernel



Why does it build and install these modules (and a whole lot of other
ones) although they're not part of my WITH_MODULES list ?


kldstat reports:
Id Refs AddressSize Name
 1   21 0x8010 999620   kernel
 21 0x80a9a000 bc10 geom_label.ko
 31 0x80aa6000 1358 mfi_linux.ko
 44 0x80aa8000 42558linux.ko
 51 0x80c22000 3ee0 linprocfs.ko
 61 0x80c26000 a11  linsysfs.ko
 71 0x80c27000 4f2c if_lagg.ko


My issue here is that I totally don't need if_xl for example and would
really love for it to be neither built nor installed.

Have I misunderstood WITH_MODULES' use ?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: No colours at all with ncurses and urxvt on FreeBSD 9.0-RC2

2011-11-25 Thread Thomas Dickey
On Fri, Nov 25, 2011 at 06:58:21PM +0100, Moritz Wilhelmy wrote:
 On Fri, Nov 25, 2011 at 08:19:15 -0500, Thomas Dickey wrote:
  well... rxvt-unicode-256color was the effect of the checkins for termcap.src
  for conf/152713 and conf/153164
  
  The earlier one suggests that the naming came from rxvt-unicode's sources.
  Checking that, it seems that the rxvt-unicode entry specifies 88 colors,
  while the rxvt-unicode-256color entry (close to rxvt-256color) does 256.
  
  However, the rxvt-unicode entry in FreeBSD was added for conf/117323,
  which equated it to rxvt-mono (no color), with some changes for 
  function-keys.
  
  On the other hand, the rxvt entry uses color, which was overlooked in
  conf/117323:
  
  # Termcap entry for rxvt-unicode, taken from 
  http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.html#I_need_a_termcap_file_entry
  rxvt-unicode|rxvt-unicode terminal (X Window System):\
  :SF=\E[%dS:SR=\E[%dT:bw:ec=\E[%dX:kb=\177:kd=\EOB:ke=\E[?1l\E:\
  :kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:lm#0:te=\E[r\E[?1049l:\
  :ti=\E[?1049h:tc=rxvt-mono:
 
 And I already wondered why it was so short..

It's short because most of the content is in rxvt-mono (that tc= acts
as an include).
 
  rxvt|rxvt terminal emulator (X Window System):\
  :pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:tc=rxvt-mono:

this also is short - the main difference between the two is that the
latter has features for color (pa, Co, AF, AB and op).

  Following the clue from the comment, the example using no color was present
  in rxvt.7 until it was removed in version 9.05 of rxvt-unicode.  The current
  documentation contains no examples (the termcap/terminfo are only separate
  files).
 
 This sounds like a bug in FreeBSD's default termcap. Should I file a PR?

yes - 

-- 
Thomas E. Dickey dic...@invisible-island.net
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature


RE: buildkernel not honoring WITH_MODULES from make.conf ? (was: Re: Quick build of stripped-down kernel)

2011-11-25 Thread Terrence Koeman
On Fri, 25 Nov 2011 at 19:27:54, Damien Fleuriot wrote:

 On 11/24/11 4:17 PM, b. f. wrote:
 
 If you are going to build most of the modules, but only want to exclude
 a few, then add the directories of the modules to be excluded (relative
 to /usr/src/sys/modules) to WITHOUT_MODULES, for example in
 /etc/make.conf. If you are only going to build a few modules, and want
 to exclude the majority of the modules, then add the directories of the
 modules that are to be built to MODULES_OVERRIDE.  For no modules at
 all, set NO_MODULES.  See /usr/src/sys/modules/Makefile and
 /usr/src/sys/conf/kern.post.mk for details. You may also save some time
 by using one of your faster machines to build the OS for the slower
 machines.
 
 b.

 Have I misunderstood WITH_MODULES' use ?

The answer is in the post you quoted: use MODULES_OVERRIDE.

-- 
Regards,
T. Koeman, MTh/BSc/BPsy; Technical Monk

MediaMonks B.V. (www.mediamonks.com)
Please quote relevant replies in correspondence.




smime.p7s
Description: S/MIME cryptographic signature


Re: Invalid fdisk partition table found (fwd)

2011-11-25 Thread Warren Block

On Fri, 25 Nov 2011, Robert wrote:


On Thu, 24 Nov 2011 13:45:37 -0700 (MST)
Warren Block wbl...@wonkity.com wrote:


On Thu, 24 Nov 2011, Robert wrote:


[robert@dell64] ~ sudo gpart destroy -F da1
da1 destroyed

[robert@dell64] ~ fdisk /dev/da1
*** Working on device /dev/da1 ***
parameters extracted from in-core disklabel are:
cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)

fdisk: invalid fdisk partition table found


The partition table was cleared.


Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
   start 32, size 59360 (28 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 28/ head 63/ sector 32


And it starts with a default table equal to the size of the drive.


Is it supposed to still show sysid 165 ?

I was under the impression that dd if=/dev/zero would clean out
everything including sector 1.


The partition table was cleared, that's why it said invalid fdisk 
partition table found.  Rather than starting with an invalid table, it 
created a valid default table in memory.



Do both cards report the same size?


Yes..sort of 28, 29 MB


If they weren't the same, I was going to suggest maybe they've been 
heavily used and worn out.  But I don't know if capacity shrinks as 
blocks go bad and spares are used up, or if they just quit working. 
And I'd expect them to be very different unless they had the exact same 
usage, like in a mirror.



OT. The last 2 times that I have sent replies to two list regarding this
question, I have not seen it come through to me. Julian's relies as
well as yours come through.


Maybe spam or duplicate filtering.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


What might be causing this during during buildworld in 7.4-STABLE ?

2011-11-25 Thread Jukka A. Ukkonen

I keep persistently getting this for no obvious reason...

=== gnu/usr.bin/texinfo/makeinfo (installincludes)
=== gnu/usr.bin/texinfo/info (installincludes)
=== gnu/usr.bin/texinfo/infokey (installincludes)
=== gnu/usr.bin/texinfo/install-info (installincludes)
=== gnu/usr.bin/texinfo/texindex (installincludes)
=== gnu/usr.bin/texinfo/doc (installincludes)
1 error
*** Error code 2
1 error
*** Error code 2
1 error
Exit 2

And before anyone asks...  Yes, it has been against the latest daily
patches (csup), and it is still repeating after several days now.

The uname -a line for the system is ...

FreeBSD mjolnir 7.4-STABLE FreeBSD 7.4-STABLE #0: Sun Nov 13 18:30:46 EET 2011 
r...@mjolnir.thunderbolt.fi:/usr/obj/usr/src/sys/Mjolnir i386

Any ideas would be welcome.


Cheers,
// jau
.---  ..-  -.-  -.-  .-.-  .-.-.-..-  -.-  -.-  ---  -.  .  -.
  /Jukka A. Ukkonen, Oxit Ltd, Finland
 /__   M.Sc. (sw-eng  cs)(Phone) +358-500-606-671
   /   Internet: Jukka.Ukkonen(a)Oxit.Fi
  /Internet: jau(a)iki.fi
 v
.---  .-  ..-  ...-.-  ..  -.-  ..  .-.-.-  ..-.  ..
+ + + + My opinions are mine and mine alone, not my employers. + + + +
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org