IRC channel logs
2025-02-04.log
back to list of logs
<crupest>I find a problem. After I finish installing with LiveCD. I boot into rescue mode in LiveCD and mount the installed system partition at /mnt. I ls /mnt/dev. <crupest>It shows, warning: directory entry too long: inode: 1875969 offset: 4096. And no files are listed. Is this expected? <crupest>In the problem presented in mail, I have to boot the real system and manually create tty in /dev in rescue mode. <crupest>But I have to firstly boot the real system. And then to rescue mode to create tty. <crupest>The ls error if I installed, _not_ boot into real system, and reboot to enter rescue mode again to mount. <crupest>fsck in rescue mode does not fix it. <crupest>Now I'm trying to reproduce this in qemu. <ZhaoM>youpi: ha the investigation takes me to the isatty() system call <ZhaoM>it is expected to return 1 but it didn't <ZhaoM>enough for today, good night <youpi>sneek: later tell ZhaoM oh that's interesting. I guess this is on the pty fd . The implementation of isatty() is the term_getctty RPC. Maybe you can rpctrace vim to get exactly what is returned by it <youpi>sneek: later tell ZhaoM see hurd/term/users.c's S_term_getctty, it returns an error only if it's not the term part of the pty or if it wasn't as read or write. Both should be fine in the vim case, but apparently something is wrong there <youpi>Mmm, not sure which one it took :) <youpi>sneek: later tell ZhaoM oh that's interesting. I guess this is on the pty fd . The implementation of isatty() is the term_getctty RPC. Maybe you can rpctrace vim to get exactly what is returned by it <youpi>sneek: later tell ZhaoM oh that s interesting. I guess this is on the pty fd . The implementation of isatty() is the term_getctty RPC. Maybe you can rpctrace vim to get exactly what is returned by it <youpi>sneek: later tell ZhaoM oh that s interesting. I guess this is on the pty fd . The implementation of isatty is the term_getctty RPC. Maybe you can rpctrace vim to get exactly what is returned by it <youpi>sneek: later tell ZhaoM please read the irc log, it seems sneek did not manage to record what I wanted to say :) <crupest>Installing with the latest i386 snapshot LiveCD will result in a debootstrap failure. <crupest>debootstrap: /usr/sbin/debootstrap --components=main,local --debian-installer --resolve-deps --include=debian-ports-archive-keyring,apt-utils,dash,dbus-x11,debian-ports-archive-keyring,gdb,grep,inetutils-ping,inetutils-tools,libp11-kit0,libpci3,libpciaccess0,netdde,pciutils,usr-is-merged,vim --no-check-gpg sid /target file:///cdrom/ <crupest>debootstrap: tar: can't open './usr/share/man/man5/access.conf.5.gz': File exists <crupest>Does some new package have any problem? <crupest>I wanted to use it to test LiveCD installation problem, because snapshot one contains the latest kernel. But I failed at this step. <youpi>crupest: probably pam needs to be fixed <crupest>I found that file is in pam related package. <crupest>I don'Is this duplicate files or postinst error. I have to investigate <crupest>I don't know if this is duplicate files or postinst error. I have to investigate a bit. <crupest>BTW, does i386 Hurd have a limit on hard disk storage size? <youpi>concerning pam it's most probably just the build failure that neesd to be fixed <youpi>about the conflict between the two versions <youpi>and just moved the file between packages <crupest>youpi: Sorry. I did not catch the important point again. <crupest>Actually I have read the faq. It says the IDE has 128G limit. But I just use 100G disk and format it to ext2 and a 1G swap area. I reported in the email that after installing with LiveCD, the new system can't find tty and I can't input anything. <crupest>I have tested a lot of cases. Looks like 100G disk does not work and 60G works. However, I'm not sure about this. I'm doing the test again to confirm. <crupest>I find I'm really bad at communication. I need a lot of learning. <crupest>My machine is very slow when running these cases at the same time. So I just want to have an ask if someone happen to know this problem already. <crupest>I see the problem. Don't push enter immediately after grub is installed and it prompts you to reboot. Wait a moment... <crupest>Whatever, I get a working one from livecd.