Re: a new hard-drive in a 2y/o laptop

[Ian Smith]

On Sun, 2 Jan 2011 01:15:35 -0500, Chris Brennan wrote:
 > On Sat, Jan 1, 2011 at 10:20 PM, Ian Smith  wrote:
[..]
 > >  The bsdlabel lives in sector 1 (counting from 0) of the slice concerned,
 > > specifically the first 0x114 (276d) bytes, in the second sector of the
 > > boot blocks.  As noted above, in unsliced disks such as memstick.img
 > > that's sector 1 of the entire disk, but in ordinary sliced disks it's in
 > > sector 1 of the _slice_, so if you'd used (here using Chris' ad4)
 > >
 > >  dd if=/dev/zero of=/dev/ad4s1 oseek=1 bs=512 count=1
 > >
 > >
 > I would happily run this, but ad4s1 doesn't exist, and hasn't (that I know
 > of), I did do oseek=0 and oseek=1 on /dev/ad4 tho and that didn't change
 > anything, it still says it can't find /dev/ad4s1b (swap obviously)

On /dev/ad4, oseek=0 zeroes sector 0, the MBR including DOS partition 
(FreeBSD slice) table, so that would kill all the slice data, so sure, 
ad4s1 won't exist.  oseek=1 just zeroes an unused sector as we've seen.

What you _can_ do from that state is:

 dd if=/dev/zero of=/dev/ad4 oseek=63 count=8

which will remove the first 4K of (what will be) slice 1, in case 
there's a misconfigured bsdlabel there, for later.  I'm not convinced 
this is likely your problem, but it can't hurt before slice 1 exists (by 
virtue of having an entry in the MBR, when it should show up in /dev)

 > > At 6.x (and 7.x, I think) it could have been 'dangerously dedicated' ie
 > > unsliced .. which option has been removed in 8.x _except_ regarding the
 > > memstick.img (appearing as /dev/daXa) .. not half confusing, eh?
 > >
 > >
 > I actually noticed this today, I had issues writing 8.2BETA1 to a 2GB
 > MicroSD card, so I used a 2.5" external hard-drive and from the fixit prompt
 > I noticed that it wrote a 1gb partition for the BETA1 image and left the
 > rest of the desk untouched (ann 59gb of it).

Do you mean you dd'd the memstick.img to the external USB drive?  And 
that booted ok?  And sysinstall found it ok, as /dev/ad0a?  Details!

 > >  sysctl kern.geom.debugflags=16
 > >  dd if=/dev/zero of=/dev/ad4s1 bs=512 count=8
 > >
 > > will remove slice 1's boot blocks entirely, including the bsdlabel.

Given you've shown previously that s1 starts at sector 63, so will:

 sysctl kern.geom.debugflags=16
 dd if=/dev/zero of=/dev/ad4 oseek=63 count=8

 > > [excuse broken threading, but unless cc'd I have to reply to the digest]
 > 
 > I've been trying to keep you in my replies

Getting yours fine; that was re my reply to Mike's message.

 > but your down-under, so I don't get your replies till after 1am my 
 > time... Anywho, it's late and I need to be up in 8hrs, hopefully this 

Yeah North America is so yesterday from here (well, 16 hours for you :)

 > can be figured out ... I would hate for the disk to be defective in 
 > some way.

Of course that's not impossible, but you did say you'd installed some 
linux on it ok?  Clutching at straws, is there anything in your BIOS 
regarding different SATA modes you can play with? (No SATA disks here)

Something else you could try is W)riting the slice table + MBR out from 
the fdisk menu, then quit sysinstall and reboot.  You can do the same 
after labelling but before newfs'ing .. not generally recommended, but 
safe enough on a blank disk.

If you do the latter, you'll have to reenter your mount points later, so 
make a note of the order and size of partitions that you specified.

Hopefully somebody else has a take on all this, I'm out of ideas ..

cheers, Ian
___
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: a new hard-drive in a 2y/o laptop

[Michael Powell]

Ian Smith wrote:

> In freebsd-questions Digest, Vol 343, Issue 10, Message: 23
> On Fri, 31 Dec 2010 19:37:10 -0500 Michael Powell 
> wrote:
[snip]
>  > >  > 
>  > >  > > Try zeroing out the mbr:
>  > >  > >
>  > >  > > Boot a LiveFS CD, then at a root prompt do:
>  > >  > >
>  > >  > > sysctl kern.geom.debugflags=16  and:
>  > >  > >
>  > >  > > dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1
>  > >  > >
>  > >  > > where x equals your drive number. This will zero out any old
>  > >  > > MBR.
>  > > 
>  > > Er, no, Mike.  The MBR is in sector 0 of the disk; that would zero
>  > > out
>  > > sector 1 as oseek=1 skips over sector 0.  What's in sector 1 depends
>  > > on
>  > > how/whether the disk is sliced.  In a 'dangerously dedicated'
>  > > (unsliced) disk like a memory stick perhaps, this would usually be
>  > > /boot/boot1 and
>  > > include the bsdlabel.  In a sliced disk, sectors 1 to 62 are
>  > > typically unused, the first slice usually starting at sector 63.
>  > > 
>  > > t23% fdisk -s ad0
>  > > /dev/ad0: 232581 cyl 16 hd 63 sec
>  > > PartStartSize Type Flags
>  > >1:  63 8385867 0x0b 0x00
>  > >2: 8385930   125821080 0xa5 0x80
>  > >3:   13420701033543342 0xa5 0x00
>  > >4:   16775073066685815 0xa5 0x00
>  > > 
>  > > If you really want to zero out sector 0, leave out the oseek (or use
>  > > oseek=0) - but you're better off using 'fdisk -Bi' to init a new
>  > > disk.
>  > > 
>  > 
>  > Yes - true enough. Was thinking partition table and typed 'mbr'.
> 
> Well, what's commonly called 'the partition table' is bytes 0x1be-1ff of
> the MBR, so I was confused by your writing to sector 1 rather than 0,
> but have a new theory to test, seeing Chris isn't making any progress;
> this maybe a victim of the old 'slice vs partition' terminology issue.
[snip]
> 
> The bsdlabel lives in sector 1 (counting from 0) of the slice concerned,
> specifically the first 0x114 (276d) bytes, in the second sector of the
> boot blocks.  As noted above, in unsliced disks such as memstick.img
> that's sector 1 of the entire disk, but in ordinary sliced disks it's in
> sector 1 of the _slice_, so if you'd used (here using Chris' ad4)
> 
>  dd if=/dev/zero of=/dev/ad4s1 oseek=1 bs=512 count=1
> 
> - rather than of=/dev/ad4 - then you would indeed be zeroing out the
> label, ie the 'partition table' in FreeBSD-speak.  Is that perhaps what
> you had to do to that 6.2 disk, which I suppose was a sliced disk?

No. I used the of=/dev/ad4 as described above. However, I think you've hit 
the nail on the head on one aspect. I believe that 6.2 disk was originally 
set up as "dangerously dedicated". It was so long ago and I had forgotten 
all about it, but this does dovetail with what your are getting at.

The machine that disk went into had been upgraded completely through the 7.x 
series and on to 8.0-Release before it's disk went up in smoke(literally). I 
was attempting to do a fresh 'minimal' install of 8.0-Release to the old 6.2 
disk pulled off a shelf prior to doing restore(s) of a dump from just the 
day before. It was only done because it could be done immediately, and a 
newer, larger, better replacement procured after the fact.

Exact copy of error from my notes here:

"Unable to find device node for /dev/ad4s1b in /dev! The creation of 
filesystems will be aborted." Then pressing "OK" brings this: "Couldn't make 
filesystems properly. Aborting."

This from sysinstall and occurs after fdisk, labeling, at the point when  
sysinstall then tries to write out the config to the disk and newfs.

 
> At 6.x (and 7.x, I think) it could have been 'dangerously dedicated' ie
> unsliced .. which option has been removed in 8.x _except_ regarding the
> memstick.img (appearing as /dev/daXa) .. not half confusing, eh?
> 
> In any case, it'd be a cheap trick for Chris to try from Fixit, and
> though it seems unlikely there'd be anything 'leftover' from an earlier
> install, maybe earlier failure/s have left a broken bsdlabel there?

Or any other form of 'garbage'. I'd use the 8.1 LiveFS CD myself just as a 
personal preference - but either approach should do the job.
 
> So at this still-uninstalled stage it couldn't hurt to zero that sector,
> or even the first 4KB of ad4s1 .. which is /boot/boot1 plus /boot/boot2
> (which equals /boot/boot !) before the label section gets written.  ie:
> 
>  sysctl kern.geom.debugflags=16
>  dd if=/dev/zero of=/dev/ad4s1 bs=512 count=8
> 
> will remove slice 1's boot blocks entirely, including the bsdlabel.
> 

Yes - I agree. Would also be nice to examine it afterward with a hex editor 
to actually see *if* all writes were zero.  Any 'ones' sprinkled in there, 
especially in the region of the disk we are talking about would indicate 
corruption. And my wild guess if this is the situation it may possibly 
indicate some form of subtle hardware incompatibility most likely a clash of 
firmwares, e.g. controller and disk(s).  Some form of non-st

Re: a new hard-drive in a 2y/o laptop

[Chris Brennan]

On Sat, Jan 1, 2011 at 10:20 PM, Ian Smith  wrote:

> Well, what's commonly called 'the partition table' is bytes 0x1be-1ff of
> the MBR, so I was confused by your writing to sector 1 rather than 0,
> but have a new theory to test, seeing Chris isn't making any progress;
> this maybe a victim of the old 'slice vs partition' terminology issue.
>
>
I think I was able to figure this part out, his meaning at least.


>  The bsdlabel lives in sector 1 (counting from 0) of the slice concerned,
> specifically the first 0x114 (276d) bytes, in the second sector of the
> boot blocks.  As noted above, in unsliced disks such as memstick.img
> that's sector 1 of the entire disk, but in ordinary sliced disks it's in
> sector 1 of the _slice_, so if you'd used (here using Chris' ad4)
>
>  dd if=/dev/zero of=/dev/ad4s1 oseek=1 bs=512 count=1
>
>
I would happily run this, but ad4s1 doesn't exist, and hasn't (that I know
of), I did do oseek=0 and oseek=1 on /dev/ad4 tho and that didn't change
anything, it still says it can't find /dev/ad4s1b (swap obviously)


> - rather than of=/dev/ad4 - then you would indeed be zeroing out the
> label, ie the 'partition table' in FreeBSD-speak.  Is that perhaps what
> you had to do to that 6.2 disk, which I suppose was a sliced disk?
>
> At 6.x (and 7.x, I think) it could have been 'dangerously dedicated' ie
> unsliced .. which option has been removed in 8.x _except_ regarding the
> memstick.img (appearing as /dev/daXa) .. not half confusing, eh?
>
>
I actually noticed this today, I had issues writing 8.2BETA1 to a 2GB
MicroSD card, so I used a 2.5" external hard-drive and from the fixit prompt
I noticed that it wrote a 1gb partition for the BETA1 image and left the
rest of the desk untouched (ann 59gb of it).


> In any case, it'd be a cheap trick for Chris to try from Fixit, and
> though it seems unlikely there'd be anything 'leftover' from an earlier
> install, maybe earlier failure/s have left a broken bsdlabel there?
>
> So at this still-uninstalled stage it couldn't hurt to zero that sector,
> or even the first 4KB of ad4s1 .. which is /boot/boot1 plus /boot/boot2
> (which equals /boot/boot !) before the label section gets written.  ie:
>
>  sysctl kern.geom.debugflags=16
>  dd if=/dev/zero of=/dev/ad4s1 bs=512 count=8
>
> will remove slice 1's boot blocks entirely, including the bsdlabel.
>
> cheers, Ian
>
> [excuse broken threading, but unless cc'd I have to reply to the digest]
>

I've been trying to keep you in my replies but your down-under, so I don't
get your replies till after 1am my time... Anywho, it's late and I need to
be up in 8hrs, hopefully this can be figured out ... I would hate for the
disk to be defective in some way.
___
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: HP 2010i 1600x900 screen sizing issue - PCBSD 8.1

[Warren Block]

On Sat, 1 Jan 2011, Michael D. Norwick wrote:

Okay, closer.  Thank You.  I commented out the HorizSync and VertRefresh 
lines restarted the X session and the screen appeared to fill more but I 
still had a black bar to the left at 1600x900.  Going to Computer -> System 
Settings -> Computer Administration - Display -> Size and Orientation, I 
found it at;


Size  1600x900
Refresh  Auto

Changed it to

Size  1280x1024
Refresh  Auto

Still no full screen width.  In fact it got narrower.

Changed it to

Size 1440x900  (which had not been an option previously)
The screen appeared to resize to the full width of the display and 'Refresh' 
now shows 59.9 Hz.


The monitor really is 1600x900, so it's still not quite right.  Your 
/var/log/Xorg.0.log may tell why it's not showing correctly.  It sounds 
like maybe a monitor adjustment.  If there's an "Auto" button on the 
monitor, set xorg.conf to 1600x900 (see below) and try that button.


I won't be pushing any buttons until I understand the effect.  I understand 
why HorizSync and VertRefresh settings would not be necessary for an LCD 
display but the xserver obviously knows what it's connected to.


Millions of years ago, when stupid CRTs roamed the earth, a wrong 
setting could physically damage the monitor.  Different refresh rates 
were used for different resolutions, with 75 Hz or higher needed to 
avoid flickering (in the US, anyway).


So the HorizSync and VertRefresh entries were there to specify the 
limits of what a given monitor could do, and protect it from incorrect, 
potentially damaging settings.


Today's monitors are smart.  The video card has a serial link to them 
through the VGA cable so the monitor can be queried for resolutions and 
refresh rates.  Even simpler, most LCDs use 60 Hz for a refresh rate, 
regardless of resolution.


This can get more complicated when you talk to xorg through a 
third-party window manager utility.  It's easiest to get xorg.conf set 
correctly by directly editing xorg.conf.


'Xorg -configure' generates an xorg.conf that is... well, not optimal 
for today's systems.  Whether that's due to apathy, inertia, or aversion 
due to so many old systems still being around, who knows.


Here's what I'd use for your entire Screen section:

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
SubSection "Display"
Modes "1600x900"
Virtual 1600 900
EndSubSection
EndSection

___
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: a new hard-drive in a 2y/o laptop

[Chris Brennan]

On Sat, Jan 1, 2011 at 11:25 AM, Chris Brennan  wrote:

> I have a 2GB MicroSD card that I am going to toss 8.2BETA1 on, hopefully
> later today and see where that gets me.
>

2GB MicroSD card was a bust, use a 60GB hard-drive and wrote the image to
that, it booted it just fine, but the install failed w/ the exact same
error. Could this be the new drive? *shudder* Defective in some way?
___
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: a new hard-drive in a 2y/o laptop

[Ian Smith]

In freebsd-questions Digest, Vol 343, Issue 10, Message: 23
On Fri, 31 Dec 2010 19:37:10 -0500 Michael Powell  
wrote:
 > Ian Smith wrote:
 > 
 > > In freebsd-questions Digest, Vol 343, Issue 5, Message: 10
 > > On Tue, 28 Dec 2010 11:02:45 -0500 Chris Brennan 
 > > wrote:
 > >  > On Tue, Dec 28, 2010 at 2:23 AM, Michael Powell
 > >  > wrote:
 > >  > 
 > >  > > Try zeroing out the mbr:
 > >  > >
 > >  > > Boot a LiveFS CD, then at a root prompt do:
 > >  > >
 > >  > > sysctl kern.geom.debugflags=16  and:
 > >  > >
 > >  > > dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1
 > >  > >
 > >  > > where x equals your drive number. This will zero out any old MBR.
 > > 
 > > Er, no, Mike.  The MBR is in sector 0 of the disk; that would zero out
 > > sector 1 as oseek=1 skips over sector 0.  What's in sector 1 depends on
 > > how/whether the disk is sliced.  In a 'dangerously dedicated' (unsliced)
 > > disk like a memory stick perhaps, this would usually be /boot/boot1 and
 > > include the bsdlabel.  In a sliced disk, sectors 1 to 62 are typically
 > > unused, the first slice usually starting at sector 63.
 > > 
 > > t23% fdisk -s ad0
 > > /dev/ad0: 232581 cyl 16 hd 63 sec
 > > PartStartSize Type Flags
 > >1:  63 8385867 0x0b 0x00
 > >2: 8385930   125821080 0xa5 0x80
 > >3:   13420701033543342 0xa5 0x00
 > >4:   16775073066685815 0xa5 0x00
 > > 
 > > If you really want to zero out sector 0, leave out the oseek (or use
 > > oseek=0) - but you're better off using 'fdisk -Bi' to init a new disk.
 > > 
 > 
 > Yes - true enough. Was thinking partition table and typed 'mbr'. 

Well, what's commonly called 'the partition table' is bytes 0x1be-1ff of 
the MBR, so I was confused by your writing to sector 1 rather than 0, 
but have a new theory to test, seeing Chris isn't making any progress; 
this maybe a victim of the old 'slice vs partition' terminology issue.

 > In my case, a temporary replacement disk had FreeBSD 6.2 on it. Something 
 > changed wrt to disklabeling on the way to 8-Release and the old 6.2 being 
 > present created a situation where that region on the disk was invisible to 
 > the new labeling and wouldn't write out. A new install of 8-Release 
 > (sysinstall) would error out with the same message as Chris when it came to 
 > the point of writing out to the disk. For me, the above 2 commands fixed my 
 > situation. Even though his error is the same, I think his problem may be  
 > different from mine.

The bsdlabel lives in sector 1 (counting from 0) of the slice concerned, 
specifically the first 0x114 (276d) bytes, in the second sector of the 
boot blocks.  As noted above, in unsliced disks such as memstick.img 
that's sector 1 of the entire disk, but in ordinary sliced disks it's in 
sector 1 of the _slice_, so if you'd used (here using Chris' ad4)

 dd if=/dev/zero of=/dev/ad4s1 oseek=1 bs=512 count=1

- rather than of=/dev/ad4 - then you would indeed be zeroing out the 
label, ie the 'partition table' in FreeBSD-speak.  Is that perhaps what 
you had to do to that 6.2 disk, which I suppose was a sliced disk?

At 6.x (and 7.x, I think) it could have been 'dangerously dedicated' ie 
unsliced .. which option has been removed in 8.x _except_ regarding the 
memstick.img (appearing as /dev/daXa) .. not half confusing, eh?

In any case, it'd be a cheap trick for Chris to try from Fixit, and 
though it seems unlikely there'd be anything 'leftover' from an earlier 
install, maybe earlier failure/s have left a broken bsdlabel there?

So at this still-uninstalled stage it couldn't hurt to zero that sector, 
or even the first 4KB of ad4s1 .. which is /boot/boot1 plus /boot/boot2 
(which equals /boot/boot !) before the label section gets written.  ie:

 sysctl kern.geom.debugflags=16
 dd if=/dev/zero of=/dev/ad4s1 bs=512 count=8

will remove slice 1's boot blocks entirely, including the bsdlabel.

cheers, Ian

[excuse broken threading, but unless cc'd I have to reply to the digest]
___
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: broken link in libgeom(3) manpage

[perryh]

Adam Vande More  wrote:
> > On Sat, Jan 1, 2011 at 3:57 PM,  wrote:
> >> The SEE ALSO section of libgeom(3) in 8.1-RELEASE is a link:
> >>
> >>  http://ezine.daemonnews.org/200308/blueprints.html
> >>
> >> That link brings up the daemonnews.org homepage, not the intended
> >> article ...
> >> Does anyone know where the article can be found?
>
> Ah, here is a pdf of it.  Unsure on any copyright problems though.
>
> http://gwdu111.gwdg.de/misc/dnews/dnews_0305.pdf

Thanks for the pointer.  (Actually it is .../dnews_0308.pdf
that contains the particular article mentioned in libgeom(3);
dnews_0305.pdf contains an earlier article, also by phk@, in
the same series, and there was a third in .../dnews_0406.)

One _hopes_ that publicly-accessible archives like that have been
vetted for copyright concerns.
___
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: broken link in libgeom(3) manpage

[perryh]

Alexander Best  wrote:
> On Sat Jan  1 11, per...@pluto.rain.com wrote:
> > The SEE ALSO section of libgeom(3) in 8.1-RELEASE is a link:
> > 
> >   http://ezine.daemonnews.org/200308/blueprints.html
> > 
> > That link brings up the daemonnews.org homepage, not the intended
> > article ...
>
> this was already fixed by r216177 ...

Which, unfortunately, seems to have removed the link rather than
updating it.

Cc'ing the article's author, in case he knows a current location
that could be used.  (It may not be advisable to link to the daemon
news archive on gwdu111.gwdg.de, since its copyright status is not
entirely clear* and it provides whole issues rather than individual
articles.)

> but not yet MFC'ed to stable/8.  so it looks like 8.2 will also
> ship with this defective reference.

--

* at least, not entirely clear to me, the site being mostly in
  German.  Someone who can read German might find something about
  the copyright status of the daemon news archive elsewhere on
  the site.
___
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: HP 2010i 1600x900 screen sizing issue - PCBSD 8.1

[Michael D. Norwick]

On 01/01/2011 12:51, Polytropon wrote:

On Sat, 01 Jan 2011 12:34:39 -0600, "Michael D. 
Norwick"  wrote:
   

And, where are those commented out option lines
in my xorg.conf documented?
 

In the obvious place: "man xorg.conf". :-)



   

From 'man xorg.conf'"VIDEOADAPTOR SECTION
   Nobody wants to say how this works.  Maybe nobody knows ...".  
See also 'man radeon'

___
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: csup and build question

[Chip Camden]

Quoth per...@pluto.rain.com on Saturday, 01 January 2011:
> Bruce Cran  wrote:
> > On Sat, 1 Jan 2011 20:44:01 +0100
> > Polytropon  wrote:
> > > If programs or other components of the world do have to
> > > be in sync with kernel or system files (sys/*.h), then
> > > I conclude that world also has to be compiled. In this
> > > regards, it means a change of the kernel, and if the
> > > kernel did change, kernel and world are out of sync,
> > > which implies that both have to be compiled.
> > The ABI of the kernel sometimes changes, in which case despite
> > there being no changes in world it still needs to be rebuilt
> > against the newer header files. For example, recently:
> >
> > 20101228:
> > The TCP stack has been modified to allow Khelp modules to
> > interact with it via helper hook points and store per-connection
> > data in the TCP control block. Bump __FreeBSD_version to 900029.
> > User space tools that rely on the size of struct tcpcb in tcp_var.h
> > (e.g. sockstat) need to be recompiled.
> 
> IIUC, things like that are supposed to happen only within -CURRENT,
> not within a -STABLE or security branch.
> 
> I would surmise that, if a csup yielded changes only in /usr/src/sys
> and none of those changes touched a .h file, it should not be necessary
> to rebuild world.

OK, that's about what I had thought.

Thanks to all three of you for responding.  Obviously, the safe choice is
to always rebuild world if anything changes.  But if I see that only a
couple of .c files in the kernel have been touched, then rebuilding only
kernel should be OK in stable -- I think.  The only possible gotcha would be if
something in the kernel gets compiled to a library that world uses, or if
something in world includes a .c file from kernel for some reason.

-- 
Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F
http://camdensoftware.com | http://chipstips.com| http://chipsquips.com


pgpB8TraeNGoR.pgp
Description: PGP signature

Re: broken link in libgeom(3) manpage

[Adam Vande More]

On Sat, Jan 1, 2011 at 4:15 PM, Adam Vande More wrote:

> On Sat, Jan 1, 2011 at 3:57 PM,  wrote:
>
>> The SEE ALSO section of libgeom(3) in 8.1-RELEASE is a link:
>>
>>  http://ezine.daemonnews.org/200308/blueprints.html
>>
>> That link brings up the daemonnews.org homepage, not the intended
>> article.  A search for geom on that page retrieves 53 articles,
>> none of which seem even vaguely related.
>>
>> Does anyone know where the article can be found?
>>
>
> This the closest I can find.
>
> http://web.archive.org/web/20030820203226/ezine.daemonnews.org/200308/
>
> so maybe phk@ would be able to help further.
>
>
Ah, here is a pdf of it.  Unsure on any copyright problems though.

http://gwdu111.gwdg.de/misc/dnews/dnews_0305.pdf

-- 
Adam Vande More
___
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: broken link in libgeom(3) manpage

[Adam Vande More]

On Sat, Jan 1, 2011 at 3:57 PM,  wrote:

> The SEE ALSO section of libgeom(3) in 8.1-RELEASE is a link:
>
>  http://ezine.daemonnews.org/200308/blueprints.html
>
> That link brings up the daemonnews.org homepage, not the intended
> article.  A search for geom on that page retrieves 53 articles,
> none of which seem even vaguely related.
>
> Does anyone know where the article can be found?
>

This the closest I can find.

http://web.archive.org/web/20030820203226/ezine.daemonnews.org/200308/

so maybe phk@ would be able to help further.

-- 
Adam Vande More
___
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: broken link in libgeom(3) manpage

[Alexander Best]

On Sat Jan  1 11, per...@pluto.rain.com wrote:
> The SEE ALSO section of libgeom(3) in 8.1-RELEASE is a link:
> 
>   http://ezine.daemonnews.org/200308/blueprints.html
> 
> That link brings up the daemonnews.org homepage, not the intended
> article.  A search for geom on that page retrieves 53 articles,
> none of which seem even vaguely related.
> 
> Does anyone know where the article can be found?

this was already fixed by r216177, but not yet MFC'ed to stable/8. so it looks
like 8.2 will also ship with this defective reference.

cheers.
alex

-- 
a13x
___
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"

broken link in libgeom(3) manpage

[perryh]

The SEE ALSO section of libgeom(3) in 8.1-RELEASE is a link:

  http://ezine.daemonnews.org/200308/blueprints.html

That link brings up the daemonnews.org homepage, not the intended
article.  A search for geom on that page retrieves 53 articles,
none of which seem even vaguely related.

Does anyone know where the article can be found?
___
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: csup and build question

[perryh]

Bruce Cran  wrote:
> On Sat, 1 Jan 2011 20:44:01 +0100
> Polytropon  wrote:
> > If programs or other components of the world do have to
> > be in sync with kernel or system files (sys/*.h), then
> > I conclude that world also has to be compiled. In this
> > regards, it means a change of the kernel, and if the
> > kernel did change, kernel and world are out of sync,
> > which implies that both have to be compiled.
> The ABI of the kernel sometimes changes, in which case despite
> there being no changes in world it still needs to be rebuilt
> against the newer header files. For example, recently:
>
> 20101228:
>   The TCP stack has been modified to allow Khelp modules to
> interact with it via helper hook points and store per-connection
> data in the TCP control block. Bump __FreeBSD_version to 900029.
> User space tools that rely on the size of struct tcpcb in tcp_var.h
> (e.g. sockstat) need to be recompiled.

IIUC, things like that are supposed to happen only within -CURRENT,
not within a -STABLE or security branch.

I would surmise that, if a csup yielded changes only in /usr/src/sys
and none of those changes touched a .h file, it should not be necessary
to rebuild world.
___
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: cshrc to bashrc??

[Gary Kline]

On Sat, Jan 01, 2011 at 11:01:31AM +0100, Polytropon wrote:
> On Fri, 31 Dec 2010 13:15:45 -0800, Gary Kline  wrote:
> > Anybody know if there is a utility that transforms the /root/.cshrc
> > into a bash RC file?After decades, I'm giving up on the csh stuff.
> > Need something simpler.
> 
> As far as I know, there is no automatic converter for csh -> sh
> config files. Basically, the C shell has these:
>   - system-wide:
> /etc/csh.cshrc, /etc/csh.login, /etc/csh.lougout
>   - per user:
> ~/.cshrc, ~/.login, ~/.logout
> I'm a csh user for most dialog use, because bash's interactive
> abilites force too much interaction (especially regarding
> completition) in the default configuration. But I'm more and
> more thinking to switch to bash permanently, as soon as I've
> beaten bash's misbehaviour out of its source code. :-)

I didn't/don't know much about bash--other that it seems to be 
everywhere.  Last night I spent several hours using my own hack
that translater the csh aliases to bashrc-type aliases.  Finally
threw in the towel.  

> 
> The system's sh uses /etc/profile and .profile in the same
> manner. Then there is bash, which I think uses the following
> files according to "man bash", section FILES:
> 
>   /etc/profile
>   The systemwide initialization file,
>   executed for login shells
>   ~/.bash_profile
>   The personal initialization file,
>   executed for login shells
>   ~/.bashrc
>   The individual per-interactive-shell startup file
>   ~/.bash_logout
>   The individual login shell cleanup file,
>   executed when a login shell exits
>   ~/.inputrc
>   Individual readline initialization file


The last one, .inputrc, is a noop to my brain.  And yes, I just
had my second cup of coffee!  IS there any cheatsheet URL that
'splains the readline init'z'n stuff?

> 
> You have to know about the different syntax definition for
> both file types, but it's relatively easy.
> 
> setenv ENVNAME envstring  -> ENVNAME="envstring"; export ENVNAME
>   -> export ENVNAME="envstring"
> 
> set VARNAME = 'varstring' -> VARNAME="varstring"
> 
> alias aliname 'alistring' -> alias aliname="alistring"


Looks at lot like my zsh usage. 



> 
> All the config files allow regular sh coding sequences (such
> as the use of conditionals or iterators).
> 
> To get a standard prompt in bash, use this:
> 
>   export PS1="\...@\h:\w\$ "
> 
> It is the equivalent to csh's
> 
>   set promptchars = "%#"
>   set prompt = "%...@%m:%~%# "
> 
> Note that csh does automatically use % or # according to the
> first setting. I'm not sure how bash handles this.
> 

I have always ripped off somebody's prompt and then modified it
to what fits my needs.  Last night I kept running into problems 
with the PATH and the aliases.  Each re-edit I did I figured it
would be just-another-minute before bash worked.  Nope, nada,
zip.  Finally got smart and :quit.

-gary


> 
> -- 
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...

-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.97a release of Jottings: http://jottings.thought.org

___
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: ZFS

[ill...@gmail.com]

On 1 January 2011 13:08, Gabor Illo  wrote:
> Spam?
>
> 2010/12/6 
>
>> Dear Sir/Madam,
>>
>> Your email was unable reach the intended person that you were sending it
>> to.
>> For more information on our business please click on the following link:
>> Click here for our website 
>> We look forward to your continued business in the future.
>>
>> Regards,
>> Webmaster
>>

Da.  They keep trying on certain threads.  One
or two a month, for me.

-- 
--
___
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: ZFS

[Modulok]

Probably. I think I've got like 10 of these on and off.

-Modulok-

On 1/1/11, Gabor Illo  wrote:
> Spam?
>
> 2010/12/6 
>
>> Dear Sir/Madam,
>>
>> Your email was unable reach the intended person that you were sending it
>> to.
>> For more information on our business please click on the following link:
>> Click here for our website 
>> We look forward to your continued business in the future.
>>
>> Regards,
>> Webmaster
>>
> ___
> 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"
>
___
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: csup and build question

[Bruce Cran]

On Sat, 1 Jan 2011 20:44:01 +0100
Polytropon  wrote:

> If programs or other components of the world do have to
> be in sync with kernel or system files (sys/*.h), then
> I conclude that world also has to be compiled. In this
> regards, it means a change of the kernel, and if the
> kernel did change, kernel and world are out of sync,
> which implies that both have to be compiled.

The ABI of the kernel sometimes changes, in which case despite there
being no changes in world it still needs to be rebuilt against the
newer header files. For example, recently:

20101228:
The TCP stack has been modified to allow Khelp modules to
interact with it via helper hook points and store per-connection data
in the TCP control block. Bump __FreeBSD_version to 900029. User space
tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
sockstat) need to be recompiled.


-- 
Bruce Cran
___
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: csup and build question

[Polytropon]

On Sat, 1 Jan 2011 11:23:11 -0800, Chip Camden  
wrote:
> Quoth Polytropon on Saturday, 01 January 2011:
> > On Sat, 1 Jan 2011 10:38:22 -0800, Chip Camden 
> >  wrote:
> > > At the risk of confirming my reputation for asking stupid questions:
> > > 
> > > If a csup only pulls files in /usr/src/sys, is it safe to assume that the
> > > only rebuilding steps required are to rebuild and install the kernel?  Or
> > > is it possible that world could require a rebuild to take advantage of
> > > some of those kernel changes?
> > 
> > Kernel and world should ALWAYS be in sync, this means you
> > should update the full /usr/src tree, not just its sys/
> > subtree, as other files, located at a higher level, may
> > be important (such as /usr/src/Makefile).
> > 
> 
> That wasn't my question.  I always do a full csup, but sometimes it only
> pulls files in /usr/src/sys (because those are the only ones that have
> changed since my last csup/build).  In that case, is a buildworld
> required?

If programs or other components of the world do have to
be in sync with kernel or system files (sys/*.h), then
I conclude that world also has to be compiled. In this
regards, it means a change of the kernel, and if the
kernel did change, kernel and world are out of sync,
which implies that both have to be compiled.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: csup and build question

[Chip Camden]

Quoth Polytropon on Saturday, 01 January 2011:
> On Sat, 1 Jan 2011 10:38:22 -0800, Chip Camden  
> wrote:
> > At the risk of confirming my reputation for asking stupid questions:
> > 
> > If a csup only pulls files in /usr/src/sys, is it safe to assume that the
> > only rebuilding steps required are to rebuild and install the kernel?  Or
> > is it possible that world could require a rebuild to take advantage of
> > some of those kernel changes?
> 
> Kernel and world should ALWAYS be in sync, this means you
> should update the full /usr/src tree, not just its sys/
> subtree, as other files, located at a higher level, may
> be important (such as /usr/src/Makefile).
> 

That wasn't my question.  I always do a full csup, but sometimes it only
pulls files in /usr/src/sys (because those are the only ones that have
changed since my last csup/build).  In that case, is a buildworld
required?

-- 
Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F
http://camdensoftware.com | http://chipstips.com| http://chipsquips.com


pgptW6PkqTnf8.pgp
Description: PGP signature

Re: csup and build question

[Polytropon]

On Sat, 1 Jan 2011 10:38:22 -0800, Chip Camden  
wrote:
> At the risk of confirming my reputation for asking stupid questions:
> 
> If a csup only pulls files in /usr/src/sys, is it safe to assume that the
> only rebuilding steps required are to rebuild and install the kernel?  Or
> is it possible that world could require a rebuild to take advantage of
> some of those kernel changes?

Kernel and world should ALWAYS be in sync, this means you
should update the full /usr/src tree, not just its sys/
subtree, as other files, located at a higher level, may
be important (such as /usr/src/Makefile).




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: HP 2010i 1600x900 screen sizing issue - PCBSD 8.1

[Polytropon]

On Sat, 01 Jan 2011 12:34:39 -0600, "Michael D. Norwick" 
 wrote:
> And, where are those commented out option lines 
> in my xorg.conf documented?

In the obvious place: "man xorg.conf". :-)



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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"

csup and build question

[Chip Camden]

At the risk of confirming my reputation for asking stupid questions:

If a csup only pulls files in /usr/src/sys, is it safe to assume that the
only rebuilding steps required are to rebuild and install the kernel?  Or
is it possible that world could require a rebuild to take advantage of
some of those kernel changes?

-- 
Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F
http://camdensoftware.com | http://chipstips.com| http://chipsquips.com


pgp1ZTxhtqUVC.pgp
Description: PGP signature

Re: HP 2010i 1600x900 screen sizing issue - PCBSD 8.1

[Michael D. Norwick]

On 01/01/2011 10:25, Warren Block wrote:

On Fri, 31 Dec 2010, Michael D. Norwick wrote:


I bought



   Identifier   "Monitor0"
   VendorName   "HWP"
   ModelName"HP 2010"
   HorizSync24.0 - 83.0
   VertRefresh  50.0 - 76.0
   Option"DPMS"
EndSection


For a start, remove or comment out the HorizSync and VertRefresh lines.


Okay, closer.  Thank You.  I commented out the HorizSync and VertRefresh 
lines restarted the X session and the screen appeared to fill more but I 
still had a black bar to the left at 1600x900.  Going to Computer -> 
System Settings -> Computer Administration - Display -> Size and 
Orientation, I found it at;


Size  1600x900
Refresh  Auto

Changed it to

Size  1280x1024
Refresh  Auto

Still no full screen width.  In fact it got narrower.

Changed it to

Size 1440x900  (which had not been an option previously)
The screen appeared to resize to the full width of the display and 
'Refresh' now shows 59.9 Hz.


This is all quite non-intuitive.

I won't be pushing any buttons until I understand the effect.  I 
understand why HorizSync and VertRefresh settings would not be necessary 
for an LCD display but the xserver obviously knows what it's connected to.
Why does it set those?  And, where are those commented out option lines 
in my xorg.conf documented?


Thank You,

Michael

___
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: ZFS

[Gabor Illo]

Spam?

2010/12/6 

> Dear Sir/Madam,
>
> Your email was unable reach the intended person that you were sending it
> to.
> For more information on our business please click on the following link:
> Click here for our website 
> We look forward to your continued business in the future.
>
> Regards,
> Webmaster
>
___
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: cshrc to bashrc??

[Polytropon]

On Sat, 1 Jan 2011 10:56:24 -0500, Chris Brennan  wrote:
> >
> > > Note that csh does automatically use % or # according to the
> > > first setting. I'm not sure how bash handles this.
> >
> 
> man bash and search for PROMPTING, everything you can pass PS1 is there
> 
> # is \# the command number of this command
> 
> I don't see how a '%' is handled tho, what does it do is csh? I (or someone
> else) may know the bash equivalent...

The csh and bash config do use differnt "escape sequences"
for substitution, such as user name, host name, current
directory and "power" (root / non-root). In bash it is \,
in csh it is %.

You are right, "man bash" does list all the sequences,
as well as "man csh". For the standard prompt

u...@host:~/my/path% _

those are the corresponding codes:

Meaning csh bash
--  --  --
user%n  \u
host%m  \h
path\w  %~  (includes substitution ~)
prompt sign %#  (# for root, % for non-root)
\$  (# for root, $ for non-root)

That's why I said csh's set prompt = "%...@%m:%~%# " equals
bash's export PS1="\...@\h:\w\$ ", because bash does have a
different default prompt (which might not be desired).

A literal % can be used for bash's PS1 setting if intended.
But it's okay to see $ for bash, and % for csh.


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: a new hard-drive in a 2y/o laptop

[Chris Brennan]

>
> Yes - true enough. Was thinking partition table and typed 'mbr'.
>
>
It's all good, I got the cmd right in the end, but alas, it helped me not!


>  > Mmm .. it's not clear from Chris' original message exactly what he did.
>
>
I clarified that in a subsequent reply with considerably more detail :D


>  In my case, a temporary replacement disk had FreeBSD 6.2 on it. Something
> changed wrt to disklabeling on the way to 8-Release and the old 6.2 being
> present created a situation where that region on the disk was invisible to
> the new labeling and wouldn't write out. A new install of 8-Release
> (sysinstall) would error out with the same message as Chris when it came to
> the point of writing out to the disk. For me, the above 2 commands fixed my
> situation. Even though his error is the same, I think his problem may be
> different from mine.
>
> -Mike
>

I have a 2GB MicroSD card that I am going to toss 8.2BETA1 on, hopefully
later today and see where that gets me.
___
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: HP 2010i 1600x900 screen sizing issue - PCBSD 8.1

[Warren Block]

On Fri, 31 Dec 2010, Michael D. Norwick wrote:

I bought a new HP 2010i LCD monitor that is supposed to give me 1600x900 
resolution at 60 Hz to replace a generic 19" C.R.T. monitor that did 
1024x768.  The machine has an ATI Radeon video card and I am using a V.G.A. 
cable not H.D.M.I.  I reconfigured my /etc/xorg.conf using Xorg --configure. 
I was given the full screen at 1600x900 resolution at the next reboot but 
then while trying to adjust some monitor settings such as Power Saver and 
Sleep Timer the screen adjusted to the right and will not center.  Adjusting 
the horizontal control to '0' (full left?) will not center the display.

...

Section "Monitor"
   #DisplaySize  440   250# mm
   Identifier   "Monitor0"
   VendorName   "HWP"
   ModelName"HP 2010"
   HorizSync24.0 - 83.0
   VertRefresh  50.0 - 76.0
   Option"DPMS"
EndSection


For a start, remove or comment out the HorizSync and VertRefresh lines.
___
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: cshrc to bashrc??

[Chris Brennan]

>
> > Note that csh does automatically use % or # according to the
> > first setting. I'm not sure how bash handles this.
>

man bash and search for PROMPTING, everything you can pass PS1 is there

# is \# the command number of this command

I don't see how a '%' is handled tho, what does it do is csh? I (or someone
else) may know the bash equivalent...


C-
___
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: cshrc to bashrc??

[Gary Kline]

I've read about 30% of your email and just have to sack out. It
is just past 04:00 and my eyes are starting to glue shut.  And
hey, once them shut, I'll bang into stuff before I can get to my
bed!!

More coming tomooor-- Hm.  Since this *is* tomorrow,
then in around some N hours.

S'all, folks!

-g


On Sat, Jan 01, 2011 at 11:01:31AM +0100, Polytropon wrote:
> On Fri, 31 Dec 2010 13:15:45 -0800, Gary Kline  wrote:
> > Anybody know if there is a utility that transforms the /root/.cshrc
> > into a bash RC file?After decades, I'm giving up on the csh stuff.
> > Need something simpler.
> 
> As far as I know, there is no automatic converter for csh -> sh
> config files. Basically, the C shell has these:
>   - system-wide:
> /etc/csh.cshrc, /etc/csh.login, /etc/csh.lougout
>   - per user:
> ~/.cshrc, ~/.login, ~/.logout
> I'm a csh user for most dialog use, because bash's interactive
> abilites force too much interaction (especially regarding
> completition) in the default configuration. But I'm more and
> more thinking to switch to bash permanently, as soon as I've
> beaten bash's misbehaviour out of its source code. :-)
> 
> The system's sh uses /etc/profile and .profile in the same
> manner. Then there is bash, which I think uses the following
> files according to "man bash", section FILES:
> 
>   /etc/profile
>   The systemwide initialization file,
>   executed for login shells
>   ~/.bash_profile
>   The personal initialization file,
>   executed for login shells
>   ~/.bashrc
>   The individual per-interactive-shell startup file
>   ~/.bash_logout
>   The individual login shell cleanup file,
>   executed when a login shell exits
>   ~/.inputrc
>   Individual readline initialization file
> 
> You have to know about the different syntax definition for
> both file types, but it's relatively easy.
> 
> setenv ENVNAME envstring  -> ENVNAME="envstring"; export ENVNAME
>   -> export ENVNAME="envstring"
> 
> set VARNAME = 'varstring' -> VARNAME="varstring"
> 
> alias aliname 'alistring' -> alias aliname="alistring"
> 
> All the config files allow regular sh coding sequences (such
> as the use of conditionals or iterators).
> 
> To get a standard prompt in bash, use this:
> 
>   export PS1="\...@\h:\w\$ "
> 
> It is the equivalent to csh's
> 
>   set promptchars = "%#"
>   set prompt = "%...@%m:%~%# "
> 
> Note that csh does automatically use % or # according to the
> first setting. I'm not sure how bash handles this.
> 
> 
> 
> -- 
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...

-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.97a release of Jottings: http://jottings.thought.org

___
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: cshrc to bashrc??

[Polytropon]

On Fri, 31 Dec 2010 13:15:45 -0800, Gary Kline  wrote:
>   Anybody know if there is a utility that transforms the /root/.cshrc
>   into a bash RC file?After decades, I'm giving up on the csh stuff.
>   Need something simpler.

As far as I know, there is no automatic converter for csh -> sh
config files. Basically, the C shell has these:
- system-wide:
  /etc/csh.cshrc, /etc/csh.login, /etc/csh.lougout
- per user:
  ~/.cshrc, ~/.login, ~/.logout
I'm a csh user for most dialog use, because bash's interactive
abilites force too much interaction (especially regarding
completition) in the default configuration. But I'm more and
more thinking to switch to bash permanently, as soon as I've
beaten bash's misbehaviour out of its source code. :-)

The system's sh uses /etc/profile and .profile in the same
manner. Then there is bash, which I think uses the following
files according to "man bash", section FILES:

/etc/profile
The systemwide initialization file,
executed for login shells
~/.bash_profile
The personal initialization file,
executed for login shells
~/.bashrc
The individual per-interactive-shell startup file
~/.bash_logout
The individual login shell cleanup file,
executed when a login shell exits
~/.inputrc
Individual readline initialization file

You have to know about the different syntax definition for
both file types, but it's relatively easy.

setenv ENVNAME envstring-> ENVNAME="envstring"; export ENVNAME
-> export ENVNAME="envstring"

set VARNAME = 'varstring'   -> VARNAME="varstring"

alias aliname 'alistring'   -> alias aliname="alistring"

All the config files allow regular sh coding sequences (such
as the use of conditionals or iterators).

To get a standard prompt in bash, use this:

export PS1="\...@\h:\w\$ "

It is the equivalent to csh's

set promptchars = "%#"
set prompt = "%...@%m:%~%# "

Note that csh does automatically use % or # according to the
first setting. I'm not sure how bash handles this.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: make buildworld errors

[Manolis Kiagias]

On 01/01/2011 9:54 ?.?., Mike wrote:
>
> Trying to buildworld but it keeps failing. I finally deleted /usr/src
> and recopyed from a cd then cvsup using standard-supfile. Tried
> limiting how much ram freebsd uses and only using one stick of ram.
> All attempts have failed at the same place.  Would using the GENERIC
> kernel make a difference?
>

You shouldn't have any trouble building world using a custom kernel.
Try rm -rf /usr/obj/* before starting the build. This usually solves th
___
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"

make buildworld errors

[Mike]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Trying to buildworld but it keeps failing. I finally deleted /usr/src
and recopyed from a cd then cvsup using standard-supfile. Tried
limiting how much ram freebsd uses and only using one stick of ram.
All attempts have failed at the same place.  Would using the GENERIC
kernel make a difference?

#make worldclean && make cleandir

#make buildworld

===> usr.sbin/ifmcstat (all)
cc -O2 -pipe  -DINET6 -std=gnu99 -fstack-protector -Wsystem-headers
- -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c
/usr/src/usr.sbin/ifmcstat/ifmcstat.c
cc1: warnings being treated as errors
/usr/src/usr.bin/ifmcstat/ifmcstat.c:170: warning: 'in6_ifinfo' used
but never defined
*** Error code 1

Stop in /usr/src/usr.sbin/ifmcstat.
*** Error code 1

#uname -a
FreeBSD frogger 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #0: Sat Nov 27
02:47:28 CST 2010 alert@:/usr/obj/usr/src/sys/MOLLY  i386
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJNHt2iAAoJEHKqVYG3x59oGG0QAKkUiME+ETJ2vHoIR15vq5FW
VIHMtaT9fFv4L9diNkZn/HnB5lWnRQ5O5DxSexn0iv7wDJzU68tArNJHgG1LvzuA
61rcsUEMIpNUJViYlEtzonVibQEoipehTgdjpNuMOcBqqi2tc8U9kN2xKB/pU+sI
yds2hNxxId3sSLBRIUwu+bsQqW6xc0LI2nsSZGArY4NxMyYUe5MLl+TUp8uhJNt4
nixJxuOi7eZ6+0MxJd79v1GkWjqVYZGddsiM0GG/5YuC6JUrTAiql3Oa6zsnqDQT
8BZjB3yrHctl77x0FpH2BfuVzlDeA1km1FWxLQIv2ewEHuPiEx0EUbe5oraXYhlb
ZlDtNs62MGoRsNl18ZzCxyIYJLDyLy6wsNOGmeuJNDgFxo7HyY+dycQAbmG13tju
uGHj4sz1PPsEOzPX5EAt9q0RgkbO715e9y1iFSmfbrD5dCLZM7OlxiUpjK9wLxqC
boVzIvD4GRFykR8vm0XAMHA3fc8O/LK7YYSDCxrOL79vtQPFm9IlnMzsZhk6QhfI
kEdX+uU8TLbzto8Pi0LvkSCC3nVgkW1yE5NPJa6XxoVXS1zGDaR2jZE5VnFx9NTP
wT6MrtEpbDTpix2IuM6JsGXrtsoB58osq+cyVONFn+yIO8w5YvhhfoPWh88GwPqa
UOIT+eKHUaexXkjkYmgQ
=+sXx
-END PGP SIGNATURE-

___
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"