| Summary: | app-text/texlive-core-2007-r13 - cp: listing attributes of `/dev/null': Invalid argument | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alexey Shvetsov <alexxy> |
| Component: | New packages | Assignee: | Alexis Ballier <aballier> |
| Status: | RESOLVED INVALID | ||
| Severity: | enhancement | CC: | tex |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
patch |
||
|
Description
Alexey Shvetsov
2008-06-12 15:26:12 UTC
Created attachment 156507 [details]
build.log
build.log
Personally I feel doing `cp /dev/null sedscript' isn't a good idea. :) (In reply to comment #2) > Personally I feel doing `cp /dev/null sedscript' isn't a good idea. :) > me too =) alexxy@thinkpad ~ $ ls -l /dev/null crw-rw-rw- 1 root root 1, 3 Июн 10 10:20 /dev/null alexxy@thinkpad ~ $ cp /dev/null sedscript cp: listing attributes of `/dev/null': Invalid argument Created attachment 157051 [details, diff]
patch
weird... your dev/null seems a bit broken. Could you please try with the attached patch ?
Also, what happens if you do: echo foo > /dev/null ?
(In reply to comment #4) > Created an attachment (id=157051) [edit] > patch > > weird... your dev/null seems a bit broken. Could you please try with the > attached patch ? > > Also, what happens if you do: echo foo > /dev/null ? > dev null works =) yes this this patch all works fine =) thanks ;-) (In reply to comment #5) > (In reply to comment #4) > > Created an attachment (id=157051) [edit] > > patch > > > > weird... your dev/null seems a bit broken. Could you please try with the > > attached patch ? > > > > Also, what happens if you do: echo foo > /dev/null ? > > > dev null works =) > yes this this patch all works fine =) thanks ;-) then please explain me what weird setup you are on before I merge the patch and send it upstream. Here I have: crwxrwxrwx 1 root root 1, 3 2008-06-04 12:31 /dev/null and 'cp /dev/null foo' works is that something new in 2.6.26 kernels ? is that a "zen-sources" patch ? > then please explain me what weird setup you are on before I merge the patch and
> send it upstream.
> Here I have:
> crwxrwxrwx 1 root root 1, 3 2008-06-04 12:31 /dev/null
>
> and 'cp /dev/null foo' works
>
> is that something new in 2.6.26 kernels ? is that a "zen-sources" patch ?
>
looks like it was bug in 2.6.26_rc5 since on 2.6.26_rc6
i have the same permissions as you have
but btw it more simple to use touch or echo to create empty file isn't it?
(In reply to comment #7) > > then please explain me what weird setup you are on before I merge the patch and > > send it upstream. > > Here I have: > > crwxrwxrwx 1 root root 1, 3 2008-06-04 12:31 /dev/null > > > > and 'cp /dev/null foo' works > > > > is that something new in 2.6.26 kernels ? is that a "zen-sources" patch ? > > > looks like it was bug in 2.6.26_rc5 since on 2.6.26_rc6 > i have the same permissions as you have > but btw it more simple to use touch or echo to create empty file isn't it? > or may be bug in udev since it was used to set permissions for devnodes (In reply to comment #7) > looks like it was bug in 2.6.26_rc5 since on 2.6.26_rc6 > i have the same permissions as you have does it still fail without the patch ? > but btw it more simple to use touch or echo to create empty file isn't it? I prefer to merge patches and annoy upstream while they're in the middle of a new release only if we're not blaming the wrong package ;) (btw touch wont create the empty file if it already exists afaik) (In reply to comment #9) > does it still fail without the patch ? > I prefer to merge patches and annoy upstream while they're in the middle of a > new release only if we're not blaming the wrong package ;) > > (btw touch wont create the empty file if it already exists afaik) > for now it can work without patch ;) it is strange bug for me =) answer from Karl (upstream): "if cp /dev/null doesn't work, it seems to me the system is fundamentally broken." so, closing as invalid. |