from:"amarendra godbole"

On 21-Jun-2012, at 11:07 PM, cody chandler cody.a.chand...@gmail.com wrote:

 Hello,

  Talk about learning C Programming and the KR book being a good one.  Is
 this the book?

 http://www.amazon.com/C-Programming-Language-2nd-Edition/dp/0131103628

 Figured it would be best to start new instead of keeping the Chat forked
 and moving away from the topid of the OBSD Fork.


 Thanks
 Cody
 [...]

By now I am sure you have the answer, however let me tell you my experience:
while learning c I spent time on many books because kr was difficult for me
to follow. Other books seemed more friendly. This resulted in me picking up no
practical skills until I thought I'd give a try to kr.

KR is deliberately small to keep with the spirit of the C language, but the
authors don't mince words - they will teach you the same things and even more
in that small book, that might be taught by huge thick books in C.

An excellent companion to this book is the C FAQ, http://c-faq.com/ as well as
the C programming notes http://www.eskimo.com/~scs/cclass/krnotes/top.html The
later will help you comprehend kr in the initial stages of learning.

http://www.eskimo.com/~scs/readings/index2.html has a collection of excellent
posts on many areas of confusion in C, for eg. see the posts on precedence and
order of evaluation.

In a nutshell, I have found no better book than kr to learn the C language.

-ag

Re: Learning C Programming

On 22-Jun-2012, at 7:06 AM, Juan Francisco Cantero Hurtado i...@juanfra.info
wrote:

 On Thu, Jun 21, 2012 at 03:56:50PM -0400, Simon Perreault wrote:
 On 2012-06-21 15:21, Juan Francisco Cantero Hurtado wrote:
 Some good or bad comments about Deitel's C How to program?
 http://www.deitel.com/Books/C/CHowtoProgram7e/tabid/3635/Default.aspx

 The worst book on C programming I've ever read.

 No, scratch that.
 The worst book on programming I've ever read.

 No, it's worse.
 The worst book I've ever read. All categories.

 Thanks for the advice!

 I'll buy a cheap copy of KR that I've found a few hours ago. I've been
 wanting buy this book for years but I only found expensive copies.

 --
 Juan Francisco Cantero Hurtado http://juanfra.info
[...]

It is rather surprising since Prentice Hall of India have been selling this
book for Rs. 95 for the last 15 yrs or so, which is less than $2 US.

-ag

Re: Recommendation about books related with OS internals

On 22-Jun-2012, at 7:37 AM, Juan Francisco Cantero Hurtado i...@juanfra.info
wrote:

 These days I'm buying a few books related to programming and OSs. I
 don't want convert this mailing list on an books recomendation website,
 so let me take advantage of the last questions about books for one
 question more and we can kill this type of threads for a long time :)

 Can you recommend me a book about OS internals? I want a book about
 unix/bsd and focused more on the concepts and less on the code. Even
 better if the book contains info about OpenBSD.

 The comments on the webs of books stores are unrealistic because all the
 punctuations are 5/5 or 4/5 on this type of books. And webs like
 StackOverflow are uncritical with the books.

 Thanks.

 --
 Juan Francisco Cantero Hurtado http://juanfra.info


http://www.amazon.com/gp/aw/d/0201549794 design and implementation of the bsd
os, as well as the classic Maurice bach book.

-ag

Rescuing a messed-up disklabel -- scan_ffs, etc.

Hi All,

I am very pleased with the turn of events after I baked the disklabel
on my OBSD partition. A toast to all the hard work put in by OBSD
development team, and an offer for a free lunch/dinner/beer if you
happen to be in this part of India (Pune, closer to Mumbai/Bombay).
scan_ffs found all partitions, and I was successfully able to restore
everything. So this is what happened:

I was experimenting with boot loaders and finally settled on GRUB as
it allowed me to boot both Win XP and OBSD on my IBM ThinkPad X201. I
was booted into WinXP and was using whole disk encryption software.
Apparently, this encryption software marked the OBSD partition to be
encrypted as well (since it was visible through the Windows Volume
Manager as valid partition). Sure, it did not bother to check if
Windows filesystems were active, etc. To get out of that situation, I
deleted this partition from Windows, and GRUB conked with Error 22
(okay, should have thought that earlier -- but dumb moments happen).
Fortunately, all my data was backed up. I then booted into OBSD via
the boot CD, and cleared the partition table as well (second dumbest
moment). *poof* went away both operating systems.

Now I had a laptop with clean partition table, but both OS'es intact.
I wasn't worried to much since data was backed up, but was wary of
setting up OBSD again (including mail, etc.). So...

(1) I booted a live CD - MarBSD 5.1
(2) Ran scan_ffs on the drive as scan_ffs -l sd0. It found almost
all partitions, but was confused between /var and swap (so /var
appeared twice!). I mounted both, and found which one was /var
(interestingly, the other partition had exactly same content as /var,
except for one sasl2 directory, and difference in size).
(3) Redirected the output to a file, to be used in setting up the disklabel.
(4) Ran disklabel -e sd0, and added the output from scan_ffs, with
best guesses for partition names. [read scan_ffs and disklabel
manpages before this].
(5) Rebooted and checked if things were fine -- /bsd booted fine,
- However, later while mounting filesystems it stopped with
messages to the tune of cannot mount sd0k and sd0j, etc.)
- These were not a part of the disklabel interestingly(!)
(6) Rebooted via OBSD 5.1 into single user mode bsd -s
(7) Mounted / manually, and fixed /etc/fstab with correct partition names.
(8) Reboot, and success! Everything was as-is.

The output of scan_ffs can be seen in this image:
http://lh3.googleusercontent.com/-ln-xNFxx6WM/T-P6e4wgEMI/ApA/zygztOh6uR8/s720/scan_ffs.jpg

Thanks OBSD team again. Appreciate all your efforts, and the terrific
OS. Many lessons learnt as well! :-)

-Amarendra

Re: Rescuing a messed-up disklabel -- scan_ffs, etc.

Oh, and I also did re-install grub as a last step. Now remains the
task of getting back the Windows OS. :-)

-Amarendra

On Fri, Jun 22, 2012 at 10:26 AM, Amarendra Godbole
amarendra.godb...@gmail.com wrote:
 Hi All,

 I am very pleased with the turn of events after I baked the disklabel
 on my OBSD partition. A toast to all the hard work put in by OBSD
 development team, and an offer for a free lunch/dinner/beer if you
 happen to be in this part of India (Pune, closer to Mumbai/Bombay).
 scan_ffs found all partitions, and I was successfully able to restore
 everything. So this is what happened:

 I was experimenting with boot loaders and finally settled on GRUB as
 it allowed me to boot both Win XP and OBSD on my IBM ThinkPad X201. I
 was booted into WinXP and was using whole disk encryption software.
 Apparently, this encryption software marked the OBSD partition to be
 encrypted as well (since it was visible through the Windows Volume
 Manager as valid partition). Sure, it did not bother to check if
 Windows filesystems were active, etc. To get out of that situation, I
 deleted this partition from Windows, and GRUB conked with Error 22
 (okay, should have thought that earlier -- but dumb moments happen).
 Fortunately, all my data was backed up. I then booted into OBSD via
 the boot CD, and cleared the partition table as well (second dumbest
 moment). *poof* went away both operating systems.

 Now I had a laptop with clean partition table, but both OS'es intact.
 I wasn't worried to much since data was backed up, but was wary of
 setting up OBSD again (including mail, etc.). So...

 (1) I booted a live CD - MarBSD 5.1
 (2) Ran scan_ffs on the drive as scan_ffs -l sd0. It found almost
 all partitions, but was confused between /var and swap (so /var
 appeared twice!). I mounted both, and found which one was /var
 (interestingly, the other partition had exactly same content as /var,
 except for one sasl2 directory, and difference in size).
 (3) Redirected the output to a file, to be used in setting up the
disklabel.
 (4) Ran disklabel -e sd0, and added the output from scan_ffs, with
 best guesses for partition names. [read scan_ffs and disklabel
 manpages before this].
 (5) Rebooted and checked if things were fine -- /bsd booted fine,
     - However, later while mounting filesystems it stopped with
 messages to the tune of cannot mount sd0k and sd0j, etc.)
     - These were not a part of the disklabel interestingly(!)
 (6) Rebooted via OBSD 5.1 into single user mode bsd -s
 (7) Mounted / manually, and fixed /etc/fstab with correct partition names.
 (8) Reboot, and success! Everything was as-is.

 The output of scan_ffs can be seen in this image:

http://lh3.googleusercontent.com/-ln-xNFxx6WM/T-P6e4wgEMI/ApA/zygztOh
6uR8/s720/scan_ffs.jpg

 Thanks OBSD team again. Appreciate all your efforts, and the terrific
 OS. Many lessons learnt as well! :-)

 -Amarendra

Re: Upgrading OpenBSD

2012-05-23 Thread Amarendra Godbole

On 23-May-2012, at 3:35 AM, Kenneth R Westerback kwesterb...@rogers.com
wrote:

 On Tue, May 22, 2012 at 03:00:55PM -0400, Jiri B wrote:
 On Mon, May 21, 2012 at 11:01:59PM -0400, Kenneth R Westerback wrote:
 There are various automated install tools out there too, but not
 (yet) officially part of the release.

 Does it mean something is being prepared?

 If so, can that be xml based like autoyast? LOL :

 jirib

 Nah. I hear all the cool kids are using json these days. :-)

  Ken
[...]

json...oh...json...! The ability to interoperate is overrated...First it was a
wheel, then the wheel, and again the wheel... ;-)

-ag

Accessing /etc/hostname.* via raw disk

2012-05-09 Thread Amarendra Godbole

Hi,

I have an OpenBSD guest VM, which needs to be configured before it
boots up. I can access the OS through the VMWare APIs', but then need
to configure the /etc/hostname.* file to update the IP address. One
way I can think of is to lookup fsck code, and figure this out (or I
may be wrong). If there is a better way, I'd appreciate pointers.
Thanks in advance.

-Amarendra

Building kernel outside /usr/src/sys -- from the FAQ

2011-07-29 Thread Amarendra Godbole

Hi,

http://www.openbsd.org/faq/faq5.html#BldKernel has a section
Variation on above process: Read-only source tree, which talks about
building a kernel outside src/. Interestingly, when I do a GENERIC.MP
build, by following these steps, the name displayed via config is that
of the directory in which this kernel has been built. Eg.

# cd /home/foo/bar/testbuild
# cp /usr/src/sys/arch/i386/conf/GENERIC.MP .
# config -s /usr/src/sys -b . GENERIC.MP
# make clean  make depend  make
# make install

config -e displays the kernel string as:
OpenBSD 5.0-beta (testbuild) #2: Fri Jul 29 12:50:00 IST 2011
root@zimbu:/home/foo/bar/testbuild

This may confuse, especially when a dmesg is required, as it loses
the type of kernel built - GENERIC or GENERIC.MP.

Can this be clarified in the FAQ, or did I miss something?

-Amarendra

Re: Building kernel outside /usr/src/sys -- from the FAQ

2011-07-29 Thread Amarendra Godbole

On Fri, Jul 29, 2011 at 2:28 PM, Gilles Chehade gil...@poolp.org wrote:
 On Fri, Jul 29, 2011 at 10:43:52AM +0200, David Vasek wrote:
 On Fri, 29 Jul 2011, Amarendra Godbole wrote:

 Hi,
 
 http://www.openbsd.org/faq/faq5.html#BldKernel has a section
 Variation on above process: Read-only source tree, which talks about
 building a kernel outside src/. Interestingly, when I do a GENERIC.MP
 build, by following these steps, the name displayed via config is that
 of the directory in which this kernel has been built. Eg.
 
 # cd /home/foo/bar/testbuild
 # cp /usr/src/sys/arch/i386/conf/GENERIC.MP .
 # config -s /usr/src/sys -b . GENERIC.MP
 # make clean  make depend  make
 # make install
 
 config -e displays the kernel string as:
 OpenBSD 5.0-beta (testbuild) #2: Fri Jul 29 12:50:00 IST 2011
root@zimbu:/home/foo/bar/testbuild
 
 This may confuse, especially when a dmesg is required, as it loses
 the type of kernel built - GENERIC or GENERIC.MP.

 It loses the arch too. It is not easy to distinguish between i386 and
 amd64 then.

 Regards,
 David


 can't you actually do:

 # mkdir -p /home/foo/bar/testbuild/`uname -m`/GENERIC.MP
 # cd /home/foo/bar/testbuild/`uname -m`/GENERIC.MP

 which would keep the arch and kernel name in the build path just as with
 a build from the regular path ?

 Gilles

 --
 Gilles Chehade
 http://u.poolp.org/~gilles/
[...]

Is it possible to update the FAQ to reflect this? Since cd
/somewhere does not accurately indicate this, and dmesg then creates
a problem.

-Amarendra

Re: config dumps core in -current

2011-06-05 Thread Amarendra Godbole

On Sun, Jun 5, 2011 at 3:23 AM, Matthew Dempsky matt...@dempsky.org wrote:
 On Thu, Jun 2, 2011 at 10:51 PM, Amarendra Godbole
 amarendra.godb...@gmail.com wrote:
 built the latest config as detailed in the current faq, and built the
 kernel. smooth. had a problem when i did a config -ef /bsd, where
 config dumped core (~9M). did not find much here, so thought i'll
 quickly check. it is possible that something is messed up at my end.

 We removed a long-unused device configuration setting, which changed
 the ABI between config(8) and the kernel.  You need a -current
 config(8) to build and edit -current kernels, and you need an older
 config(8) to build and edit older kernels.

 If you've confirmed that they're in sync and you're still experiencing
 issues, please let us know.
[...]

mea culpa - though my sources were synced, it was a while since i
built the userland. i believe that caused problem for config, since it
depends on libkvm. config no longer dumps core now. thanks all.

-amarendra

Re: config dumps core in -current

2011-06-04 Thread Amarendra Godbole

On Fri, Jun 3, 2011 at 1:54 PM, Amarendra Godbole
amarendra.godb...@gmail.com wrote:
 On Fri, Jun 3, 2011 at 11:44 AM, Otto Moerbeek o...@drijf.net wrote:
 On Fri, Jun 03, 2011 at 11:21:17AM +0530, Amarendra Godbole wrote:

 built the latest config as detailed in the current faq, and built the
 kernel. smooth. had a problem when i did a config -ef /bsd, where
 config dumped core (~9M). did not find much here, so thought i'll
 quickly check. it is possible that something is messed up at my end. i
 am running it on a lenovo x201 thinkpad notebook.

 grumble. a non-GENERIC kernel which doesn't clearly show if it's i386
 or amd64. Please retest with a GENERIC kernel and report back,

 something is messed up with my configuration -- i did the standard
 config -s /usr/src/sys -b . GENERIC.MP acrobatics, and even then the
 dmesg is messed up. i realize this has happened in the last 2-3 weeks,
 since the kernel build before that was okay. let me dig a little
 further and report. thanks.
[...]

building the kernel via config GENERIC.MP worked, but config -s
/usr/src/sys -d . GENERIC.MP does not. config dumps core even now,

OpenBSD_49$ sudo config -ef /bsd
OpenBSD 4.9-current (GENERIC.MP) #1: Sun Jun  5 05:49:24 IST 2011
r...@zimbu.xxx.com:/usr/src/sys/arch/i386/compile/GENERIC.MP
Segmentation fault (core dumped)
OpenBSD_49$

am i missing something?

-amarendra

OpenBSD 4.9-current (GENERIC.MP) #1: Sun Jun  5 05:49:24 IST 2011
r...@zimbu.xxx.com:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES
real mem  = 1998626816 (1906MB)
avail mem = 1955090432 (1864MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/26/10, BIOS32 rev. 0 @
0xfdbe0, SMBIOS rev. 2.6 @ 0xe0010 (78 entries)
bios0: vendor LENOVO version 6QET61WW (1.31 ) date 10/26/2010
bios0: LENOVO 3680LA2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT
TCPA SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4)
EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu2: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES
cpu3 at mainbus0: apid 5 (application processor)
cpu3: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu3: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 13 (EXP1)
acpiprt3 at acpi0: bus -1 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpiprt5 at acpi0: bus 5 (EXP4)
acpiprt6 at acpi0: bus 2 (EXP5)
acpicpu0 at acpi0: C3, C1, PSS
acpicpu1 at acpi0: C3, C1, PSS
acpicpu2 at acpi0: C3, C1, PSS
acpicpu3 at acpi0: C3, C1, PSS
acpipwrres0 at acpi0: PUBS
acpitz0 at acpi0: critical temperature 100 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model 42T4835 serial   120 type LION oem SANYO
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: GDCK not docked (0)
bios0: ROM list: 0xc/0x1! 0xd/0x1000 0xd1000/0x1000
0xdd000/0x3000! 0xe/0x1
cpu0: Enhanced SpeedStep 2395 MHz: speeds: 2400, 2399, 2266, 2133,
1999, 1866, 1733, 1599, 1466, 1333, 1199 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 Intel Core Host rev 0x02
vga1 at pci0 dev 2 function 0 Intel Mobile HD graphics rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xd000, size 0x1000

Re: config dumps core in -current

2011-06-03 Thread Amarendra Godbole

On Fri, Jun 3, 2011 at 11:44 AM, Otto Moerbeek o...@drijf.net wrote:
 On Fri, Jun 03, 2011 at 11:21:17AM +0530, Amarendra Godbole wrote:

 built the latest config as detailed in the current faq, and built the
 kernel. smooth. had a problem when i did a config -ef /bsd, where
 config dumped core (~9M). did not find much here, so thought i'll
 quickly check. it is possible that something is messed up at my end. i
 am running it on a lenovo x201 thinkpad notebook.

 grumble. a non-GENERIC kernel which doesn't clearly show if it's i386
 or amd64. Please retest with a GENERIC kernel and report back,

something is messed up with my configuration -- i did the standard
config -s /usr/src/sys -b . GENERIC.MP acrobatics, and even then the
dmesg is messed up. i realize this has happened in the last 2-3 weeks,
since the kernel build before that was okay. let me dig a little
further and report. thanks.

-amarendra


-Otto


 -amarendra

 here is my dmesg:

 OpenBSD 4.9-current (kernel) #1: Fri Jun  3 10:59:16 IST 2011
 r...@zimbu.xyz.com:/home/amar/site-specific/builds/kernel
 cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
 686-class) 2.40 GHz
[...]

config dumps core in -current

2011-06-02 Thread Amarendra Godbole

built the latest config as detailed in the current faq, and built the
kernel. smooth. had a problem when i did a config -ef /bsd, where
config dumped core (~9M). did not find much here, so thought i'll
quickly check. it is possible that something is messed up at my end. i
am running it on a lenovo x201 thinkpad notebook.

-amarendra

here is my dmesg:

OpenBSD 4.9-current (kernel) #1: Fri Jun  3 10:59:16 IST 2011
r...@zimbu.xyz.com:/home/amar/site-specific/builds/kernel
cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES
real mem  = 1998626816 (1906MB)
avail mem = 1955090432 (1864MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/26/10, BIOS32 rev. 0 @
0xfdbe0, SMBIOS rev. 2.6 @ 0xe0010 (78 entries)
bios0: vendor LENOVO version 6QET61WW (1.31 ) date 10/26/2010
bios0: LENOVO 3680LA2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT
TCPA SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4)
EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 132MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu2: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES
cpu3 at mainbus0: apid 5 (application processor)
cpu3: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu3: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 13 (EXP1)
acpiprt3 at acpi0: bus -1 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpiprt5 at acpi0: bus 5 (EXP4)
acpiprt6 at acpi0: bus 2 (EXP5)
acpicpu0 at acpi0: C3, C1, PSS
acpicpu1 at acpi0: C3, C1, PSS
acpicpu2 at acpi0: C3, C1, PSS
acpicpu3 at acpi0: C3, C1, PSS
acpipwrres0 at acpi0: PUBS
acpitz0 at acpi0: critical temperature 100 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model 42T4835 serial   120 type LION oem SANYO
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: GDCK docked (15)
bios0: ROM list: 0xc/0x1! 0xd/0x1000 0xd1000/0x1000
0xdd000/0x3000! 0xe/0x1
cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2400, 2399, 2266, 2133,
1999, 1866, 1733, 1599, 1466, 1333, 1199 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 Intel Core Host rev 0x02
vga1 at pci0 dev 2 function 0 Intel Mobile HD graphics rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0 at vga1: msi
drm0 at inteldrm0
Intel 3400 MEI rev 0x06 at pci0 dev 22 function 0 not configured
Intel 3400 KT rev 0x06 at pci0 dev 22 function 3 not configured
em0 at pci0 dev 25 function 0 Intel 82577LM rev 0x06: apic 1 int 20,
address f0:de:f1:37:cc:84
ehci0 at pci0 dev 26 function 0 Intel 3400 USB rev 0x06: apic 1 int 23
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 Intel 3400 HD Audio rev 0x06: msi
azalia0: codecs: Conexant/0x5069, Intel/0x2804, using Conexant/0x5069
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 Intel 3400 PCIE rev 0x06: msi
pci1 at ppb0 bus 13
ppb1 at pci0 dev 28 function 3 Intel 3400 PCIE rev 0x06: msi
pci2 at ppb1 bus 5
ppb2 at pci0 dev 28 function 4 Intel 3400 PCIE rev 0x06: msi
pci3 at ppb2 bus 2
iwn0 at pci3 dev 0 function 0 Intel Centrino Advanced-N 6200 rev
0x35: apic 1 int 16, MIMO 2T2R, MoW, address 58:94:6b:91:87:38
ehci1 at pci0 dev 29 function 0 Intel 3400 USB rev 0x06: apic 1 int 19
usb1 at ehci1:

Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.

Hi,

I have run into a deadend trying to understand, and troubleshoot this
problem. Hence, I would like some pointers. Following is what I did to
get my OpenBSD system running, and then subsequently messing it up (in
sequence):

(1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
Did reserve ~140G for Windows, and then installed OpenBSD as described
in FAQ. Things were fine for a couple of months.

(2) Installed Windows XP ghost image to the first partition. Sadly,
ntldr was not installed so machine still booted directly into OpenBSD

(3) Installed grub. Here is what /grub/menu.lst looks like:
default 0 timeout 5
title Windows XP
root (hd0,0)
chainloader +1

title OpenBSD
root (hd0,1)
chainloader +1

(4) grub started fine, and Windows XP boots fine, but when I try to
boot OpenBSD, I get something like this:
Loading...
probing: additional details
disk: fd0 hd0+*
 OpenBSD/i386 BOOT 2.13
open(hd0a:/etc/boot.conf): Invalid argument
boot
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
 failed(22). will try ...

And OpenBSD never boots. I don't recall changing anything else. From
what I know (very little), biosboot was able to load the 2nd stage
bootloader, but it now failed loading the kernel image.

I can boot successfully into OpenBSD using a 4.8 boot CD though. I
tried running installboot again (mindlessly!), and get this error:
--
OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
Password:
boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
/boot is 3 blocks x 16384 bytes
fs block shift 2; part offset 293603940; inode block 32, offset 10792
master boot record (MBR) at sector 0
partition 0: type 0x07 offset 63 size 293603877
partition 1: type 0xA6 offset 293603940 size 377487360
installboot: invalid location: all of /boot must be  sector 268435455.
--

disklabel reads:
--
OpenBSD_49$ disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: ST9320423AS
duid: 93cf9b951f02f209
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 38913
total sectors: 625142448
boundstart: 0
boundend: 0
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize  cpg]
  a:  2104508293603940  4.2BSD   2048 163841 # /
  b:  8385937295708448swap
  c:6251424480  unused
  d: 41945696304094400  4.2BSD   2048 163841 # /usr
  e:  4192960346040096  4.2BSD   2048 163841 # /tmp
  f: 20964832350233056  4.2BSD   2048 163841 # /usr/local
  g:  4192960371197888  4.2BSD   2048 163841 # /usr/X11R6
  h:125821056375390848  4.2BSD   2048 163841 # /home
  j:  8385952501211904  4.2BSD   2048 163841 # /var
  k:  8385920509597856  4.2BSD   2048 163841 # /usr/src
  l: 12578912517983776  4.2BSD   2048 163841 # /usr/obj
OpenBSD_49$
--

dmesg is
-
OpenBSD 4.9-current (kernel) #5: Wed Mar 23 23:58:17 IST 2011
r...@zimbu.vxindia.veritas.com:/home/amar/site-specific/builds/kernel
cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
,AES
real mem  = 1998659584 (1906MB)
avail mem = 1955794944 (1865MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/26/10, BIOS32 rev. 0 @
0xfdbe0, SMBIOS rev. 2.6 @ 0xe0010 (78 entries)
bios0: vendor LENOVO version 6QET61WW (1.31 ) date 10/26/2010
bios0: LENOVO 3680LA2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT
TCPA SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4)
EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 132MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
,AES
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu2: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
,AES
cpu3 at mainbus0:

Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.

On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback
kwesterb...@rogers.com wrote:
 On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote:
 Hi,

 I have run into a deadend trying to understand, and troubleshoot this
 problem. Hence, I would like some pointers. Following is what I did to
 get my OpenBSD system running, and then subsequently messing it up (in
 sequence):

 (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
 Did reserve ~140G for Windows, and then installed OpenBSD as described

    OpenBSD will reliably boot only if located 128GB. A
   recent change has made this explicit until a more reliable
   way of booting from 128GB can be found.

 in FAQ. Things were fine for a couple of months.

[...]
 (4) grub started fine, and Windows XP boots fine, but when I try to
 boot OpenBSD, I get something like this:
 Loading...
 probing: additional details
 disk: fd0 hd0+*
  OpenBSD/i386 BOOT 2.13
 open(hd0a:/etc/boot.conf): Invalid argument
 boot
 booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
  failed(22). will try ...

 And OpenBSD never boots. I don't recall changing anything else. From
 what I know (very little), biosboot was able to load the 2nd stage
 bootloader, but it now failed loading the kernel image.

 I can boot successfully into OpenBSD using a 4.8 boot CD though. I
 tried running installboot again (mindlessly!), and get this error:
 --
 OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
 Password:
 boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
 /boot is 3 blocks x 16384 bytes
 fs block shift 2; part offset 293603940; inode block 32, offset 10792
 master boot record (MBR) at sector 0
 partition 0: type 0x07 offset 63 size 293603877
 partition 1: type 0xA6 offset 293603940 size 377487360
 installboot: invalid location: all of /boot must be  sector 268435455.

 And here is the error now being generated. If you have a BIOS/Hardware
 combo that can actually boot from 128GB, you can recompile installboot
 and friends after changing the value of BIOSBOOT_MAXSEC in
sys/sys/disklabel.h.

Okay, so I changed BOOTBIOS_MAXSEC and got installboot to work fine.
Nothing seems to have changed though, as I still run into the booting
hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try...
error message at boot.

What surprises me is OpenBSD booted fine *before* I had Windows XP,
and the ~143G partition was still present. Possibly something else is
broken...

makeactive in menu.lst for grub did not help either (as I had guessed).

-Amarendra
[...]

[FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.

Okay, seems like I sent a hasty reply earlier.

Got this fixed, by booting off a 4.8 CD, and upgrading - fsck all
filesystems, say no to bsd, bsd.mp and base, it created device nodes,
and congratulated me for completion of the upgrade. Rebooted, and the
system came up nicely.

Noticed two things:
(a) the * after hd0+ is gone during boot
(b) the disklabel now shows proper values for boundstart and
boundend - earlier both were 0.

Thanks to all those who replied. Now I am off to reading more about
boot, and friends (though I am not sure if things are well at this
point!).

-Amarendra

On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback
kwesterb...@rogers.com wrote:
 On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote:
 Hi,

 I have run into a deadend trying to understand, and troubleshoot this
 problem. Hence, I would like some pointers. Following is what I did to
 get my OpenBSD system running, and then subsequently messing it up (in
 sequence):

 (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
 Did reserve ~140G for Windows, and then installed OpenBSD as described

    OpenBSD will reliably boot only if located 128GB. A
   recent change has made this explicit until a more reliable
   way of booting from 128GB can be found.

 in FAQ. Things were fine for a couple of months.

 (2) Installed Windows XP ghost image to the first partition. Sadly,
 ntldr was not installed so machine still booted directly into OpenBSD

 (3) Installed grub. Here is what /grub/menu.lst looks like:
 default 0 timeout 5
 title Windows XP
 root (hd0,0)
 chainloader +1

 title OpenBSD
 root (hd0,1)
 chainloader +1

 (4) grub started fine, and Windows XP boots fine, but when I try to
 boot OpenBSD, I get something like this:
 Loading...
 probing: additional details
 disk: fd0 hd0+*
  OpenBSD/i386 BOOT 2.13
 open(hd0a:/etc/boot.conf): Invalid argument
 boot
 booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
  failed(22). will try ...

 And OpenBSD never boots. I don't recall changing anything else. From
 what I know (very little), biosboot was able to load the 2nd stage
 bootloader, but it now failed loading the kernel image.

 I can boot successfully into OpenBSD using a 4.8 boot CD though. I
 tried running installboot again (mindlessly!), and get this error:
 --
 OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
 Password:
 boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
 /boot is 3 blocks x 16384 bytes
 fs block shift 2; part offset 293603940; inode block 32, offset 10792
 master boot record (MBR) at sector 0
 partition 0: type 0x07 offset 63 size 293603877
 partition 1: type 0xA6 offset 293603940 size 377487360
 installboot: invalid location: all of /boot must be  sector 268435455.

 And here is the error now being generated. If you have a BIOS/Hardware
 combo that can actually boot from 128GB, you can recompile installboot
 and friends after changing the value of BIOSBOOT_MAXSEC in
sys/sys/disklabel.h.

 If you have any knowledge on how to reliably detect that the BIOS/Hardware
 will correctly support EDD access beyond 128GB, we are very interested.

  Ken

 --

 disklabel reads:
 --
 OpenBSD_49$ disklabel sd0
 # /dev/rsd0c:
 type: SCSI
 disk: SCSI disk
 label: ST9320423AS
 duid: 93cf9b951f02f209
 flags:
 bytes/sector: 512
 sectors/track: 63
 tracks/cylinder: 255
 sectors/cylinder: 16065
 cylinders: 38913
 total sectors: 625142448
 boundstart: 0
 boundend: 0
 drivedata: 0

 16 partitions:
 #size   offset  fstype [fsize bsize  cpg]
   a:  2104508293603940  4.2BSD   2048 163841 # /
   b:  8385937295708448swap
   c:6251424480  unused
   d: 41945696304094400  4.2BSD   2048 163841 # /usr
   e:  4192960346040096  4.2BSD   2048 163841 # /tmp
   f: 20964832350233056  4.2BSD   2048 163841 #
/usr/local
   g:  4192960371197888  4.2BSD   2048 163841 #
/usr/X11R6
   h:125821056375390848  4.2BSD   2048 163841 # /home
   j:  8385952501211904  4.2BSD   2048 163841 # /var
   k:  8385920509597856  4.2BSD   2048 163841 #
/usr/src
   l: 12578912517983776  4.2BSD   2048 163841 #
/usr/obj
 OpenBSD_49$
 --

 dmesg is
 -
 OpenBSD 4.9-current (kernel) #5: Wed Mar 23 23:58:17 IST 2011
 r...@zimbu.vxindia.veritas.com:/home/amar/site-specific/builds/kernel
 cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
 686-class) 2.40 GHz
 cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES
T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
 ,AES
 real mem

Re: [FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.

On Sun, Mar 27, 2011 at 12:23 AM, Kenneth R Westerback
kwesterb...@rogers.com wrote:
 On Sat, Mar 26, 2011 at 11:59:17PM +0530, Amarendra Godbole wrote:
 Okay, seems like I sent a hasty reply earlier.

 Got this fixed, by booting off a 4.8 CD, and upgrading - fsck all
 filesystems, say no to bsd, bsd.mp and base, it created device nodes,
 and congratulated me for completion of the upgrade. Rebooted, and the
 system came up nicely.

 And now has 4.8 or 4.9 installed?

4.9, since I said no to everything. I re-created device nodes after
booting, so hopefully things are okay.

 Noticed two things:
 (a) the * after hd0+ is gone during boot

 The '*' reports a failure to find an OpenBSD disklabel.
 The '+' reports the BIOS claiming support of EDD, a.k.a. BIOS LBA, access.

 (b) the disklabel now shows proper values for boundstart and
 boundend - earlier both were 0.

 Because earlier the OpenBSD partition was not found, and thus unable to
 provide the bound information.

Yes, that was nagging me earlier, but somehow I could not fix it -
there is too much to understand for the i386 boot process, and the
partition and disklabel is a source of confusion for me.

Thanks for your pointers, I atleast had heart to continue trying to
fix (agree, I did not understand all - but since the CD boot was
working fine, and I have a full backup of my data, I decided to
probe.)

-Amarendra



 Thanks to all those who replied. Now I am off to reading more about
 boot, and friends (though I am not sure if things are well at this
 point!).

 -Amarendra

 On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback
 kwesterb...@rogers.com wrote:
  On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote:
  Hi,
 
  I have run into a deadend trying to understand, and troubleshoot this
  problem. Hence, I would like some pointers. Following is what I did to
  get my OpenBSD system running, and then subsequently messing it up (in
  sequence):
 
  (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
  Did reserve ~140G for Windows, and then installed OpenBSD as described
 
  ? ? ? ? ? ? ?  OpenBSD will reliably boot only if located 128GB. A
  ? ? ? ? ? ? ? recent change has made this explicit until a more reliable
  ? ? ? ? ? ? ? way of booting from 128GB can be found.
 
  in FAQ. Things were fine for a couple of months.
 
  (2) Installed Windows XP ghost image to the first partition. Sadly,
  ntldr was not installed so machine still booted directly into OpenBSD
 
  (3) Installed grub. Here is what /grub/menu.lst looks like:
  default 0 timeout 5
  title Windows XP
  root (hd0,0)
  chainloader +1
 
  title OpenBSD
  root (hd0,1)
  chainloader +1
 
  (4) grub started fine, and Windows XP boots fine, but when I try to
  boot OpenBSD, I get something like this:
  Loading...
  probing: additional details
  disk: fd0 hd0+*
   OpenBSD/i386 BOOT 2.13
  open(hd0a:/etc/boot.conf): Invalid argument
  boot
  booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
  ?failed(22). will try ...
 
  And OpenBSD never boots. I don't recall changing anything else. From
  what I know (very little), biosboot was able to load the 2nd stage
  bootloader, but it now failed loading the kernel image.
 
  I can boot successfully into OpenBSD using a 4.8 boot CD though. I
  tried running installboot again (mindlessly!), and get this error:
  --
  OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
  Password:
  boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
  /boot is 3 blocks x 16384 bytes
  fs block shift 2; part offset 293603940; inode block 32, offset 10792
  master boot record (MBR) at sector 0
  ? ? ? ? partition 0: type 0x07 offset 63 size 293603877
  ? ? ? ? partition 1: type 0xA6 offset 293603940 size 377487360
  installboot: invalid location: all of /boot must be  sector 268435455.
 
  And here is the error now being generated. If you have a BIOS/Hardware
  combo that can actually boot from 128GB, you can recompile installboot
  and friends after changing the value of BIOSBOOT_MAXSEC in 
  sys/sys/disklabel.h.
 
  If you have any knowledge on how to reliably detect that the BIOS/Hardware
  will correctly support EDD access beyond 128GB, we are very interested.
 
   Ken
 
  --
 
  disklabel reads:
  --
  OpenBSD_49$ disklabel sd0
  # /dev/rsd0c:
  type: SCSI
  disk: SCSI disk
  label: ST9320423AS
  duid: 93cf9b951f02f209
  flags:
  bytes/sector: 512
  sectors/track: 63
  tracks/cylinder: 255
  sectors/cylinder: 16065
  cylinders: 38913
  total sectors: 625142448
  boundstart: 0
  boundend: 0
  drivedata: 0
 
  16 partitions:
  # ? ? ? ? ? ? ? ?size ? ? ? ? ? offset ?fstype [fsize bsize ?cpg]
  ? a: ? ? ? ? ?2104508 ? ? ? ?293603940 ?4.2BSD ? 2048 16384 ? ?1 # /
  ? b: ? ? ? ? ?8385937 ? ? ? ?295708448 ? ?swap
  ? c: ? ? ? ?625142448 ? ? ? ? ? ? ? ?0 ?unused
  ? d: ? ? ? ? 41945696 ? ? ? ?304094400 ?4.2BSD ? 2048 16384 ? ?1 # /usr

Re: -current ports compile fails in /usr/src/lib/libc/gen/vis.c

2010-08-22 Thread Amarendra Godbole

On Mon, Aug 23, 2010 at 2:08 AM, Amit Kulkarni amitk...@gmail.com wrote:
 # sysctl -n kern.version
 OpenBSD 4.8-current (GENERIC) #3: Sun Aug 22 12:49:11 CDT 2010
a...@pilloo.my.domain:/usr/src/sys/arch/i386/compile/GENERIC

 I did do a cvs update src, ports, xenocara for -current. Submitted dmesg
 too.

 Compiled, installed, rebooted with new kernel

 Having the same problem since yesterday (or was it friday?)  today, so
 thought to report it

 Complete newbie to -current

 cc -O2 -pipe -g -I/usr/src/lib/libc/include -DAPIWARN -DYP
 -I/usr/src/lib/libc/yp -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc
 -I/usr/src/lib/libc/gdtoa -I/usr/src/lib/libc/arch/i386/gdtoa
-DINFNAN_CHECK
 -DMULTIPLE_THREADS -DNO_FENV_H -DUSE_LOCALE -I/usr/src/lib/libc
 -I/usr/src/lib/libc/citrus -DRESOLVSORT -DPOSIX_MISTAKE -DFLOATING_POINT
 -DNLS   -c /usr/src/lib/libc/gen/vis.c -o vis.o
 /usr/src/lib/libc/gen/vis.c: In function 'vis':
 /usr/src/lib/libc/gen/vis.c:57: error: 'VIS_ALL' undeclared (first use in
 this function)
 /usr/src/lib/libc/gen/vis.c:57: error: (Each undeclared identifier is
 reported only once
 /usr/src/lib/libc/gen/vis.c:57: error: for each function it appears in.)
 /usr/src/lib/libc/gen/vis.c:109: error: 'VIS_HEX' undeclared (first use in
 this function)
[...]

I hope you are religiously following instructions here:
http://www.openbsd.org/faq/faq5.html#BldUserland.

Another important thing you may want to look at (since you run
-current) is http://www.openbsd.org/faq/current.html Especially check
the config(8) and gcc4 updates.

-Amarendra

Re: OpenBSD culture?

2010-04-14 Thread Amarendra Godbole

On Thu, Apr 15, 2010 at 6:05 AM, Greg Thomas get.li...@gmail.com wrote:
 On Wed, Apr 14, 2010 at 5:21 PM, Aaron Glenn aaron.gl...@gmail.com wrote:


 sincerity by itself is useless. if you can't take the time to read the
 concise, thoughtfully produced information provided in both manual
 pages, the FAQ, and the mailing list archives then you will most
 definitely be told to gfy and read what has been painstakingly written
 for your benefit. any other response is borne from pity.


 Not reading the fine documentation is a sign of obvious insincerity.
[...]

Because most Linux distros' have inaccurate/incomplete documentation
most of the time, it is difficult to find reliable answers. Hence,
the tendency of linux users to ask questions first.

Obviously, my experience strongly indicates that OpenBSD strives very
hard for the same level of correctness in their documentation, as
their code and hence folks get most of the stuff from the docs (either
the man pages, or the FAQ).

This is a cultural difference, and I don't see Linux bridging that gap
anytime soon -- they are too busy with adding bell and whistles to the
kernel, that are useless most of the time for most of the folks.

-Amarendra

Re: Major and minor version changes

2010-04-01 Thread Amarendra Godbole

 I think its dangerous to automatically say that libfoo-a.b.c is going to
 be the same across OS's, as that assumes the compiler is the same.
 With the case of gcc, I'd be wary of that.

Agree, libraries were an example - my point was *all* dependencies,
including the compiler and kernel.

 As for minor bumps not being a worry, what if the part of the library
 that caused the bump is something that you really depend on?

My question is: do minor versions of the library introduce any API
change for example, or are most of the minor versions generally
backward compatible? I may be wrong in the major-minor version
interpretation though.

 After having done testing of software/hardware in the pre-open
 source world, I've come to the conclusion that its cutting corners to
 make assumptions, and no matter how much of a pain in the ass it
 is, testing everything, at least sometimes, is the right thing to do.

 --STeve Andre'

Agree -- doing away with complete testing always is not an option,
but isn't the behavior of the minor version bumps in terms of compat
predictable enough not to run full test cycles every time a minor
version is bumped?

I am not building a case against testing, but wanted to see if things
can be optimized, and the general fear of test all if *anything* has
changed can be modified to make a decision to test *all*, based on
*what* has changed.

Thanks for the feedback folks.

-Amarendra

Re: Major and minor version changes

2010-04-01 Thread Amarendra Godbole

On Thu, Apr 1, 2010 at 9:10 AM, Marco Peereboom sl...@peereboom.us wrote:
 Completely insane!

 Of course you have to test!

Boo hoo, can't I even make an assumption that APIs' would be backward
compatible across minor version changes? :-/

-Amarendra


 On Thu, Apr 01, 2010 at 08:35:00AM +0530, Amarendra Godbole wrote:
 I am having this discussion with a colleague, who wants to test the
 application across various OS versions (Debian in this case). My
 argument (supported by experience) is that one should re-test the
 application only if the dependencies have had a major version change.
 For eg., if app A depends on libc-x.y.z, and libfoo-a.b.c, ideally no
 testing is required for all OS releases that have libc-x.*.* and
 libfoo-a.*.* -- the same major version.

 The idea being - minor version bumps do not spring surprises, but
 major version almost always do. App A is a large enterprise app
 being discussed, and my idea is the optimize the QA cycles that the
 team has to put in.

 Is my experience sound enough to say this, or are there any exceptions
 to the norm? How does OpenBSD handle this situation? If I have to
 release an app on OpenBSD-4.6 and -4.7, as long as I ensure that all
 the dependencies of the app have the same major version across both
 releases, it should run fine on both.

 Thanks.

 -Amarendra

Major and minor version changes

2010-03-31 Thread Amarendra Godbole

I am having this discussion with a colleague, who wants to test the
application across various OS versions (Debian in this case). My
argument (supported by experience) is that one should re-test the
application only if the dependencies have had a major version change.
For eg., if app A depends on libc-x.y.z, and libfoo-a.b.c, ideally no
testing is required for all OS releases that have libc-x.*.* and
libfoo-a.*.* -- the same major version.

The idea being - minor version bumps do not spring surprises, but
major version almost always do. App A is a large enterprise app
being discussed, and my idea is the optimize the QA cycles that the
team has to put in.

Is my experience sound enough to say this, or are there any exceptions
to the norm? How does OpenBSD handle this situation? If I have to
release an app on OpenBSD-4.6 and -4.7, as long as I ensure that all
the dependencies of the app have the same major version across both
releases, it should run fine on both.

Thanks.

-Amarendra

Re: tools for finding a type of bug?

2010-03-07 Thread Amarendra Godbole

On Fri, Mar 5, 2010 at 11:02 PM, Mark Bucciarelli mkb...@gmail.com wrote:
 Is there some set of tools you all use to
 help find bad code?

 Specifically, I'm working with a large code
 base (monetdb), and have found two instances
 where the fopen() return value was not
 checked.

 Now I'd like to search the tree and find all
 instances of this bug.

 How do you do this?  Must it be manual or
 are there static analysis tools (e.g., grep 
 awk or perhaps clang) that you use.

 (I didn't mark as OT b/c I'm working towards
 an OpenBSD port of this most-excellent db.)
[...]

grep is an excellent static source code analyzer if you know what you
are looking for. If you don't know what you are looking for, then you
should mostly pay folks who know things that you might be looking for
(for eg., fortify, coverity).

-Amarendra

Re: Recommended laptop

2009-12-29 Thread Amarendra Godbole

On Tue, Dec 29, 2009 at 12:30 AM, STeve Andre' and...@msu.edu wrote:
 On Monday 28 December 2009 04:27:40 Johan M:son Lindman wrote:
 On Tuesday 22 December 2009 04:57:55 STeve Andre' wrote:
  On Monday 21 December 2009 22:48:45 James Hozier wrote:
   This will be my first purchase that is focused primarily on having
only
   OpenBSD on it and nothing else to be used as a main workstation. The
   budget is around $900 or so. I'm looking for something with quality
parts
   and probably have everything supported and compatible with OpenBSD
   straight out of the box (like the graphics/sound, wireless card, etc.)
  
   I've heard that most developers use Thinkpads. Which model would be a
   good suggestion?
 
  A problem is that $900 isn't going to get you a thinkpad and a
multi-year
  warranty.  If you stay away from nvidia video, just about all the
thinkpads
  are going to work with the ooccaisonal exception of the wireless card,
and
  I'm not sure that hasn't shrunk a bunch, the ones that don't work.  My
W500
  runs OpenBSD wonderfully.
 
  Looking at the Lenovo site I see a T500 with a 15 screen with *led*
back
  light, 160G disk 2.4G core two something, intel wifi and intel graphics
  for $849.  I don't know the status of the Intel graphics card, but you
  could get that, except it has a 1 year warranty.  There are discounts
  if you can get it through an educational organization, etc.
 
  --STeve Andre'

 If you get a Thinkpad stay clear of the SL300.
 It's cheap crap.

 I suppose I should add to this.  In order to compete with
HP/Dell/Toshiba/Sony
 Lenovo had to come out with a low end series, the SL.  Having used one for
a
 few days I will say that the SL is better than its competitors, but still
not
 as good as the W or T series Thinkpads.  Note that you can increase the
price
 of an SL by 50% and get a 3 year on site warranty, so Lenovo will back it
up.

 The T, W and X series are the reliable units, with the X series being a
little
 weaker in the physical ruggedness department.  The R series seems to be
best
 for desktop usage, somewhere between the SL and T/W in terms of
reliability.
[...]

[OT]
I can contest the physical ruggedness thingy -- about an year and half
ago, I had a nasty fall, and my X60 banged on the concrete floor on
its lower right hand vertex. The fall was bad, because my backpack
took my entire weight when I slipped sideways and fell down, with the
Thinkpad vertext touching the ground first, followed by me. :-) It
only sustained a break on that corner, and on the LCD top corner, but
not a single functional issue has it developed since then.

Sure, I have no data to backup the ruggedness of T and W, but I call
*this* as reasonably rugged.
[/OT]

So yes, I also find the Thinkpads' to be a better option
aesthetically, but that's just me. I have been running OpenBSD on X60
with standard configuration, and every necessary thing works just
fine.

Ah, but don't get the X60 since it has known heating issues in most
configurations, where, due to poor ventilation, the wireless card
heats up a lot, and your right palm faces the heat! X61 tried to fix
it by having an additional fan (some configurations), and a exhaust
vent on the right side. You can stick a USB cooling fan underneath,
and it is okay.

-Amarendra

Re: OpenBSD book

2009-12-20 Thread Amarendra Godbole

On Mon, Dec 21, 2009 at 2:31 AM, Julian Leyh jul...@vgai.de wrote:
 ropers schrieb:
 http://i.imgur.com/ggkB5.png

 High Quality and Wikipedia articles are mutually exclusive!

+1

 better get one of those: http://openbsd.org/books.html

That reminds me: OpenBSD 4.0: A Crash Course (PDF)  is now updated for
4.1. This name probably needs to be changed. Looping in www@

-Amarendra

Partitioning an external USB drive through OpenBSD -- disklabel

2009-10-30 Thread Amarendra Godbole

Hi,

I have a 320G Buffalo Ministation external USB drive, which I wish to
partition so that it contains 1 DOS and 1 native OpenBSD (FFS)
partition. Using disklabel, I could created these:
 p
OpenBSD area: 0-625142448; size: 625142448; free: 0
#size   offset  fstype [fsize bsize  cpg]
  c:6251424480  unused
  h:310557618314584830  4.2BSD   2048 163841
  i:3145848300   MSDOS


Now I format sd1h with newfs and things go fine. But when I format
sd1i with newfs_msdos, I see the disklabel changed to something like
this:
OpenBSD_46$ sudo disklabel -E sd1
Label editor (enter '?' for help at any prompt)
 p
OpenBSD area: 0-625142448; size: 625142448; free: 0
#size   offset  fstype [fsize bsize  cpg]
  c:6251424480  unused
  i:6251424480   MSDOS


So the FFS partition is gone. I want the USB disk to be also used on
Windows XP, so the MSDOS partition. I am not sure if this is possible,
since disklabel is OpenBSD specific, and XP may not be able to see it
anyways. I am missing something here for sure, but cannot figure out
what. Would appreciate a pointer. Thanks.

Also, is there another way to achieve this? (I was unable to create a
MSDOS partition from Windows XP, as it only allows NTFS now).

-Amarendra

Re: Partitioning an external USB drive through OpenBSD -- disklabel

2009-10-30 Thread Amarendra Godbole

On Fri, Oct 30, 2009 at 4:06 PM, Otto Moerbeek o...@drijf.net wrote:
 The disklabel is written at the start of the disk and you're
 overwriting it with the newfs_msdos command. You should fdisk the
 disk first, and reserve a separate MBR partition for MSDOS.

 See the FAQ.

Thank you all for responses -- I have a better idea now. The only
thing that I noticed was newfs_msdos wipes out the entire disklabel as
well as any fdisk created partitions and gobbles up the entire disk.

I guess what James Hartley said in this thread is correct -- Windows
must be used to create the DOS partition, and then disklabel to get
the OpenBSD one.

-Amarendra


-Otto

 On Fri, Oct 30, 2009 at 03:30:23PM +0530, Amarendra Godbole wrote:

 Hi,

 I have a 320G Buffalo Ministation external USB drive, which I wish to
 partition so that it contains 1 DOS and 1 native OpenBSD (FFS)
 partition. Using disklabel, I could created these:
  p
 OpenBSD area: 0-625142448; size: 625142448; free: 0
 #size   offset  fstype [fsize bsize  cpg]
   c:6251424480  unused
   h:310557618314584830  4.2BSD   2048 163841
   i:3145848300   MSDOS
 

 Now I format sd1h with newfs and things go fine. But when I format
 sd1i with newfs_msdos, I see the disklabel changed to something like
 this:
 OpenBSD_46$ sudo disklabel -E sd1
 Label editor (enter '?' for help at any prompt)
  p
 OpenBSD area: 0-625142448; size: 625142448; free: 0
 #size   offset  fstype [fsize bsize  cpg]
   c:6251424480  unused
   i:6251424480   MSDOS
 

 So the FFS partition is gone. I want the USB disk to be also used on
 Windows XP, so the MSDOS partition. I am not sure if this is possible,
 since disklabel is OpenBSD specific, and XP may not be able to see it
 anyways. I am missing something here for sure, but cannot figure out
 what. Would appreciate a pointer. Thanks.

 Also, is there another way to achieve this? (I was unable to create a
 MSDOS partition from Windows XP, as it only allows NTFS now).

 -Amarendra

Re: 4.6 arriving

2009-10-21 Thread Amarendra Godbole

On Wed, Oct 21, 2009 at 9:26 PM, Andri li...@braisel.com wrote:
 Yes, yes, yes!

 Also 4.6 arrived in East Frisia, Germany, yesterday from OpenBSDEurope.
 Great work. Especially, but not exclusively, the artwork ;-)

 ThX to all of you for this fine piece of OS.
[...]

When will my copy arrive? *sigh* The postal-mail system here in India
works at a snail's pace, and I hope my mug arrives as a single-piece
too.

Thanks to all OpenBSD folks for a superb OS -- ever since I have
started using it, I don't feel like going to anything else, though I
am aware of using the tool for the job. I try and mostly succeed in
making OpenBSD do what I want it to do. :-)

And all the folks on misc@, a thanks to you all too -- I have turned
from a juvenile to a reasonable OpenBSD user due to all your support
and help.

-Amarendra
 Pune, India.

Re: Defending OpenBSD Performance

2009-09-16 Thread Amarendra Godbole

On Wed, Sep 16, 2009 at 10:22 PM, Bob Beck b...@ualberta.ca wrote:
 boo hoo. run one machine somewhere and make release. done.

 Once you have a built release you can run upgrades everywhere from
 that release tarball.

 man release

 to figure out how to do that.

 Now you may ask, why don't we do that?  We simply do not have the
 resources and time to
 devote racks of machines, developer time, and internet bandwidth to
 building stable somewhere
 for all architectures, and distributing it securely.

 Us (the developers) would rather spend our time improving the os and
 our resources at
 distributing it and making it better than expending a lot of effort
 because someone is
 too lazy to rtfm and patch something themselves.  If you want push
 butan, get os, please
 go run windows 7 or OSuX.. you'll be much happier, as will we because
 the neediness
 of our user community goes down.

 The fact that you have to not be lazy to use OpenBSD is important to
 us. Unlike a commercial
 OS, or linux, we don't measure our success in how popular it is, or if
 we're going to replace the
 evil microsoft any time soon. we *WANT* needy lazy users to use those
 other OS's so we can
 concentrate on making something that works and is stable for people
 who really need it, like
 ourselves.
[...]

Well said. Recently, I introduced a friend to OpenBSD 4.5 through the
CDs', and deliberately asked him to follow the install manual (he was
firstly surprised to see only 4 pages) and go ahead and install.
Within 30 minutes he came running out of the lab, with eyes sparkling
and said -- never ever have I seen such a small install manual, and
an installation that goes through perfect as indicated in there. He
manages a redhat ent linux farm, and is now trying to assess the
stability of OpenBSD, so that he can cutover some of his linux boxes
to OpenBSD.

My personal experience tells me this -- OpenBSD is simple and elegant.
Irrespective of what benchmarks tell you, they can never tell me
anything about simplicity and as a result anything about elegance. So
they are useless for me atleast. There is no point purchasing an Audi
A6, when my 10 yr old Fiat does the same job, and does it well
(reaches me in time - the additional time I buy due to Audi's speedup
is not worth spending the additional $$ that it costs). Tradeoffs,
tradeoffs,...

-Amarendra

Re: OT: Laptop advice. SSD costs.

2009-09-16 Thread Amarendra Godbole

On Mon, Sep 14, 2009 at 9:26 PM, Edd Barrett vex...@gmail.com wrote:
 Hi,

 On Mon, Sep 14, 2009 at 4:35 PM, Dan Harnett dan...@harnett.name wrote:
 At least here, one could get a used X60 for the cost of the 128GB drive.

 Yes, I think this is my new plan. Would have been nice to have the
 tablet, but it's not essential.

 Thanks to all that replied.
[...]

Be careful with X60, since it has *known* heating issues for the
wireless (intel one) -- the right palm rest terribly heats up, and it
is very uncomfortable to use then. I have the one that heats up, and I
know how it is like on OpenBSD (less heating observed on Windows). No
changes were observed even after changing the power. Lenovo finally
replaced the entire motherboard for my X60, and it now heats up less.
So if you are planning to go for a resale X60, confirm this first.

Turns out that the vents and sinks are poorly designed around the card
under the palm rest. In X61, they added a vent mesh on the right,
which has reduced this problem somewhat.

More details on the heating issue here:
http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/x6x-thinkpad-hot-palmrest-issue/td-p/775

-Amarendra

Re: Why does OBSD advise to use packages if they are outdated?

2009-09-01 Thread Amarendra Godbole

On Wed, Sep 2, 2009 at 4:39 AM, David Taverasd3taveras3...@gmail.com wrote:
 Hello community,Thanks for all the hard work for the developers and testers
 out there, I have a confusion:
 W
 hy OBSD strongly advises to use packages over building an application from
 ports (according to FAQ 15.4.6) if :

 a.) Obsd does not maintain the stable packages since 4.0 (source:
 http://www.openbsd.org/pkg-stable.html)
 b.) The packages are only from -release because they are downloaded from
 ftp/cd and therefore do not contain reliability and security patches applied
 to applications build from ports stable? ( Source
 ftp://ftp.openbsd.org/pub/OpenBSD/4.5/packages/i386/ all packages last
 updated on 03/03/2009)

 If it is advised to use packages, then why follow the important security
 updates from the stable branch? Iam sure there are many highly used packages
 that have security fixes available (such as apache2) that I would need to
 compile from ports.

 It is annoying that everytime I ask a question about an application that I
 build from ports I get asked why I didnt use packages.. my answer is..
 because most of the time the package is outdated and can be vulnerable!

 What am I missing?

15.4.6 also says:
Of course, there are a few good reasons to use ports over packages in
some cases:
* Distribution rules prohibit OpenBSD from distributing a package.
* You wish to modify or debug the application or study its source code.
* You need a flavor of a port that is not built by the OpenBSD ports team.
* You wish to alter the directory layout (i.e. modifying PREFIX or
SYSCONFDIR).

Hope it answers your question.

-Amarendra


 Thanks

 Daniel

 15.4.6 - What should I use: packages or ports? In general, you are *highly
 advised* to use packages over building an application from ports. The
 OpenBSD ports team considers packages to be the goal of their porting work,
 not the ports themselves.

Primary group wheel -- still cannot su -

2009-07-30 Thread Amarendra Godbole

Hi,

I recently installed 4.5 from the CD, and while adding user amar, I
set the primary group to wheel. But now when I try to do a su -, I
am kicked out for not being in group wheel. Though FAQ 10.1 says that
one has to be manually added to group wheel if su - is needed, does it
mean that folks having primary group as wheel are denied? Did I miss
something very obvious?

Here is the transcript:
==
$ id
uid=1001(amar) gid=0(wheel) groups=0(wheel)
$ su -
Password:
you are not in group wheel
Sorry
$ dmesg | head -10
OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Xeon(TM) CPU 2.40GHz (GenuineIntel 686-class) 2.39 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR
real mem  = 4026040320 (3839MB)
avail mem = 3913691136 (3732MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/25/03, BIOS32 rev. 0 @
0xffe90, SMBIOS rev. 2.3 @ 0xfb290 (56 entries)
bios0: vendor Dell Computer Corporation version A05 date 06/25/2003
bios0: Dell Computer Corporation PowerEdge 1750
$
==

Thanks.

-Amarendra

Re: Primary group wheel -- still cannot su -

2009-07-30 Thread Amarendra Godbole

On Fri, Jul 31, 2009 at 10:22 AM, Theo de Raadtdera...@cvs.openbsd.org
wrote:
 I recently installed 4.5 from the CD, and while adding user amar, I
 set the primary group to wheel. But now when I try to do a su -, I
 am kicked out for not being in group wheel. Though FAQ 10.1 says that
 one has to be manually added to group wheel if su - is needed, does it
 mean that folks having primary group as wheel are denied? Did I miss
 something very obvious?

 Here is the transcript:
 ==
 $ id
 uid=1001(amar) gid=0(wheel) groups=0(wheel)
 $ su -
 Password:
 you are not in group wheel

 I don't know why it is so difficult to read the manual pages

 % man su


 If group 0 (normally ``wheel'') has users listed then only those users
 can su to ``root''.  It is not sufficient to change a user's
/etc/passwd
 entry to add them to the ``wheel'' group; they must explicitly be
listed
 in /etc/group.  If no one is in the ``wheel'' group, it is ignored, and
 anyone who knows the root password is permitted to su to ``root''.
[...]

Ouch! Caught in the wrong foot -- I read everything but the man page.
:-[ So I did miss something very *obvious*.

-Amarendra

Re: New snapshots - new installer

2009-05-08 Thread Amarendra Godbole

On Fri, May 8, 2009 at 1:31 PM, Antoine Jacoutot ajacou...@bsdfrog.org
wrote:
 On Thu, 7 May 2009, Theo de Raadt wrote:
 useradd really does that?  A new group for every user?  I think that
 is stupid behaviour.  But I will think about if we should this in the
 script.

 I agree, it is stupid behaviour.

 FWIW, adduser(8) may be doing this, but by default useradd(8) adds a new
 user to the users group which is what I would expect from the install
 script too.
[...]

I second that. IMHO, creating so many groups when users suffices is
not needed. Adding new users to users group by default also helps in
better and simplified privilege management.

-Amarendra

Re: openbsd europe

2009-04-06 Thread Amarendra Godbole

On Mon, Apr 6, 2009 at 7:29 PM, Duncan Patton a Campbell
campb...@neotext.ca wrote:

 Howdy Amarendtra, all?

 I note here the comment that shipping to India
 is quicker from Europe than from Canada or the US.

 How are these shipments being made?  In my (long)
 experience it is quicker/cheaper/more reliable to
 use the standard postal system for international
 shipments of sw images than pretty much anything
 else.  There are various reasons for this, not
 all of which are constructively defined.
[...]

Yes, I believe they ship via standard postal system. Over the last
year or so, stuff sent from the US and Canada took more time to arrive
at my place, than that shipped from the EU. Both were standard postal
system. So I am led to believe that this will be the case this time
too, though I know my sample space is very limited. :-)

-Amarendra

Re: openbsd europe

2009-04-05 Thread Amarendra Godbole

On Tue, Apr 7, 2009 at 4:19 AM, Jesus Sanchez zexe...@gmail.com wrote:
 I didn't knew about that site, does www.openbsdeurope.com have any
 relationship with the OpenBSD project? I'm from Spain and since the
 Wim issue I'm going to try this web. Any previous experience with them?
[...]

I recently pre-ordered from them, and was happy that they agreed to
ship to a country not listed in their shipping zone -- India. The cost
breaks-even for me, as both the computer shop and obsdeurope roughly
cost roughly the same amount. But in my experience, shipments from EU
reach India faster than those from Canada or US, so thought of giving
them a try.

The service is very friendly, and prompt. And I am happy that the
money is going back into the OpenBSD project. Thanks.

-Amarendra

Weird behavior of find on ntfs partition

Folks,

I saw find behaving inconsistently while finding files on an ntfs
partition. It was unable to find files ending in .dat, but then later
on it did find those. C drive has been mounted on /mnt/m0, and the
other partition has Windows XP. Details below:

---
OpenBSD_45$ pwd
/mnt/m0/Program Files/Norton Internet Security
OpenBSD_45$ ls
BrandingEngine  MUI isolate.ini
OpenBSD_45$ cd MUI
OpenBSD_45$ ls
16.1.0.33fallback.dat langver.map  maplngid.dat
OpenBSD_45$ find . -name *.dat
./fallback.dat
./maplngid.dat
OpenBSD_45$ cd ../
OpenBSD_45$ pwd
/mnt/m0/Program Files/Norton Internet Security
OpenBSD_45$ find . -name *.dat
./Branding/fallback.dat
./Engine/16.2.0.7/ccGEvt/Global/LM.dat
./Engine/16.2.0.7/ccGLog/ccGLog.dat
./Engine/16.2.0.7/hnData.dat
./Engine/16.2.0.7/Jobs/ccJobManagerSchedules.dat
./Engine/16.2.0.7/NCOVER.dat
./Engine/16.2.0.7/ncwTrstP.dat
./Engine/16.2.0.7/NisVer.dat
./Engine/16.2.0.7/NPCTray.dat
./Engine/16.2.0.7/nppw.dat
./Engine/16.2.0.7/service.dat
./MUI/fallback.dat
./MUI/maplngid.dat
OpenBSD_45$ find . -name *.dat

At this point, find returns no results, even though the files exist.

OpenBSD_45$ mount
/dev/sd0a on / type ffs (local)
/dev/sd0h on /home type ffs (local, nodev, nosuid)
/dev/sd0d on /tmp type ffs (local, nodev, nosuid)
/dev/sd0g on /usr type ffs (local, nodev, softdep)
/dev/sd0e on /var type ffs (local, nodev, nosuid)
procfs on /proc type procfs (local, linux)
/dev/sd0i on /mnt/m0 type ntfs (local)
OpenBSD_45$
---

Not sure if this is a bug in find, or a bug in me, so thought of
running it through you before I file a bug report. Thanks.

-Amarendra

Re: Weird behavior of find on ntfs partition

Here is another transcript, which, hopefully, is more clear than the
earlier one:
---
OpenBSD_45$ pwd
/mnt/m0/Program Files/Norton Internet Security
OpenBSD_45$ ls
BrandingEngine  MUI isolate.ini
OpenBSD_45$ find . -name *.dat
OpenBSD_45$ cd MUI/
OpenBSD_45$ pwd
/mnt/m0/Program Files/Norton Internet Security/MUI
OpenBSD_45$ find . -name *.dat
./fallback.dat
./maplngid.dat
OpenBSD_45$ cd ../
OpenBSD_45$ pwd
/mnt/m0/Program Files/Norton Internet Security
OpenBSD_45$ find . -name *.dat
./Branding/fallback.dat
./Engine/16.2.0.7/ccGEvt/Global/LM.dat
./Engine/16.2.0.7/ccGLog/ccGLog.dat
./Engine/16.2.0.7/hnData.dat
./Engine/16.2.0.7/Jobs/ccJobManagerSchedules.dat
./Engine/16.2.0.7/NCOVER.dat
./Engine/16.2.0.7/ncwTrstP.dat
./Engine/16.2.0.7/NisVer.dat
./Engine/16.2.0.7/NPCTray.dat
./Engine/16.2.0.7/nppw.dat
./Engine/16.2.0.7/service.dat
./MUI/fallback.dat
./MUI/maplngid.dat
OpenBSD_45$ pwd
/mnt/m0/Program Files/Norton Internet Security
OpenBSD_45$ find . -name *.dat
OpenBSD_45$ pwd
/mnt/m0/Program Files/Norton Internet Security
OpenBSD_45$ find . -name *.dat
OpenBSD_45$ mount
/dev/sd0a on / type ffs (local)
/dev/sd0h on /home type ffs (local, nodev, nosuid)
/dev/sd0d on /tmp type ffs (local, nodev, nosuid)
/dev/sd0g on /usr type ffs (local, nodev, softdep)
/dev/sd0e on /var type ffs (local, nodev, nosuid)
procfs on /proc type procfs (local, linux)
/dev/sd0i on /mnt/m0 type ntfs (local)
OpenBSD_45$
---

At various times, find fails to find files ending in .dat under the
Norton Internet Security directory.

-Amarendra

On Tue, Mar 24, 2009 at 2:16 PM, ropers rop...@gmail.com wrote:
 2009/3/24 Amarendra Godbole amarendra.godb...@gmail.com:
 I saw find behaving inconsistently while finding files on an ntfs
 partition. It was unable to find files ending in .dat, but then later
 on it did find those.

 OpenBSD_45$ pwd
 /mnt/m0/Program Files/Norton Internet Security
 OpenBSD_45$ find . -name *.dat
 ./Branding/fallback.dat
 ./Engine/16.2.0.7/ccGEvt/Global/LM.dat
 ./Engine/16.2.0.7/ccGLog/ccGLog.dat
 ./Engine/16.2.0.7/hnData.dat
 ./Engine/16.2.0.7/Jobs/ccJobManagerSchedules.dat
 ./Engine/16.2.0.7/NCOVER.dat
 ./Engine/16.2.0.7/ncwTrstP.dat
 ./Engine/16.2.0.7/NisVer.dat
 ./Engine/16.2.0.7/NPCTray.dat
 ./Engine/16.2.0.7/nppw.dat
 ./Engine/16.2.0.7/service.dat
 ./MUI/fallback.dat
 ./MUI/maplngid.dat
 OpenBSD_45$ find . -name *.dat

 At this point, find returns no results, even though the files exist.

 You must have left something out in this transcript. Both of these
 above find commands are exactly identical, and executed from the same
 folder, yet you claim they delivered different results.

 regards,
 --ropers

Re: Weird behavior of find on ntfs partition

On Tue, Mar 24, 2009 at 2:42 PM, Paul Irofti bulib...@sdf.lonestar.org wrote:
 On Tue, Mar 24, 2009 at 01:14:51PM +0530, Amarendra Godbole wrote:
 I saw find behaving inconsistently while finding files on an ntfs
 partition.

 Is this GENERIC?


No. -CURRENT. The GENERIC I have does not support ntfs, default, so
could not post results. :(

-Amarendra

Re: Weird behavior of find on ntfs partition