ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Paul Wolneykien <manowar@altlinux.org>
To: devel@lists.altlinux.org
Subject: Re: [devel] Q: [python3] posix_fadvise не работает в hasher`е?
Date: Wed, 13 Feb 2013 20:14:52 +0400
Message-ID: <511BBBFC.9000402@altlinux.org> (raw)
In-Reply-To: <511BBB36.7080506@solin.spb.ru>

13.02.2013 20:11, Aleksey Avdeev пишет:
> 13.02.2013 19:57, Paul Wolneykien пишет:
>> 13.02.2013 19:49, Aleksey Avdeev пишет:
>>> Приветствую.
>>>
> ...
>>>
>>>   Прошу помощи знатоков:
>>>
>>> 1. Зависит ли вызов posix_fadvise зависеть от среды выполнения? Могут ли
>>> ему мешать используемые hasher`ом механихмы, такие как chroot и fakeroot?
>>
>>   /proc и /dev/pts смонтированы в хешер?
> 
> 
>   Похоже нет:
> 
> $ ls -lA /tmp/.private/solo/hasher/chroot/{proc,dev/pts}
> /tmp/.private/solo/hasher/chroot/dev/pts:
> итого 0
> 
> /tmp/.private/solo/hasher/chroot/proc:
> итого 0
> -rw-r--r-- 1 solo solo 0 фев 13 19:05 filesystems
> 
>   Как указывать их монтирование в спеке?

  Сперва смонтируй /proc вручную:

hsh-shell --mountpoints=/proc

В /etc/hasher-priv/system должно при этом быть:

allowed_mountpoints=/proc

Если тест пройдёт, то нужно написать в спеке:

BuildRequires: /proc

> 
> PS: Про /proc помню что-то про:
> 
> BuildPreReq /proc
> 
>   Оно?
> 
> 
> 
> 
> _______________________________________________
> Devel mailing list
> Devel@lists.altlinux.org
> https://lists.altlinux.org/mailman/listinfo/devel



  reply	other threads:[~2013-02-13 16:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 15:49 Aleksey Avdeev
2013-02-13 15:57 ` Paul Wolneykien
2013-02-13 16:11   ` Aleksey Avdeev
2013-02-13 16:14     ` Paul Wolneykien [this message]
2013-02-13 16:55       ` Aleksey Avdeev
2013-02-14  9:11 ` Sergey Vlasov
2013-02-14 12:00   ` Aleksey Avdeev
2013-02-14 16:38     ` Dmitry V. Levin
2013-02-14 17:15       ` Aleksey Avdeev
2013-02-14 20:05         ` Dmitry V. Levin
2013-02-14 21:30           ` Aleksey Avdeev
2013-02-17  0:11             ` Aleksey Avdeev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=511BBBFC.9000402@altlinux.org \
    --to=manowar@altlinux.org \
    --cc=devel@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git