Re: Weird / FS behavior

2006-05-04 Thread Johny Mattsson

On 05/05/06 12:30, Christian Lopez de Castilla Wagner wrote:

I'm posting this to -questions and -stable, since I'm not sure if it is
a problem or if I'm simply overlooking something.


You're overlooking something :)



[EMAIL PROTECTED] cat S56/vcs/20060504/*.vcs >> S56/vcs/20060504/cal.vcs


The shell creates the "cal.vcs" file before it expands the glob (the 
*.vcs), and therefore the cat command ends up using cal.vcs as input as 
well, causing a nasty feedback loop.


Cheers,
/Johny
--
Johny Mattsson - Making IT work  ,-.   ,-.   ,-.  When all else fails,
http://www.earthmagic.org _.'  `-'   `-'   Murphy's Law still works!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Postfix and faststart

2006-01-07 Thread Johny Mattsson

On 01/08/06 12:11, Mike Jakubik wrote:
I think the port should also depend on a database server, if it has been 
compiled with one or any other of the supported configuration options. 
I'm not sure if this can be dynamically generated based on ports 
configuration though.


Maybe it would be useful to have a dummy DATABASE milestone, since I 
imagine there are many applications that do depends on various databases 
(mail & webservers being the first to come to mind). Having a DATABASE 
milestone would allow for good decoupling between the individual apps 
and the various databases. Databases would "BEFORE: DATABASE", and apps 
depending on them could simply "REQUIRE: DATABASE" and not have to worry 
about whether it was compiled with a postgresql, mysql or someothersql 
database.


Just a thought, and possibly not the most well-considered one at that, 
but I figured it might be worthwhile enough to share :)


Cheers,
/Johny
--
Johny Mattsson - Making IT work  ,-.   ,-.   ,-.  When all else fails,
http://www.earthmagic.org _.'  `-'   `-'   Murphy's Law still works!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Diskless /libexec/ld-elf.so.1: Cannot execute objects on /

2005-12-16 Thread Johny Mattsson

On 12/17/05 06:25, Mike Andrews wrote:

On Fri, 16 Dec 2005, Paulo Fragoso wrote:

After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless
machines didn't work correctly, many applications using dynamic
libraries didn't start, this error was showed:

/libexec/ld-elf.so.1: Cannot execute objects on /


We had the same problem with our netboot cluster, and going from 
RELENG_5_4 (5.4-RELEASE) up to RELENG_5 (5-STABLE) fixed it.


Confirmed. This problem was fixed shortly after 5.4-RELEASE. I'm running 
a 5.4 from Aug 22, and it has the fix in it. If you need the precise 
patch, you should be able to search the archives from August and find it.


Cheers,
/Johny
--
Johny Mattsson - Making IT work  ,-.   ,-.   ,-.  When all else fails,
http://www.earthmagic.org _.'  `-'   `-'   Murphy's Law still works!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: devfs doesn't set access rights

2005-12-13 Thread Johny Mattsson

On 12/14/05 06:44, [LoN]Kamikaze wrote:

3)
There is one kind of thing I cannot do in /etc/devfs.rules, creating
links. So I am still doing this in /etc/devfs.conf (links don't cause
race conditions anyway, I hope).

One would think that "link ttyU0 pilot" would simply be translated to
"ln -s /dev/ttyU0 /dev/pilot" which would simply create the link and it
would work as soon as a ttyU0 device (my PDA) is there. But instead it
checks weather the device exists (of course it doesn't since I didn't
press the hotsync button during boot) and omits the creation of the link.


Note that while for you it might be sufficient to have a hard coded link 
from /dev/pilot to /dev/ttyU0, that is not necessarily the case if you 
have multiple USB serial gadgets.

The way I handled it is by using an entry in /etc/usbd.conf:

#
# Fixup permissions for Palm Handheld ucom devices
# (set here and not in devfs.rules since we only want to apply
# the change to Palm com ports, not all USB com ports)
device "PalmHandheld"
devname "ucom[0-9]+"
vendor 0x0830
attach "/bin/chmod 0666 /dev/${DEVNAME} ; /bin/ln -s 
/dev/${DEVNAME} /dev/pilot"

detach "rm -f /dev/pilot


Having said that, it would be great to be able to create links from 
devfs.rules - I'd certainly use it for my /dev/cdrom entry!


Cheers,
/Johny
--
Johny Mattsson - Making IT work  ,-.   ,-.   ,-.  When all else fails,
http://www.earthmagic.org _.'  `-'   `-'   Murphy's Law still works!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Swapfile problem in 6?

2005-11-15 Thread Johny Mattsson

On 11/16/05 07:49, Lars Kristiansen wrote:

I had an infinite while loop running during the
kernel compilation, printing out 'swapinfo' every
15 seconds. The last output before the machine goes
dead is this:

/dev/ad0s1b 39848118203984830%
/dev/md0   131072 5908   131072 5%
Total  17092017728   15319210%


Quite possibly not related, but on 5.4 I can reliably cause a panic by 
attaching md0 to a file residing on an NFS drive and then use it for 
swap. After 3-5k of used swap on md0, the box dies and reboots. If I run 
"swapon" directly on the NFS file, things work fine, but it did mean 
that I couldn't use the default "addswap" rc script to set up the swap 
on my diskless system.
I'm not sure whether it's supposed to work or not, but I haven't had 
time to look into it yet. Just thought it might be another datapoint for 
someone in the know to consider, just in case it is related.


Cheers,
/Johny
--
Johny Mattsson - Making IT work  ,-.   ,-.   ,-.  When all else fails,
http://www.earthmagic.org _.'  `-'   `-'   Murphy's Law still works!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: MNT_NOEXEC flag set on / when PXE booting diskless on 5.4-R?

2005-08-22 Thread Johny Mattsson

On 08/20/05 19:28, Johny Mattsson wrote:

 I've run into a problem in that it appears that the root mount
gets marked with MNT_NOEXEC for some reason, which causes ld-elf.so.1 to 
barf with a message of:

Cannot execute objects on /


Okay, this one's for the archive, in case anyone else runs into this 
same problem:


As Danny said, the problem has been fixed (at least I don't get the 
error message any longer). By upgrading to 5.4-STABLE I've managed to 
get the full PXE boot setup to work now.


Thanks to whoever fixed that bug :)

Cheers,
/Johny
--
Johny Mattsson - Making IT work  ,-.   ,-.   ,-.  When all else fails,
http://www.earthmagic.org _.'  `-'   `-'   Murphy's Law still works!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


MNT_NOEXEC flag set on / when PXE booting diskless on 5.4-R?

2005-08-20 Thread Johny Mattsson

Hi all,

I've just been trying to switch one of my FreeBSD work stations over to 
PXE booting and running diskless (the system drive has died).


However, I've run into a problem in that it appears that the root mount 
gets marked with MNT_NOEXEC for some reason, which causes ld-elf.so.1 to 
barf with a message of:

Cannot execute objects on /

The error doesn't occur for all applications, and I've narrowed it down 
to be that whenever LD_LIBRARY_PATH is set, then ld-elf.so.1 falls over 
with the above message.


I saw in the archives that this issue was raised back in March, but 
there was no followup there. Message ID for that email was 
<[EMAIL PROTECTED]>; interested parties are recommended 
to dig that one up.


Does anyone have a solution to this problem? I couldn't find any PRs 
(open or closed).


Thanks in advance,
/Johny
--
Johny Mattsson - Making IT work  ,-.   ,-.   ,-.  When all else fails,
http://www.earthmagic.org _.'  `-'   `-'   Murphy's Law still works!

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: ATA_DMA errors - [ workaround for me ]

2005-06-25 Thread Johny Mattsson
 PCI to IDE/ATA Controller'
class= mass storage
subclass = RAID
[EMAIL PROTECTED]:11:0:class=0x03 card=0x chip=0x0519102b 
rev=0x01 hdr=0x00

vendor   = 'Matrox Electronic Systems Ltd.'
device   = 'MGA-2064W Storm (Millennium board)'
class= display
subclass = VGA
[EMAIL PROTECTED]:12:0: class=0x01 card=0x chip=0x81789004 rev=0x00 
hdr=0x00

vendor   = 'Adaptec Inc'
device   = 'AHA-2940U/UW/2940D Ultra/Ultra Wide/Dual SCSI Host Adapter'
class= mass storage
subclass = SCSI
[EMAIL PROTECTED]:13:0:  class=0x02 card=0x813910ec chip=0x813910ec rev=0x10 
hdr=0x00

vendor   = 'Realtek Semiconductor'
device   = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter'
class= network
subclass = ethernet
--


--
Johny Mattsson - Making IT work  ,-.   ,-.   ,-.  When all else fails,
http://www.earthmagic.org _.'  `-'   `-'   Murphy's Law still works!

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: ATA_DMA errors

2005-06-24 Thread Johny Mattsson
no driver attached)
Jun 24 18:22:19 kernel: atapci1:  port
0xa400-0xa40f,0xa000-0xa003,0x9c00-0x9c07,0x9800-0x9803,0x9400-0x9407 
mem 0xe9001000-0xe900

10ff irq 9 at device 10.0 on pci0
Jun 24 18:22:19 kernel: ata2: channel #0 on atapci1
Jun 24 18:22:19 kernel: ata3: channel #1 on atapci1
Jun 24 18:22:19 kernel: pci0:  at device 11.0 (no driver
attached)
Jun 24 18:22:19 kernel: ahc0:  port
0xa800-0xa8ff mem 0xe900-0xe9000fff irq 10 at device 12.0 on pci0
Jun 24 18:22:19 kernel: aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253
SCBs
Jun 24 18:22:19 kernel: rl0:  port
0xac00-0xacff mem 0xe9002000-0xe90020ff irq 11 at device 13.0 on pci0
Jun 24 18:22:19 kernel: miibus0:  on rl0
Jun 24 18:22:19 kernel: rlphy0:  on
miibus0
Jun 24 18:22:19 kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX,
100baseTX-FDX, auto
Jun 24 18:22:19 kernel: rl0: Ethernet address: 00:40:f4:28:9d:20
Jun 24 18:22:19 kernel: sio0: <16550A-compatible COM port> port
0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Jun 24 18:22:19 kernel: sio0: type 16550A
Jun 24 18:22:19 kernel: sio1: <16550A-compatible COM port> port
0x2f8-0x2ff irq 3 on acpi0
Jun 24 18:22:19 kernel: sio1: type 16550A
Jun 24 18:22:19 kernel: ppc0:  port
0x778-0x77b,0x378-0x37b irq 7 drq 3 on acpi0
Jun 24 18:22:19 kernel: ppc0: SMC-like chipset ((ECP/EPP/PS2/NIBBLE) in
COMPATIBLE mode
Jun 24 18:22:19 kernel: ppc0: FIFO with 16/16/16 bytes threshold
Jun 24 18:22:19 kernel: ppbus0:  on ppc0
Jun 24 18:22:19 kernel: plip0:  on ppbus0
Jun 24 18:22:19 kernel: lpt0:  on ppbus0
Jun 24 18:22:19 kernel: lpt0: Interrupt-driven port
Jun 24 18:22:19 kernel: ppi0:  on ppbus0
Jun 24 18:22:19 kernel: atkbdc0:  port
0x64,0x60 irq 1 on acpi0
Jun 24 18:22:19 kernel: atkbd0:  irq 1 on atkbdc0
Jun 24 18:22:19 kernel: kbd0 at atkbd0
Jun 24 18:22:19 kernel: psm0:  irq 12 on atkbdc0
Jun 24 18:22:19 kernel: psm0: model IntelliMouse Explorer, device ID 4
Jun 24 18:22:19 kernel: orm0:  at iomem
0xcd000-0xcd7ff,0xc-0xc7fff on isa0
Jun 24 18:22:19 kernel: pmtimer0 on isa0
Jun 24 18:22:19 kernel: fdc0: cannot allocate I/O port (6 ports)
Jun 24 18:22:19 kernel: sc0:  at flags 0x100 on isa0
Jun 24 18:22:19 kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Jun 24 18:22:19 kernel: vga0:  at port 0x3c0-0x3df
iomem 0xa-0xb on isa0
Jun 24 18:22:19 kernel: Timecounter "TSC" frequency 467729279 Hz quality 800
Jun 24 18:22:19 kernel: Timecounters tick every 10.000 msec
Jun 24 18:22:19 kernel: ad0: 8207MB  [16676/16/63] at
ata0-master UDMA33
Jun 24 18:22:19 kernel: ad4: 57241MB  [116301/16/63] at
ata2-master UDMA100
Jun 24 18:22:19 kernel: ad6: 76319MB  [155061/16/63] at
ata3-master UDMA100
Jun 24 18:22:19 kernel: ad7: 152627MB 
[310101/16/63] at ata3-slave UDMA100
Jun 24 18:22:19 kernel: Waiting 15 seconds for SCSI devices to settle
Jun 24 18:22:19 kernel: sa0 at ahc0 bus 0 target 4 lun 0
Jun 24 18:22:19 kernel: sa0:  Removable Sequential
Access SCSI-2 device
Jun 24 18:22:19 kernel: sa0: 5.000MB/s transfers (5.000MHz, offset 8)
Jun 24 18:22:19 kernel: sa1 at ahc0 bus 0 target 6 lun 0
Jun 24 18:22:19 kernel: sa1:  Removable Sequential
Access SCSI-2 device
Jun 24 18:22:19 kernel: sa1: 10.000MB/s transfers (10.000MHz, offset 15)
Jun 24 18:22:19 kernel: cd0 at ahc0 bus 0 target 5 lun 0
Jun 24 18:22:19 kernel: cd0:  Removable CD-ROM
SCSI-2device
Jun 24 18:22:19 kernel: cd0: 20.000MB/s transfers (20.000MHz, offset 15)
Jun 24 18:22:19 kernel: cd0: Attempt to query device size failed: NOT
READY, Medium not present
Jun 24 18:22:19 kernel: Mounting root from ufs:/dev/ad0s1a


Cheers,
/Johny
--
Johny Mattsson - Making IT work  ,-.   ,-.   ,-.  When all else fails,
http://www.earthmagic.org _.'  `-'   `-'   Murphy's Law still works!

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"