WUT_Computer_Science/Programming/EOPSY/lab4/task4/work
Krzysztof kuhy Rudnicki d407527863 Untrack 189 regenerable artifacts and close the silent-ignore trap
Untracked (--cached, so they stay on disk): 76 LaTeX artifacts, 7 .xdv XeTeX
intermediates, 18 -eps-converted-to.pdf from epstopdf, 32 files of .NET
obj/Debug/net6.0 output including three copies of lab2.dll, 16 .class/.o, the
9 MB Nx cache with its native .node, and an entire committed Python
virtualenv at ECOTE/program/ecote (python 3.10.10, 18 files).

The existing 407-line LaTeX .gitignore was NOT unused as I first assumed --
it already covered *.aux and *.class, and the artifacts simply predate it. So
this appends the categories it missed (*.o, obj/, .venv/, .nx/, target/)
rather than rewriting something that was working.

The second half is the more interesting bug. Auditing with

    git ls-files | git check-ignore --stdin --no-index

found 130 files that were tracked AND ignored. That combination fails
silently: `git add` on such a file is not an error, the edit just never
lands. Causes were dist/ swallowing the vendored jQuery/Bootstrap bundle,
.vscode/ and .idea/, and -- the good one -- the LaTeX template's man-page
patterns *.[1-9] and *.[1-9][0-9] matching EPFU's date-named report
directories, so doc/21.11/ read as a man page section and took report.pdf
and seven screenshots with it.

32 of those 130 turned out to be more build output and were untracked too;
the rest got targeted ! overrides. The first attempt used a blanket
!NotProgramming/EMISY/** which re-enabled that course's own LaTeX artifacts,
so it is narrowed to the *.1 schematic exports that actually needed it.
TRAK's nested .gitignore excluded the .vscode DIRECTORY, which stops git
descending, so no root-level ! can reach inside -- that one had to be fixed
at its source.

Both invariants now verified: 0 tracked files ignored, and 0 of the 189
untracked artifacts leaked back into view.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0172dj34FDpao6wsix8ZuCzE
2026-08-28 17:35:38 +02:00
..
javadoc feat: divided into categories 2022-06-23 17:54:37 +02:00
commands feat: divided into categories 2022-06-23 17:54:37 +02:00
Common.java feat: divided into categories 2022-06-23 17:54:37 +02:00
ControlPanel.java feat: divided into categories 2022-06-23 17:54:37 +02:00
copying.txt feat: divided into categories 2022-06-23 17:54:37 +02:00
install_unix.html feat: divided into categories 2022-06-23 17:54:37 +02:00
install_windows.html feat: divided into categories 2022-06-23 17:54:37 +02:00
Instruction.java feat: divided into categories 2022-06-23 17:54:37 +02:00
Kernel.java feat: divided into categories 2022-06-23 17:54:37 +02:00
Makefile feat: divided into categories 2022-06-23 17:54:37 +02:00
memory.conf feat: divided into categories 2022-06-23 17:54:37 +02:00
MemoryManagement.java feat: divided into categories 2022-06-23 17:54:37 +02:00
Page.java feat: divided into categories 2022-06-23 17:54:37 +02:00
PageFault.java feat: divided into categories 2022-06-23 17:54:37 +02:00
README.tjk feat: divided into categories 2022-06-23 17:54:37 +02:00
setUp feat: divided into categories 2022-06-23 17:54:37 +02:00
tracefile feat: divided into categories 2022-06-23 17:54:37 +02:00
user_guide_1.gif feat: divided into categories 2022-06-23 17:54:37 +02:00
user_guide.html feat: divided into categories 2022-06-23 17:54:37 +02:00
Virtual2Physical.java feat: divided into categories 2022-06-23 17:54:37 +02:00


  WORKPLACE ORGANIZATION:
mkdir ../work
cd ../work
cp ../ftp/* .
gzip -d memory.tgz
tar -xvf memory.tar
rm memory.tar


  READING:
more/less/vi/vim README.tjk
netscape/lynx/links install_unix.html
netscape/lynx/links user_guide.html


  COMPILE:
javac -nowarn *.java


  RUN:
java MemoryManagement commands memory.conf


  FILES:
input file name:                commands
initial content of the VM map:  memory.conf
output file name:               tracefile


--[ YOUR TASK ]-------------------------------------------------------

Create a command file that maps any 8 pages of physical memory to the
first 8 pages of virtual memory, and then reads from one virtual memory
address on each of the 64 virtual pages. Step through the simulator one
operation at a time and see if you can predict which virtual memory
addresses cause page faults. What page replacement algorithm is being
used?

Locate in the sources and describe to the instructor the page 
replacement algorithm.

----------------------------------------------------------------------